Plugins

Enregistre un fournisseur fetch `wsl-proxy ctx.web` afin que `web_fetch` officiel utilise undici `ProxyAgent` via `HTTP(S)_PROXY`, au lieu de se connecter depuis WSL à une IP publique épinglée par DNS (le chemin officiel qui provoque `TypeError: fetch failed` derrière un proxy Windows).

Canvas infini pour les sessions, avec zones liées aux workspaces et préréglages d’agents, cartes de session épinglées, notes autocollantes et repères d’alignement.

Outils de code et préréglages d’agents façon Codex pour les modèles GPT dans DeepSeek Harness : exec_command, write_stdin, apply_patch et view_image ; routes OpenAI Chat Completions et Responses API reliées au plan, ask, approval et compaction natifs DSH. Les commandes longues deviennent des jobs d’arrière-plan DSH à sortie head/tail bornée, lisible via job_output. Chaque type de sous-agent peut épingler son preset, fournisseur, modèle et reasoning effort.

Gestion du contexte DeepSeek Harness : allège les sorties d’outils selon leur contenu, nettoie les vieux journaux, épingle les exigences utilisateur et travaux en cours, puis archive avant compactage avec piste d’audit.

Épingle et désépingle les sessions en haut de la barre latérale Web DSH, avec panneau dédié, section d’archives et intégration au menu natif à trois points.

Ajoute un sélecteur Workspaces/Recent-sessions au-dessus de la liste latérale, un groupe épinglé, un menu par ligne (pin/unpin, copie du session id), un filtre de titre et un stockage local au navigateur ; migration unique depuis dsh-plugin-pin-session.

Bibliothèque de référence Clean Architecture pour DSH : indexe huit dépôts épinglés (Go, Java, C#, Python) dans une base FTS5 locale, avec règles d’assertion, registre de revue et panneau d’observation en lecture seule.

Vue fractionnée multi-session pour l’UI Web DeepSeek Harness : la fenêtre supérieure remplace le slot racine par un conteneur redimensionnable; chaque panneau est un iframe avec client DSH complet fixé à sa session. Barres de titre par panneau et hibernation LRU.

Gestionnaire de menus tiers pour l’interface Web DSH : rassemble les nouvelles entrées ajoutées par d’autres plugins en un seul endroit, avec possibilité de réduire et d’épingler des éléments.

Divise la barre latérale de DeepSeek Harness en volets Épinglés et Récents à défilement indépendant, et masque les sessions épinglées de Récents.

Navigateur de plugins DSH sensible aux tâches : construit un index local à partir des sujets GitHub et des listes communautaires, effectue des recherches dans 28 classes de capacités bilingues et fournit un audit statique des risques au niveau des commits, une installation épinglée soumise à consentement, des vérifications de composition et une récupération.

Plugin DSH : porte à mot de passe pour l'accès distant (non-loopback) à /api (sans mot de passe par défaut), débloque les points de terminaison privilégiés épinglés sur loopback, restaure tout à la désinstallation et offre à l'utilisateur local 127.0.0.1 le sélecteur de dossier natif du système pour choisir l'espace de travail. selec

Adds a cross-workspace activity sidebar for running, waiting and unread sessions, with search, optional pinned and scheduled-delivery groups, local read tracking and confirmed archiving.

A sticky-notes wall pinned to the sidebar: one click opens a full-page wall, notes save as you type, and writing #tags in the text turns them into one-click filter chips. Six paper colors, pinning, search, JSON export and import.

Domain-routed proxy for DSH fetch traffic: hosts on a force-proxy list always go through the proxy, every other host tries direct first and fails over to the proxy within a second, the first channel to answer is pinned for the session, connections are reused for 120 seconds, and each attempt is logged. Can also route pnpm/git subprocesses used by plugin installs.

Archives sessions that have gone unused for longer than a set number of days (5 by default), skipping archived, pinned, and protected ones — a session context-menu item marks a single session as protected, a small shield shows it on the row, and a General settings field changes the threshold.

A right-sidebar tab listing the files DSH Sessions produced, newest first, with the Session in view expanded on top: a click copies a row's full path, a double click previews it in the sidebar, and a file can be pinned in one Session or in all of them.

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.

Adds a Speed setting (Standard, Fast, Ultrafast) for OpenAI and Codex models on a patched dsh build: the pinned dsh 0.2.1-alpha.2 web client needs the Model / Effort child-slot patch, the host pi-ai must be 0.87.1 or 1.1.0 (other versions refuse to load), and the terminal controls need a patched dsh-TUI. Then it appears in the Model / Effort menu; in dst /speed opens a picker or sets the speed directly, and the current speed shows in the bottom bar. The choice is kept per session, provider and model and is sent as the request service tier.

Replaces the DSH sidebar list with a workspace rail: pinned chats and folders, projects that are folders with their own AGENTS.md and files, a virtualized Recents list ordered by the last finished turn, a project_search tool, unread markers, a collapsed icon column with an unread count and a live browser tab title.

Base de connaissances partagée en équipe : un membre lance un Hub sans dépendance ; les autres installent le plugin et le rejoignent avec un code d’invitation. Les contenus importés sont classés en dix catégories avec résumé, confiance et points ; 15 outils d’agent permettent de les ajouter, rechercher, rappeler, commenter et lire. Les éléments importants restent épinglés avec une recommandation manuscrite jusqu’à leur lecture. Chaque compte dispose aussi d’une bibliothèque locale privée, de collections, d’un résumé hebdomadaire et de différences de versions.

Mémoire d’agent avec courbe d’oubli : les entrées gagnent du poids lorsqu’elles sont mentionnées, diminuent lorsqu’elles sont oubliées et les éléments épinglés ne décroissent jamais. Six outils et un panneau de paramètres.

Mémoire à long terme intersessions pour DeepSeek Harness : injecte les règles épinglées à chaque tour et rappelle le reste selon des mots-clés pondérés par IDF. Déduplication par fact-key, stockage JSON simple et édition/suppression des entrées dans les paramètres.

Liste les sessions Claude Code et Codex dans le navigateur DSH Workspace, pour les ouvrir, poursuivre, épingler, renommer ou archiver, avec onglets terminal, file et git.