Repository navigation
DeepSeek Harness Obsidian plugin 3.1.0
What's new in 3.1.0:
- Selections no longer always end with 'should I rewrite it?': DSH first decides whether you are sourcing material, editing in place, or just locating/explaining, so requests like 'save this into another file' or 'summarise this' are answered directly
- Selecting a heading now means the whole section: the range widens to the next heading of the same or higher level, mid-sentence selections expand to the full sentence or paragraph, and the edit reports the changed line range
- Explicit write requests are executed without a second confirmation; only four genuine ambiguities prompt a question (ambiguous target, append vs overwrite, deletions, unclear request), and selecting text with no instruction reports what was located, then asks
- Verified DSH range raised to 0.2.2-rc.5: the 28 seams the plugin relies on show no drift versus rc.3, the same 338 upstream packages, and the plugin already runs on rc.5 day to day
Features:
- Embed the DSH Web GUI (iframe) with one-click install/detection and auto service startup (silent on Windows)
- One-click install auto-installs missing tools (git/Node/pnpm) and shows a live progress bar (download % + stage timers)
- Send selected text to DSH: the implicit bridge line appears when you focus the chat box, rewritten in place so it never clears your input or steals the caret
- Two-way bridge: DSH outputs inside your vault open in the editor; [[wikilinks]] in chat are clickable
- Attachment uploads work inside the panel and keep native percentage progress (system browser behaviour untouched)
- Multi-profile coexistence: bind the panel to another profile while the desktop app keeps its own, one port per instance; restarting only ever touches instances this plugin launched, and foreign DSH processes are never killed
- Custom service endpoint (IPv4/IPv6) and native HTTPS for the DSH service, with a read-only connection test (DSH 0.2.1-rc.2)
- One-click remote access: self-signed HTTPS certificate, rootCA.pem on the Desktop, auto-filled endpoint settings, iOS/Android trust steps, a walk-through phone remote-access example in settings, and one-click reset of the endpoint defaults
- Endpoint settings also apply to a custom startup command: only missing --host / --tls-cert / --tls-key are appended (flags you already wrote win)
- Phone access auto-installs the root certificate into the current Windows user's trust store (no admin), and a Copy token link button copies the full token URL — the browser drops ?token= from the address bar after its redirect
- Resetting endpoint defaults restarts the service and reloads the panel automatically, so the panel follows the settings back to 127.0.0.1 (an open external tab must be reopened)
- Fixes the embedded panel on DSH 0.2.2 (it showed 'dsh web authentication required' after DSH moved the index fallback to the Fetch API)
- When the panel is unavailable, a 'Fall back to adapted DSH' button installs the verified version and restarts the service (never silently: it asks first)
- Compatibility verdict is shown, never shouted: the plugin checks the local DSH version against its verified range (currently 0.1.5-rc.1 ~ 0.2.2-rc.5) and whether the bridge is actually live in the served page, then reports it as plain text in the status row and under 'current compatibility' — no interruption dialogs; the plugin info row links to the full explanation
- Update channel you control (stable / follow official releases / include alpha) plus an optional automatic check that always asks before installing; a version is only offered after it appears as a GitHub release of the official repo, so a prerelease that npm receives first (next tag) is not pushed
- Only the official DSH package counts: versions are read from the official manifests, never from third-party same-named packages on npm
- Bilingual UI (Chinese / English); other system languages fall back to English. AED safe-mode rescue, session format repair, credential self-heal, page zoom, shortcut passthrough
- macOS / Windows / Linux (desktop)
Assets are built from source and attestation-signed by GitHub Actions.
See the repository README for install instructions and settings.