dsh-session-toolkit
统一本地插件：会话身份、全局提示、自动恢复、Web 重启、会话日志重新定位、对等消息（整合 6 个插件）。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:Han-Yao94/dsh-session-toolkit#fc40587c489e9eef11510af3af5e1208b8d68f0cSession Toolkit 以 dsh-session-toolkit 发布，当前版本为 0.1.9。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
A consolidated plugin toolkit for the DeepSeek Harness. Six previously separate local plugins — session identity, global prompt, session auto-resume, web restart service, Session-log button relocation, and peer-session messaging — merged into a single installable package that ships in the official bundle form (dsh.bundle.patch) and installs with dsh plugin add; it also includes a Prompt Dedup feature.
Current version: 0.1.9, verified against DeepSeek Harness dsh-v0.1.6-alpha.2 (older kernels keep working through the fallbacks noted below).
Per-session persona prompt injected into that session's system prompt (independent section session-identity, order 40, resolved per agent at every assembly), with a default identity plus per-session overrides. UI provides an identity dialog (enable switch, 4000-char soft limit, save/reset, edit default, inherit default) and status buttons in both conversation.session.header.actions (id session-identity, order 40) and conversation.input.left (id session-identity-input, order 40).
A settings page (settings.section, id global-prompt, order 30) rendered as Tabs (Global / Per workspace). The Global tab injects one prompt into every conversation's system prompt (section global-prompt, order 50); the Per workspace tab injects per-workspace prompts (section workspace-prompt, order 60). Both sections are registered with interpolate: false, so {{...}} inside prompt text and referenced files stays literal — user content is never rewritten, and an unregistered {{name}} can never fail assembly. On kernels older than 0.1.6 (no per-section interpolate flag) lib/prompt-literal.js falls back to escaping { runs in the assembled text.
Per-workspace prompt injected for sessions whose cwd prefix-matches a configured workspace directory (that directory plus its subdirectories). The workspace list is derived from active sessions' cwd (ctx.agents.roots()), deduplicated and counted. When several enabled workspaces prefix-match a session's cwd, the most-specific (longest matching path) one wins. removed records paths the user removed so the active-workspace sync never re-adds them. The workspace row's enable switch is live-save (persisted immediately); the Save button only persists the prompt content + referenced files.
Both global and workspace prompts can reference a list of files. Every assembly re-reads each referenced file (UTF-8, content cached by mtimeMs + size, so an unchanged file is not re-read) and injects it after the prompt text. Byte budgets are enforced (globalPrompt.maxFileBytes / maxTotalBytes, defaults 256 KiB / 1 MiB): an oversized file is skipped rather than blocking assembly. A read failure is skipped too, and both cases are reported in the UI with the reason. Supports plain text and markdown. Per-file read status is projected to the UI via the prompt-file-status namespace (ok: N chars / fail: reason / pending); the projection is only written when the status actually changed (a settings write persists the whole settings.yaml).
Sessions with the per-session switch on are resumed automatically after a GUI restart, through the official resume path (ctx.sessionController.resolveAgent) when it exists — that is what restores the session's own model selection (via installSelection) in addition to the preset mount, and it validates subagent ownership and de-duplicates concurrent resumes. Older kernels without sessionController fall back to ctx.agents.resume plus a preset mount, carrying the default model from agentDefaultModel. Switching a session on resumes it immediately (false→true edge). Filters: switch on, top-level only (no subagent origin, no delegationDepth > 0, no parentSession), non-blank (eventCount !== 0, snapshot shape). Concurrency-bounded (CONCURRENCY = 3) with per-item failure isolation and an in-flight set that prevents duplicate resume.
A "Restart service" entry in the General settings (settings.general.item, id web-restart, order 90) that restarts the GUI server and shows a full-screen progress overlay (probe-driven progress, fill-up animation before reload, 90 s timeout fallback with manual refresh). Two platform chains, both detached and independent of the dying server:
windows-script): wscript.exe runs the launcher VBS, which hides the console and runs <DSH_HOME>/autostart/dsh-web-restart.cmd; the spawn inherits the server process token, so the elevated branch (the only UAC source) is never reached.posix-relaunch, or posix-script when webRestart.scriptPath is set): with no configuration the host restarts itself — it generates a one-shot /bin/sh script that SIGTERMs the current PID, waits up to 10 s (then SIGKILLs), cds back to the original CWD and re-executes process.execPath with the original process.argv.slice(1), appending output to <DSH_HOME>/autostart/dsh-web-restart.log. Point webRestart.scriptPath at your own .sh to take over instead (useful when the server was started by a supervisor).The client probes GET /api/restart on mount and hides the entry when the host reports available: false (unsupported platform); POST returns 501 there. Routes: GET /api/restart (health probe, constant 200 + available/mode/platform) and POST /api/restart (trigger; 409 while a restart is in flight, 500 with the reason when the configured script is missing or self-relaunch is impossible, 202 + 500 ms buffer before spawn). The client only enters the overlay on 202 — any other status is shown inline as an error instead of a 90 s dead wait. Recovery is detected by interruption-then-restore: the overlay only reloads after it observes the probe fail for restartFailThreshold consecutive checks and then return 200 again; if the probe is reachable the whole time it reports "no restart detected" (noRestart) until the timeout, offering a manual refresh.
Shadows the official entry in conversation.session.header.utilities (same id session-log-download, priority −1, cell-shadowing) and registers a copy in conversation.session.header.actions (id session-log-download-moved, order 41), reusing the official sessionLogDownload controller (ctx.get('sessionLogDownload')) so download behavior stays identical to stock. The copy mirrors the 0.1.6 official surface — a "⋯ More actions" menu whose single item triggers the shared download dialog (localized through this plugin's own locale namespace) — and is a frozen replica: a stock upgrade that changes that UI must be synced by hand, and the shadowing registration must be re-checked whenever the official entry gains new menu items.
send_to_session / list_sessions tools on the host plane (session addressing by id or workspace path, wakeup delivery) plus a "copy session ID" button in both conversation.session.header.actions (id copy-session-id, order 30) and conversation.input.left (id copy-session-id-input, order 30). Outgoing message content is converted to plain text (toPlainText) before delivery so recipients see tidy text rather than raw markdown.
Performs cross-section line-level deduplication across the identity / global / workspace system-prompt sections (session-identity, global-prompt, workspace-prompt, orders 40/50/60). promptDedup.enabled is on by default (disable only by setting it to false). Splits each section on \n and keeps only the first occurrence of each identical original line (a single seen set spans all three sections, so intra-section self-duplicates also collapse); duplicate lines in later sections are dropped. Blank lines (including whitespace-only lines) never take part in deduplication — they are markdown's paragraph/list separators, and treating them as duplicates silently collapsed every section after the first one. Every section's unique content is preserved. It does not parse {{name}} placeholders (single-line complete groups, never split by line), does not break markdown, never sets complete, and never touches harness-owned sections (harness:identity / deployment:persona / tool sections). Mechanism: subscribe to the system-prompt/assemble waterfall on the plugin's root ctx, await next(), then deduplicate sections on the returned result before returning it.
The plugin is verified against DeepSeek Harness dsh-v0.1.6-alpha.2. The host- and client-side integration points it uses are present in that native version; the two 0.1.6-only capabilities it consumes (interpolate: false, ctx.sessionController.resolveAgent) are each guarded by a fallback, so older kernels degrade instead of breaking.
@deepseek-ai/cordis 4.0.2 and @deepseek-ai/schemastery 3.18.2 (the versions dsh-v0.1.6-alpha.2 vendors). The plugin loads through the cordis harness and registers as a bundle via dsh.bundle.patch.ctx.settings.register(ns, schema, { applies: 'live', base }) → scope { get / watch(next, prev) / update / replace } where get() returns a deep-frozen value; ctx.systemPrompt.section({ name, order, text, interpolate: false }); ctx.agents.{ get, resume({ resumeSessionId, agentOptions, setup }), roots, requireInitiator }; ctx.sessionController.resolveAgent(sessionId); session.header fields (cwd, origin, delegationDepth, parentSession, agentPreset; there is no seedLength); ctx.inject(names, cb) for late-arriving optional services; ctx.get('webServer').register({ kind: 'exact', path, handler }); @deepseek-ai/dsh-tools defineTool + tools.register(); and ctx.get('agentDefaultModel'), sessionPersistence, sessionTitle, workspaceRegistry, sessionLogDownload, timer, on, effect.window.__ModuleLoader__.load({ id, factory }); ctx.get('slots') → slots.register(meta, render) / slots.inject(name, fn) with lower-priority shadows; ctx.get('settingsScope').bind({ namespace }) → { getSnapshot()/.value/.status, set(field, value), subscribe }; ctx.get('locale') → register(ns, { zh, en }) / bind(ns); and the timer client service (ctx.timeout). The bundle's runtime requires resolve against the platform seed words (react, react/jsx-runtime, @deepseek-ai/dsh-client-store, @deepseek-ai/dsh-client-ui-primitives, …).The plugin's host-side Config validates the entire configuration tree with schemastery as soon as the plugin loads. config.client is not delivered to the browser by cordis: the harness creates every client entry with loader.create({ name }) and its boot-graph rows carry only id/url/rev/inject/immediately/external, and the browser module table has no @deepseek-ai/schemastery, so a client bundle cannot export a Config either. The host therefore mirrors config.client into the session-toolkit-ui settings namespace as its composition base, and the client half reads that namespace through ctx.get('settingsScope').bind({ namespace: 'session-toolkit-ui' }). Resolution order is schema default → config.client (base) → user's settings.yaml; if the namespace is unavailable the client keeps its frozen fallback values.
lib/index.js composes nine feature modules (identity.js, global-prompt.js, auto-resume.js, web-restart.js, peer-message.js, log-reposition.js, prompt-dedup.js, prompt-literal.js, ui-config.js). inject is the deduplicated union of module dependencies; each module's apply runs inside a safe() guard so one failing module never takes the whole package down. Every contribution is lifecycle-bound (ctx.effect for prompt sections and HTTP routes, plugin-fiber registrations for tools; timers go through the timer service). global-prompt.js owns the global-prompt, workspace-prompt, workspace-registry-active, and prompt-file-status namespaces, the readPromptFiles helper (mtime/size-cached live read), and the workspace/live-workflow projection (agents.roots() → active workspaces); prompt-literal.js is the pre-0.1.6 fallback for literal prompt rendering; ui-config.js registers the session-toolkit-ui namespace that carries config.client to the browser.client/client.js is a single window.__ModuleLoader__.load bundle; the five UI modules live in IIFEs and are collected into one apply that registers all slots in order (guarded per module). All UI uses React.createElement; styles are injected as data-plugin style tags with theme CSS variables and dark-mode coverage; no global DOM manipulation. The global-prompt module renders the Tabs (Global / Per workspace) page plus a reusable FileRefsPanel (add/remove referenced files, per-file status via the bound prompt-file-status scope).| Slot | Id | Order / priority | Feature |
|---|---|---|---|
settings.section | global-prompt | order 30 | Global + workspace prompt page (Tabs) |
settings.general.item | web-restart | order 90 | Restart entry |
conversation.session.header.actions | copy-session-id | order 30 | Copy session ID |
conversation.session.header.actions | session-identity | order 40 | Identity button |
conversation.session.header.actions | session-log-download-moved | order 41 | Session log download |
conversation.input.left | copy-session-id-input | order 30 | Copy session ID (tool row) |
conversation.input.left | session-identity-input | order 40 | Identity button (tool row) |
conversation.session.header.utilities | session-log-download | priority −1 (shadow) | Hide stock button |
Schema-validated namespaces, applies: live, persisted in settings.yaml:
| Namespace | Schema | Notes |
|---|---|---|
session-identity | { default: {enabled: boolean, text: string}, sessions: Record<sessionId, {enabled, text}> } | Resolution: session record → default → empty. Disabled or empty entries inject nothing. Identity text is clipped to 8000 chars (token guard). |
session-auto-resume | { sessions: Record<sessionId, boolean> } | Switch per session; absent keys mean off. |
global-prompt | { enabled: boolean, content: string, files: string[] } | Injected into every conversation when enabled. files is the list of referenced files appended at assembly (live read with mtime/size cache; failed or oversized files skipped). |
workspace-prompt | { workspaces: Record<path,{enabled, content, files: string[]}>, removed: string[] } | Per-workspace prompt. A session gets the most-specific (longest matching path) enabled workspace whose directory prefix-matches its cwd. removed lists paths the user removed so the active-workspace sync never re-adds them. |
workspace-registry-active | { active: [{path, sessionCount}] } | Read-only projection of live workspaces aggregated from ctx.agents.roots() (each agent's session.header.cwd, deduped and counted). Never sourced from workspaceRegistry (which is not visible in this plugin's scope). |
prompt-file-status | { byScope: Record<global|path, [{filePath, status: 'ok'|'fail', charCount?, reason?}]> } | Read-only projection of the most recent read result of each scoped referenced file; the UI's FileRefsPanel reads it to show ok: N chars / fail: reason. Written only when the status changed (each write persists the whole settings.yaml). |
session-toolkit-ui | { identityCharLimit, restartTimeoutMs, restartPollMs, restartFillMs, restartFailThreshold, restartSettleMs, copyFeedbackMs } | Host-registered, read-only-by-convention namespace carrying the UI knobs to the browser half; config.client is its composition base. This is the only host→browser configuration channel available to a client bundle. |
The plugin exposes a single Config (schemastery schema) with per-feature keys. Defaults equal current behavior; override them via the plugin row's config in cordis.yml / cordis.patch.yml without touching code. config.client is validated on the host and becomes the base layer of the session-toolkit-ui namespace, which is how the browser half receives it (see Configuration validation).
- id: session-toolkit
name: 'dsh-session-toolkit'
config:
identity:
maxText: 8000
sectionOrder: 40
globalPrompt:
sectionOrder: 50
workspaceSectionOrder: 60
maxFileBytes: 262144 # per referenced file; oversized files are skipped and reported as fail
maxTotalBytes: 1048576 # across all referenced files of one section
autoResume:
concurrency: 3
webRestart:
scriptPath: '' # optional; default derived as <DSH_HOME>/autostart/dsh-web-restart.cmd
spawnDelayMs: 500
promptDedup:
enabled: true # cross-section line-level dedup across identity/global/workspace; default true (disable only by setting false)
client:
identityCharLimit: 4000
restartTimeoutMs: 90000
restartPollMs: 1000
restartFillMs: 600
restartFailThreshold: 2
restartSettleMs: 8000
copyFeedbackMs: 1600
| Key | Default | Meaning |
|---|---|---|
identity.maxText | 8000 | Identity text clip limit (chars, token guard). UI soft limit is client.identityCharLimit (4000, editor); host hard-clip is this value (8000). |
identity.sectionOrder | 40 | System-prompt order of the identity section. Migration: users who explicitly pinned identity.sectionOrder: 55 must set it to 40 to keep the identity-before-global ordering. |
globalPrompt.sectionOrder | 50 | System-prompt order of the global prompt section. |
globalPrompt.workspaceSectionOrder | 60 | System-prompt order of the workspace prompt section (placed last). |
globalPrompt.maxFileBytes | 262144 | Per referenced file byte limit; an oversized file is skipped (status fail) instead of blocking assembly. |
globalPrompt.maxTotalBytes | 1048576 | Combined byte budget for all referenced files of one section. |
autoResume.concurrency | 3 | Max in-flight resumes during startup restore. |
webRestart.scriptPath | derived | Restart script path. Empty (default) = derive <DSH_HOME>/autostart/dsh-web-restart.cmd on Windows / …/dsh-web-restart.sh on macOS+Linux, and on POSIX additionally enable self-relaunch (no script needed). Set a path to take over with your own script — on POSIX it runs via /bin/sh, and a missing file makes POST fail fast with 500 instead of hanging the overlay. |
webRestart.spawnDelayMs | 500 | Delay before spawning the restart script (202 buffer). |
promptDedup.enabled | true | Cross-section line-level deduplication across the identity/global/workspace system-prompt sections (on by default; disable only by setting it to false). When on, each identical non-blank original line across the three sections keeps only its "first occurrence" (a single seen set spans all three); duplicate lines in later sections are dropped, while blank lines are always preserved (they are markdown's paragraph/list separators). Every section's unique content is preserved. It does not parse placeholders, does not break markdown, never sets , and never touches harness-owned sections. |
| Key | Default | Meaning |
|---|---|---|
client.identityCharLimit | 4000 | Identity editor character limit (UI soft limit; the global-prompt editor uses it too). |
client.restartTimeoutMs | 90000 | Restart overlay timeout before the manual-refresh hint. |
client.restartPollMs | 1000 | Restart health-poll interval (and progress tick). |
client.restartFillMs | 600 | Progress fill animation after recovery detected. |
client.restartFailThreshold | 2 | Consecutive failed health polls before an interruption is considered observed. |
client.restartSettleMs | 8000 | Settle window (ms) after recovery before the auto-reload. DSH session titles are generated asynchronously by the LLM with no "ready" signal, so this is the wait window for the first post-restart reload to reduce the title fallback (showing the workspace name). If a session title still shows the workspace name, refresh manually or raise this value. A full fix requires DSH to expose a "titles ready" signal. |
client.copyFeedbackMs | 1600 | Copy-feedback checkmark duration. |
Install into any profile (bundle layer; single source, no copies):
# from npm
dsh plugin --profile web add dsh-session-toolkit
# from GitHub
dsh plugin --profile web add github:Han-Yao94/dsh-session-toolkit
# from a local checkout / tarball
dsh plugin --profile web add ./dsh-session-toolkit-<version>.tgz
The package's dsh.bundle.patch (cordis.patch.yml) registers the single entry (id: session-toolkit, name: 'dsh-session-toolkit') as a bundle layer — applied after dsh-base / dsh-web-app and before the profile patch layer (layer order: bundles in sequence → profile patch → home patch → --patch overlay).
Uninstall: dsh plugin --profile web remove dsh-session-toolkit.
To iterate on the source without publishing, install the checkout directly (dsh plugin --profile web add <path-to-checkout>, which uses a pnpm link: dependency), or use a manual junction into the profile's node_modules plus an explicit - insert: entry in the profile's cordis.patch.yml. Prefer dsh plugin add.
Verification gate for the source checkout only (scripts/ is not shipped in the published package; no build step and no dependency install needed):
pnpm check # syntax gate — node --check over every shipped JS file
pnpm verify # + packaging contract — entry reachability, undeclared imports, EN/ZH README version parity
pnpm verify asserts that the working-tree content equals the tarball content, so it fails on purpose if a prepare/prepack/prepublishOnly script is ever added. The DSH integration-point inventory used when upgrading the harness lives in docs/agents/integration-contracts.md.
Published on npm as dsh-session-toolkit (v0.1.8, MIT) and mirrored on GitHub at github.com/Han-Yao94/dsh-session-toolkit. Pure-JS package — no build step, no prepare script. files whitelists lib/, client/, cordis.patch.yml and the READMEs.
dsh plugin --profile web add dsh-session-toolkit; new versions are released with npm publish (or pnpm publish).dsh plugin --profile web add github:Han-Yao94/dsh-session-toolkit.pnpm pack → dsh plugin --profile web add ./dsh-session-toolkit-<version>.tgz.Runtime dependencies (@deepseek-ai/schemastery, @deepseek-ai/dsh-tools, @deepseek-ai/dsh-home-paths) are declared in dependencies and install automatically; platform modules (react, @deepseek-ai/cordis, @deepseek-ai/dsh-client-locale, @deepseek-ai/dsh-client-store, @deepseek-ai/dsh-client-ui-primitives) are peerDependencies provided by the DSH host. Harness-provided ranges are written as a prerelease union — ^0.1.2-alpha.5 || ^0.1.6-alpha.2 — because caret ranges never cross a minor line and ^0.1.2-alpha.1 cannot match 0.1.6-alpha.2 (this is exactly what produced the §F resolution skew: the plugin ended up with its own older copy while the host ran a newer one). @deepseek-ai/dsh-client-ui-slots is intentionally absent: the slots service is seeded by the web shell, so a npm peer declaration was dead weight. Verified: a clean install of the packed tarball resolves all imports without any local junction. Two install-side tools back this up (they need an external checkout/profile, so they are not CI jobs — see docs/agents/integration-contracts.md §D/§E/§F):
node scripts/dependency-skew.measure.mjs --profile <DSH_HOME>/profiles/web # §F: 期望 SKEW_COUNT=0
node scripts/dsh-log-ui.drift.mjs --harness <deepseek-harness 路径> # §E: 复刻件漂移
Three sections are contributed per assembly, in order: session-identity (order 40) → global-prompt (order 50) → workspace-prompt (order 60), placed after the deployment persona and before tool guidance (100–199). The identity section is resolved per agent (AssembleContext.agent) at assembly time from session-identity settings and is skipped for subagents (origin/delegationDepth). The workspace section injects the most-specific (longest matching path) enabled workspace prompt for a session whose cwd prefix-matches a configured workspace; otherwise nothing.
Each of the global and workspace sections appends its referenced files' content after the prompt text: every assembly re-reads files with fs.readFileSync (UTF-8, live), sanitizes each file's content (spaces out { runs), and concatenates them. A file that cannot be read is skipped (its content is not injected) but its read status is recorded for the UI. Empty sections are dropped at render.
All three sections repeat their text on every request when enabled. The global prompt applies to every conversation; the identity text applies only to sessions that resolve it (their own record or the default); the workspace text applies only to sessions whose cwd prefix-matches an enabled configured workspace (most-specific match wins). Referenced files add their full content to the effective prompt and therefore consume additional tokens — a large referenced file meaningfully increases the per-request token cost. Identity text is clipped to 8000 chars as a token guard.
Each section's rendered text is a fixed part of the request prefix while its settings are unchanged. Editing a session identity or a global/workspace prompt (or editing / adding a referenced file) may invalidate provider cache reuse from the first changed token (same semantics as stock persona sections).
send_to_session and list_sessions are registered on the host plane and visible to every session (subagents inherit them through the standing preset composition). Their arguments and results are JSON-compatible.
ctx.settings.register(...).scope.get() returns a value frozen by deepFreeze (immutable). Any host write to a scope must first { ... } copy the object (and .slice() arrays) into a mutable object, then use update() (the register scope has get/watch/update/replace, no set); writing to the frozen object directly throws object is not extensible (this was the root cause of the "workspace list empty" bug fixed here). On the client side, settingsScope.bind().set(field, value) is used (the client scope supports set). The same { ... } copy rule applies on the client for workspace-prompt writes (onWsFilesChange / save / saveWsEnabled / removeWorkspace).readPromptFiles runs inside the prompt text() on every assembly; a failing file never breaks assembly and its status is recorded in prompt-file-status for the UI.dispose() — AgentHandle.dispose() removes the session from storage; turning a switch off only affects the next restart, it never takes a live session down.taskkill targets a same-privilege process and the script's elevated branch (the only UAC source) is unreachable. If port 3080 is held by another program, an elevated retry may still appear (documented in the restart script).session-log-download cell at a lower priority; the stock entry abdicates gracefully if the shadow crashes.toPlainText (10 rules, code-fence state machine, loose matching) runs at send time only; the message structure and source: { kind: 'user' } are unchanged.lib/ and client/client.js.sessionLogDownload controller interface and mirrors the 0.1.6 official surface (a "⋯ More actions" menu). It is a frozen replica: run node scripts/dsh-log-ui.drift.mjs --harness <checkout> after a DSH upgrade — it audits both sides for the same anchors and exits non-zero on drift (§E).toPlainText can drop * pairs in non-format positions (e.g. a * b * c); acceptable for agent-generated messages, boundary tightening is optional.inject union waits for every listed service; a profile missing one service delays the whole package (web profile provides all of them today).pnpm install must be re-run after changing them, and the resulting install should be checked with node scripts/dependency-skew.measure.mjs --profile <DSH_HOME>/profiles/web (expect SKEW_COUNT=0; DE-INSTANCE = same version, different instance, which §F treats as acceptable).ctx.get('agentDefaultModel'), sessionTitle and workspaceRegistry are resolved lazily at call time and degrade to cwd/path addressing; tools and webServer are awaited through ctx.inject so a late-arriving service cannot silently disable a feature (the loader creates entries concurrently, so apply-time ctx.get had no ordering guarantee).restartFailThreshold × restartPollMs (default 2 × 1000 ms = 2 s) and then recovers. If a relaunch completes in under that window, the overlay can misreport "no restart detected" (noRestart); lowering restartFailThreshold to 1 makes detection more sensitive but also lets a single transient failure masquerade as a restart interruption.readPromptFiles runs a statSync per referenced file on every assembly and reads only when mtimeMs/size changed; the per-file and total byte budgets prevent a huge file from blocking assembly or inflating the prompt, and the status projection is written only on change. On the client, files are saved immediately (onWsFilesChange / ).Uninstall the bundle: dsh plugin --profile web remove dsh-session-toolkit, then restart the GUI. To roll back to the pre-consolidation layout, re-enable the original plugins instead of installing this package.
{{name}}completeThe client.* keys below are validated by the host and become the base layer of the session-toolkit-ui namespace — the channel the browser half actually reads. Users can also override them per user in settings.yaml under that namespace. |
savesession-toolkit-ui — because the harness gives client entries no config channel and no schemastery, the browser half cannot validate or receive config.client directly; the host mirrors it into the settings namespace (see Configuration validation) and the client falls back to frozen defaults when the namespace is unavailable.