f376ee23d1
Three defects surfaced while driving the Models page. A hand-declared model needed an explicit contextWindow and maxTokens, but a provider listing usually returns ids and nothing else — so the page happily wrote a profile the adapter then rejected, which took the whole namespace down silently. Capacities now fall back to the route's `defaultContextWindow` (262,144) and `defaultMaxTokens` (32,768). Both are guesses by construction, which is why they are route fields a deployment corrects once rather than constants buried in the adapter; the fallback sizes the model and never becomes a per-request cap. That silent failure was the second defect. A schema-valid profile the adapter could not serve was stored and only rejected later, disabling every route in the namespace with nothing said. `dsh-settings` gains an optional `validate` on registration — a check for what a schema cannot express — and `llm-pi-ai` refuses an unserviceable section at the write that produced it. A stored section that fails keeps the namespace's last good value, as a schema failure already did, so an externally edited document still cannot strand the owner. The plugin's own last-good fallback goes with it: nothing reaching it can fail any more. Third, a model with no reasoning metadata advertised the single level `off`, which pi-ai translates to *omitting* the reasoning option — the same request naming no effort produces. Selecting it disabled nothing, so a provider whose default is to think kept thinking with `off` shown as selected. Such a model now reports no reasoning capability at all, which is the seam's way of saying the control is unavailable, and the per-model `reasoning` flag is gone: without a thinkingLevelMap to spell levels it could only invent them. The protocol table narrows to the three a hand-declared route reaches today, most-reached first so a surface offering a choice defaults to the one gateways actually speak.
@deepseek-ai/dsh-tool-cordis
English | 中文
The self-referential Cordis toolset: three model-facing tools over the live runtime in the current DSH process. Design home — sandbox semantics, temporary-plugin lifecycle and composition, the generated API catalog, standing decisions: the toolset Agent Note.
What it does
cordis_inspect— read-only report over the current process: services, all live plugin fibers, registered tools, thecordis_mounttemporary-Plugin subset, and the catalog-backedapi/eventsreferences. An exactnamewithwhat: "api"orwhat: "events"narrows the report and adds the original source JSDoc.cordis_mount— evaluates model-written JavaScript now and saves it nowhere; the code must return an in-memory temporary Plugin tracked asdyn-<n>.cordis_unmount— unmounts onedyn-<n>temporary Plugin and returns only after its owned effects reach quiescence. It cannot remove Loader, configured, or installed Plugins.
Exact model-facing schemas: the generated tool catalog.
Canonical successes are the inspection string, mount { id, pluginName, state, provides, waitingFor }, and unmount { id, pluginName }. Native rendering says whether the temporary Plugin is running or pending and that it remains available until unmounted or DSH restarts; unmount confirms that it was removed.
Temporary Plugins live only in the shared DSH process memory. They remain active across later turns and may affect other sessions in that process, but disappear after cordis_unmount, toolset unload, or DSH restart. They create no Plugin file, install no package, change no cordis.yml or personal/project configuration, do not survive restart, and cannot be promoted automatically. To keep an experiment, ask the Agent to implement a normal local, project, or repository Plugin through the regular development workflow.
Trust stance
The sandbox isolates globals but is not a security boundary. Node globals are absent or redirect to Cordis services such as ctx.fs, ctx.web, and ctx.bash, and writes to globalThis stay local, but host-realm helpers make escape possible. Mounted plugins receive a façade without framework internals, yet its allowed services affect the live runtime. Dynamic tool schemas and annotations cross the realm through iterative JSON cloning and schema normalization, so valid deep declarations are memory-bounded rather than call-stack-bounded; records with JSON-invisible keys and subclassed or decorated schema arrays reject before normalization. Treat this toolset like bash access; see the design and trust stance.
Config
| Field | Default | Meaning |
|---|---|---|
vmTimeoutMs |
5000 |
Bound on the SYNCHRONOUS portion of temporary-Plugin code evaluation; an async body escapes it |
The generated API catalog
src/api-catalog.ts is generated from the same Typert FaceModel projection as docs/cordis-catalog and freshness-gated by pnpm run verify-cordis-api (in doc-sync) — never edit it by hand. scripts/gen-cordis-api.ts is a compatibility entry point for that unified projection, not a second collector. cordis_inspect intersects the committed catalog with the live service store at call time; it has no runtime Typert dependency. Broad api / events reports render summaries and signatures only; an exact name opts into the retained method/event JSDoc, and unknown or non-running service targets fail loud.
Rendering
All three tools render generic cards (read / execute / delete); cordis_mount carries the temporary-Plugin code as rawInput. Presenters are pure functions of the args; results keep the default text rendering.
Export shape
Namespace plugin: named exports name / inject / Config / apply, no default export (docs/postmortem/0001).
Model Experience
Tool schemas
What the model sees
The conversation model sees the generated cordis_inspect, cordis_mount, and cordis_unmount schemas whenever this plugin is visible.
Token effect
Fixed schema cost on every request in that tool view.
KV Cache effect
Prefix-stable while this tool view is unchanged. Scoping or plugin lifecycle changes that hide these definitions may invalidate reuse from the first changed schema token.
Tool-call history and results
What the model sees
Inspect joins selected sections exactly as ## <section> then a newline and the data-dependent body, with one blank line between sections; what: "temporary" uses the ## Temporary Plugins heading. Each temporary-Plugin row reports running/pending state, provided and awaited services, and its lifetime until unmounted or DSH restart. The empty state explains that cordis_mount Plugins disappear on restart. Broad API/event reports omit JSDoc; name with what: "api" or what: "events" returns one exact target with its original JSDoc. Mount returns Temporary Plugin <id> is running (...) or Temporary Plugin <id> is pending (...); unmount returns Temporary Plugin <id> was unmounted and removed. The submitted program remains in assistant tool-call history.
Token effect
Inspect output and mount code are data-dependent and resent until compaction; lifecycle acknowledgements are small.
KV Cache effect
Append-only; newly visible content follows the reusable request prefix and does not invalidate existing KV-cache entries.
Later requests after cordis_mount
What the model sees
A temporary Plugin may register tools, prompt contributions, or listeners that change later requests for the scopes it targets; cordis_unmount removes those contributions after quiescence.
Token effect
Indirect token impact equals the temporary Plugin's contributions and lasts only for its process-local lifetime.
KV Cache effect
Mounting or unmounting a prompt or tool contribution changes later request prefixes and may invalidate reuse from the first changed contribution; an unchanged temporary-Plugin set remains prefix-stable.
Known Limitations and Deferred Work
- The sandbox is containment for honest code, not a security boundary — host-realm helpers on the sandbox global are reachable, so mount code can reach Node; load this plugin as deliberately as you would grant a bash tool (see § Trust stance).
- The
ctxfaçade exposes noeffect()— mount code cannot register a bespoke disposer;on/provide/tools.registercover every mount seen so far, and a guardedeffectwaits on a real need (FIXME(sandbox-effect)). vmTimeoutMsbounds only synchronous evaluation — an async mount body escapes it; there is no async budget on mount code.