プラグイン

行範囲選択：ワークスペースのファイルを閲覧し、行番号付きでコードをプレビューし、範囲を視覚的に選択して @path:start-end 参照をコンポーザーに書き込み、送信時にエージェントが正確な選択行を受け取る。

DeepSeek Harness 向けの GPU 対応実行レイヤー。gpu_status / gpu_exec / gpu_run_bg ツール、ステップごとの GPU コンテキスト注入、CUDA_VISIBLE_DEVICES による自動カード選択に対応します。

DeepSeek Harness 向けの再利用可能な Markdown プロンプトプロファイル。ターンごとのモデル選択、引数の置換、状態の復元に対応します。

Composer button that rewrites the current draft with four style presets, selection-only rewriting, a keyboard shortcut and instant undo; no settings page.

AI-native text editor for DeepSeek Harness: tabs, encoding-safe saves, selection/document AI with diff review, Markdown preview, and Windows file associations.

One settings card that gives every DSH agent mode its own compaction threshold: it registers <mode>-compact-<ratio> preset copies with compaction-basic.thresholdRatio rewritten, re-registers when the value or the selection changes, and can adopt one copy as the default mode (standard > cordis > minimal > ptc).

Fills in a cheaper sibling route for subagent calls that name no provider, model or effort (for example Opus to Sonnet 5.5 at medium, Qwen max to Qwen flash); explicit choices and subagent_fork are left alone. Requires the subagent-model-selection policy to be enabled with the target route in its allowedModels - without it the plugin does nothing.

One-step local model onboarding plus a light harness for DSH. On load it probes loopback and private-network inference endpoints (llama.cpp, Ollama, vLLM, LM Studio), reads each model's context window and output budget from the backend, and registers the provider through settings, so a local model becomes selectable without hand-writing config. It then trims only that provider: masks the tool list through tools.restrict, drops named system-prompt sections and memory contexts, swaps the injected instruction block for a short one while preserving its first 80 and last 96 characters, and truncates tool-schema descriptions without touching structure or required fields. Cloud providers are returned as the same assembly object, untouched. The injected block is re-read from disk on every assembly, so editing the file takes effect on the next request with no reload. The panel in the plugin detail page is a live operations view: it shows whether the takeover is active and by which hook, how many characters the last assembly was trimmed from and to, and which providers are online (probed concurrently, with a real one-shot completion reporting latency and reply text per provider). If a local backend is not running, the panel offers a one-click launch: it probes the port first (never starting a duplicate), then starts the matching server (ollama serve, or a custom command you supply) detached and polls until the endpoint answers, clamping the wait to 3-600 seconds, reaping the child it just spawned if it never answers, and naming the paths it searched when it cannot find the binary. A stop button kills backends this plugin started (SIGTERM, then SIGKILL) and refuses to touch a server somebody else launched. When a model has just been downloaded and no backend exists yet, the panel can also scan the machine for .gguf files with hard caps (300 models, 20000 directory entries, Downloads only one level deep), start llama-server on the chosen one (skipping the .mmproj. vision projection and reusing a server that already answers), register the provider under the model id the backend reports, and run one real completion to prove it works. Before spawning anything it does a fit check that counts only the part of the file the GPU cannot hold: hostBytes = fileSize - VRAM, compared against max(total RAM - 2GB, free RAM). A file far larger than RAM is refused outright; a heavy host-side remainder is refused unless you confirm; the same remainder under mmap is only a warning, because the weights land in reclaimable page cache. A load-mode selector (auto / mmap / none / mlock / mmap+mlock) maps to llama.cpp --load-mode, and the default is whatever the engine picks. From 0.4.2 everything above is derived from the platform instead of assumed: home and data directories come from os.homedir() and the OS conventions (LOCALAPPDATA on Windows, ~/Library/Application Support on macOS, XDG_DATA_HOME elsewhere); backend binaries are looked up in the official install locations of each OS and can be pinned with OLLAMA_BIN, LLAMA_SERVER_BIN, VLLM_BIN or LMSTUDIO_BIN; model discovery walks DSH_LOCAL_MODELS_DIR, ~/models, ~/llama.cpp/models, ~/.cache/llama.cpp and the LM Studio data directory, with the WorkBuddy layout demoted to one candidate among them. VRAM is asked from nvidia-smi, then rocm-smi, then sysctl hw.memsize on Apple Silicon (flagged unified, so the same bytes are not charged twice), and any flip to a unified-memory budget is handled explicitly. Before building a command line the plugin runs llama-server --help once and keeps only the flags that build actually has, so older engines get --n-gpu-layers 99 and no KV quantization while newer ones get auto plus q8_0; anything it cannot probe is passed through rather than dropped. LM Studio is started with lms server start --port N rather than being lumped in with the engines that need a model argument, and vLLM gets its own --model example instead of llama.cpp syntax. Windows, macOS and Linux are all exercised in CI, including a windows-latest and a macos-latest job, because a cross-platform claim that has only ever run on one OS is not a claim. Two of those suites exist specifically to catch this machine's blind spots: one replays the whole suite with process.platform rewritten to each OS, and one deletes every advantage this development box has — no nvidia-smi, no rocm-smi, no sysctl, an empty PATH, a home directory with no models — and requires graceful degradation rather than a crash. That last one caught a real class of bug: several assertions hardcoded 'lms.exe', which cannot pass where the executable has no suffix. Measured on the reference machine: a 16.9GB 27.2B MoE with 14.5GB of VRAM holds a 285-691MB working set and sustains 76 tok/s after a 1000-2000 token warm-up, so file size alone is not a fit signal. From 0.4.3 the scanned models are shown as a table rather than a dropdown (one row per gguf, with its size and any fit warning), so you can see what is on disk before choosing. From 0.4.4 the delete button on the provider table removes the provider entry, not the weights file on disk. That distinction matters: what people actually want to clear out is the dead entry - one pointing at a port that never answered, one registered twice for the same port, one whose model file was deleted long ago - not a 15.8GB gguf. Deleting a config is undone by importing again; deleting a gguf is not. The removal goes through settings.mutate with an unset op on \['providers', id], because update merges layers: writing null there leaves a null provider key that the loader reads as a broken config rather than an absent entry, and only mutate/unset is implemented as Reflect.deleteProperty. The result is read back afterwards, because unset on a key that comes from a lower layer (the profile cordis.patch.yml or a home patch) does not delete it - it restores the inherited value, so the call succeeds while the entry stays. When the entry is still there the panel says so and points at the file to edit instead of reporting success, and a DSH whose settings service predates mutate() is told plainly rather than silently ignored. Deleting takes two clicks and clearing the confirmation is as easy as clicking another row; on success the online and baseURL caches are cleared and the tool surface is recomputed, since the provider list changed. The gguf itself is never touched by this plugin - the scanned-model table is display and selection only.VRAM reporting is driver-dependent. From 0.4.5 model discovery also reads Ollama's own storage: its blobs are named sha256-… with no extension, so extension matching could never list them. Weights are now accepted by extension OR by GGUF magic header (only dot-free files of at least 8MB, capped at 600 header reads per scan; obviously-not-weights extensions like .json/.md/.safetensors/.part are never opened). Ollama models are resolved from their manifests: the model layer is picked by mediaType application/vnd.ollama.image.model (never adapter/mmproj layers), the human-readable name is restored from the manifest path (…/qwen3/8b becomes qwen3:8b, …/latest stays bare), tags sharing one blob merge into a single row, and the metadata kv supplies name, quantization and context length. Adopting an Ollama model does not start a duplicate llama-server over the same weights: it confirms ollama serve answers on 11434 (launching it if not) and registers the provider under the tag the endpoint itself reports — the blob's sha256 name would never match anything, since 11434 lists qwen3:14b, not sha256-a8cc…. Two real-machine-only traps fixed on the way: existsSync('<file>/') returns true on Windows, so manifest-vs-directory branching now goes by parseable content instead of trailing-slash semantics; and the quantization label table had been copied from a stale ggml enum generation, labelling ggml_type 15 as Q5_K_S while ollama show reports Q4_K_M. Same-blob dedup is by (dev,ino), keeping whichever entry has a name. Verified on the reference machine: the scan goes from 1 row to 4 — qwen3:14b (8.64G) and qwen3:8b (4.87G) now appear with Q4_K_M badges — in 4ms; npm run verify exits 0 (launcher 57, portable 35, panel-host green including the linux/darwin simulated-platform runs); the new panel-host suite builds a real miniature Ollama store in tmpdir and points OLLAMA_MODELS at it, so results no longer depend on whether the test machine happens to have Ollama installed. From 0.4.6 the panel shows each model its real name instead of its file name, because some download tooling stores every weight under one generic file name, leaving the real name only inside the GGUF header. The scan now reads each file GGUF KV section - not a fixed-size head buffer, because tokenizer.ggml.tokens (hundreds of thousands of strings on a large MoE model) and the chat template push general.file_type past any window; and GGUF string arrays are interleaved (u64 length plus payload per element), so treating them as a length table walks the cursor off the rails and produces astronomically large reads. Reading and skipping are accounted separately: key names and types are always read, string values over 256KB and string arrays are only walked past without copying, non-string arrays over 64 elements are skipped outright, and a cursor past the file size stops the read, because an out-of-range position means the cursor is wrong rather than that a limit should be raised. The displayed name goes Ollama tag, then general.basename plus size_label, then general.name, then the file name, with the full string kept for the hover text since it usually carries internal build numbers; mmproj files are now identified by general.type as well as by name. A short read (truncated file) no longer feeds half a value into the parser. On the reference machine, reading one file header parses 44 keys in about 16ms, and a whole scan takes about 31ms. From 0.4.7 the smoke test no longer fails the first time and passes the second. The old code gave both request attempts one shared AbortController and one shared 30-second timer, so the total budget covered both rounds: a cold load of a large model burned it in round one, the abort left the signal permanently aborted, and the second round (the Ollama-style reasoning_effort: none retry) could not even be sent - which is exactly why the first click returned This operation was aborted and the second succeeded. Now each attempt gets its own controller and timer, a timeout retries once automatically (retryOnTimeout, on by default) because a first-request timeout almost always means the weights are still being read from disk, and non-timeout errors (refused connection, HTTP error) are not retried at all. Timeouts report themselves: the message says the wait exceeded smokeTimeout, whether a retry already happened, and points at the new smokeTimeout setting (seconds, default 60, clamped to 5-600) - port responding is not the same as tokens coming out, so it is a separate knob from launchTimeout. Unrelated: an example naming one specific model was dropped from the panel copy, since not every machine has that model downloaded, and the explanation now describes the mechanism instead.

Persona 3 Reload style skin: midnight-blue palette, cyan hairlines, skewed blue selection slabs, game-style-like dialogue boxes.

Wandering Earth 550C control-room palette for the DSH Web UI, with dim 2px frames and amber selection states.

Looks up English words in chat replies by click or selection, showing part of speech, Chinese meaning and exam tags; selecting a pure-English sentence translates it. Ships an offline dictionary: 20,499 entries, 8,960 with bilingual examples, 6,374 with root analysis.

Select English text in the conversation or the sidebar file preview to translate it in place — single words get a dictionary entry with IPA, part-of-speech senses, web meanings and pronunciation, while sentences use machine translation.

Two split composer controls for output style: a tone switch with its own preset menu, and an output-form switch with its own preset menu; each session's system prompt follows the selections, with a preset settings page.

チャットの履歴でテキストを選び、右クリックして入力欄に引用します。引用は分割されないチップとして渡され、折りたたみ可能なカードで表示されます。モデルにはメッセージの役割、ターン、ブロック番号、文字範囲を含む全文が渡ります。

DeepSeek Harness向けWeb検索plugin。複数ベンダーの検索backendを選択戦略に沿って振り分け、自動failoverします。

DSH message内の引用textをクリックすると、元の場所へ戻り、中央に合わせて一時的にhighlightします。

DSH Web GUI向けYoudao風の選択範囲翻訳。画面上のtextを選択して浮動buttonを押すと翻訳を表示。既定ではkey不要の公開翻訳endpointを使い、もう1つのengineとしてHarness自身のLLMも選べます。

舗装設計手法の判断マニュアル。9章に76枚のカードを収録し、手法選択、指標の割り当て、パラメータの基準、軸重換算、気候区分を扱います。空港章は完全なPDFを再OCRして復元しています。

Windows専用（Edge WebView2 Runtimeが必要）です。現在のセッションを常に最前面のWebView2ミニウィンドウで開き、独自タイトルバー、自由なサイズ変更、メインウィンドウへ戻る操作を提供します。全画面／範囲スクリーンショットをcomposerに貼り付け、任意のアプリで選択したテキスト用の「選択範囲について質問」ピル、グローバルホットキー、設定セクションも追加します。

DSHで手軽に質問できます。チャット、Markdown／コード、レンダリング済みHTMLレポート、better-sidebarエディターのテキストを選択すると、既定の回答が自動開始します（英語の文章は翻訳、用語は説明、質問には回答）。入力するとキャンセルされます。メインウィンドウのモデルによる1回限りのcompletionで回答をストリーミングし、読み取り専用の会話スナップショットを引き継ぎ、選択したファイルを既定で最大20,000文字のコンテキストとして読みます。メインセッションには書き込みません。1行でインストールでき、ホストのルート、クライアントスロット、ドキュメントレンダラー、iframe選択ブリッジは個別に差し替えられます。

右サイドバーに、現在のセッションで使えるスキルの一覧、検索、タグ付け機能を追加します。自分の保存済みプロンプトと組み合わせ、選択内容をワンクリックでコンポーザーに追加できます。スキルやプロンプトをピン留めし、システムプロンプト経由で常時有効なコンテキストとして注入することもできます。

VS Codeで選択した箇所またはファイルパスを、行範囲付き`@path`参照として開いているDSH会話のcomposerに挿入。送信はしません。同梱bundle内のcompanion VS Code拡張`.vsix`が必要（composerからワンクリック導入、または手動導入）。

DeepSeek Harness（大肥鱼 bot）の2ホスト連携：ローカルチャットからタスクを渡し、クラウドworkerで範囲限定ジョブを実行し、1つのworkbenchで結果確認と後続手順の承認。保護された6ページ導入、タスクごとのmodel選択、承認台帳、段階的な制御付き実行を含みます。

OpenCode GoサブスクリプションをDSH Desktopへ接続。API key管理、利用状況スナップショット、自動モデル同期、モデル選択に対応。