codsh-cli 0.2.0 → 0.3.0

package/agent-presets/code-cli/agent.cordis.yml

@@ -1,322 +0,0 @@
-# The `code-cli` agent preset: the `standard` coding agent plus the capabilities a
-# terminal surface needs — persistent terminal sessions, optional LSP code
-# navigation, and web fetch.
-#
-# This file is an AGENT-PLANE composition. The roster mounts it ONCE under a
-# standing scope; every session naming it joins by scope parentage, so the
-# tools and prompt sections registered here cover each joined agent while a
-# session's own state stays keyed per Session/Agent inside the plugins. The
-# host composition (`base.cordis.yml` + the `dsh-coding-cli` bundle patch) keeps
-# everything a preset must not own: the registries themselves, the sandbox and
-# approval stack, persistence, and the model route.
-#
-# A service row here MUST sit inside a group carrying an `isolate` realm.
-# Without one it publishes into the root realm, where it is process-global —
-# another preset publishing the same name collides, and a host reader would
-# resolve one preset's instance for every session; `dsh-agent-presets` rejects
-# that at mount. `true` means an entry-local realm: this standing mount's own
-# private instance, apart from every other preset's. (A shared label does NOT
-# pool instances — `provide()` throws on the second registration under the
-# same realm symbol; labels join REALMS, and are not what this file needs.)
-#
-# The `app:cli-surface` prompt section that orients the model to the terminal
-# belongs to the `dsh-coding-cli` bundle, not here: it describes the surface
-# that booted the process, and every preset a terminal session mounts needs it.
-
-# ── identity ────────────────────────────────────────────────────────────────
-
-# The preset's own persona, shadowing the deployment default for this agent.
-# `{{model}}` and `{{cwd}}` resolve from the agent's own route and workspace.
-- id: persona
-  name: '@deepseek-ai/dsh-persona'
-  config:
-    text: >-
-      You are a coding agent powered by the {{model}} model. Your working directory is {{cwd}}.
-
-- id: agent-instructions
-  name: '@deepseek-ai/dsh-agent-instructions'
-  config:
-    maxBytes: 65536
-
-# ── shell ───────────────────────────────────────────────────────────────────
-
-# `shell-env` stays in the HOST composition: a host row that injects a service is
-# the criterion for host-plane ownership — injection resolves before any session
-# exists, so there is no agent to key by. Both shell tools consume the host
-# registry from here; their executors (`bash-sandbox`/`pwsh-sandbox`) are
-# host-plane too.
-- id: tool-bash
-  name: '@deepseek-ai/dsh-tool-bash'
-  disabled: !!js process.platform === 'win32'
-
-- id: tool-pwsh
-  name: '@deepseek-ai/dsh-tool-pwsh'
-  disabled: !!js process.platform !== 'win32'
-
-# ── persistent terminals ────────────────────────────────────────────────────
-
-# `terminals` is an agent-owned registry, so it lives in an entry-local realm;
-# the backend still consumes the host sandbox policy and subprocess
-# implementation. A terminal outlives one tool call, which is what separates it
-# from `tool-bash`: the agent starts a dev server, a watcher, or a REPL and
-# reads from it across turns instead of blocking a call until the process exits.
-#
-# `dsh-terminal-bash` is the only shipped backend, so the whole group is off on
-# Windows — `tool-terminal` without a backend would answer every `terminal_open`
-# with an unavailable registry rather than a missing tool.
-- id: terminals
-  name: cordis:group
-  group: true
-  disabled: !!js process.platform === 'win32'
-  isolate:
-    terminals: true
-  config:
-    - id: pty
-      name: '@deepseek-ai/dsh-terminal'
-
-    - id: terminal-bash
-      name: '@deepseek-ai/dsh-terminal-bash'
-      config:
-        timeoutMs: 300000
-
-    - id: tool-terminal
-      name: '@deepseek-ai/dsh-tool-terminal'
-
-# ── code navigation ─────────────────────────────────────────────────────────
-
-# `lsp` is an agent-owned provider registry, so it and its stdio provider share
-# one entry-local realm with the tool that reads them.
-#
-# The group is off by default because `lsp-stdio` spawns `command` from the host
-# PATH: enabling it on a machine without that binary turns every `lsp` call into
-# a spawn failure. Install the server, then delete the `disabled` line below.
-# The `servers` table maps stable provider ids to independent local servers, and
-# each provider reserves its `extensionToLanguage` extensions exclusively.
-- id: code-navigation
-  name: cordis:group
-  group: true
-  disabled: true
-  isolate:
-    lsp: true
-  config:
-    - id: lsp
-      name: '@deepseek-ai/dsh-lsp'
-
-    - id: lsp-stdio
-      name: '@deepseek-ai/dsh-lsp-stdio'
-      config:
-        servers:
-          typescript:
-            command: typescript-language-server
-            args: ['--stdio']
-            extensionToLanguage:
-              .ts: typescript
-              .tsx: typescriptreact
-              .mts: typescript
-              .cts: typescript
-              .js: javascript
-              .jsx: javascriptreact
-              .mjs: javascript
-              .cjs: javascript
-
-    - id: tool-lsp
-      name: '@deepseek-ai/dsh-tool-lsp'
-
-# ── filesystem ──────────────────────────────────────────────────────────────
-
-# Both register into the host `tools` registry and provide nothing, so
-# they need no realm. The `fs` service and its policy stay in the host.
-- id: tool-fs
-  name: '@deepseek-ai/dsh-tool-fs'
-
-- id: tool-fs-search
-  name: '@deepseek-ai/dsh-tool-fs-search'
-  config:
-    sampleOverCapGlobResults: false
-
-# ── background jobs ────────────────────────────────────────────────────────
-
-# Only the model-facing controls. The task REGISTRY stays on the host plane:
-# its producers sit outside any realm this file could put it in — `tool-bash`
-# above resolves it with `ctx.get`, and an entry-local realm here is invisible
-# to every sibling row, so `run_in_background` would answer "background jobs
-# unavailable" while these controls sat in the catalog. The registry is keyed by
-# owning agent anyway, so one host instance serves every session. What a preset
-# chooses is whether its agent can collect and stop background work at all.
-- id: tool-jobs
-  name: '@deepseek-ai/dsh-tool-jobs'
-
-# ── skills ──────────────────────────────────────────────────────────────────
-
-# The skill REGISTRY lives in the host composition and is layered per scope:
-# these rows register into THIS preset's layer of it, so they need no realm.
-# `skill-filesystem` contributes local-root discovery for agents on this preset, and
-# `tool-skill` gives them the catalog and loader; the merged catalog also
-# carries whatever the deployment registered globally (repository plugins).
-- id: skill-filesystem
-  name: '@deepseek-ai/dsh-skill-filesystem'
-
-- id: tool-skill
-  name: '@deepseek-ai/dsh-tool-skill'
-
-# ── goals ───────────────────────────────────────────────────────────────────
-
-# Only the model-facing tool. The goal SERVICE and its session driver stay on
-# the host plane; the registry is keyed by session anyway, so one host instance
-# serves every session. What a preset chooses is whether its agent can call the
-# goal tool.
-- id: tool-goal
-  name: '@deepseek-ai/dsh-tool-goal'
-
-# ── plan mode ───────────────────────────────────────────────────────────────
-
-# Plan state is per-agent by nature, so an entry-local realm is not a
-# workaround here — it is the correct lifetime.
-- id: planning
-  name: cordis:group
-  group: true
-  isolate:
-    planMode: true
-  config:
-    - id: plan-mode
-      name: '@deepseek-ai/dsh-plan-mode'
-      config:
-        section: |
-              You are in plan mode. Stay in plan mode until exit_plan_mode succeeds or the user switches the session mode. Imperative language to implement changes means plan the implementation, not execute it. A user's conversational agreement — including an answer confirming something you asked — approves nothing and does not end plan mode; fold the confirmed decision into the plan and submit it through exit_plan_mode.
-
-              Explore first. Use non-mutating reads, searches, static analysis, and checks to ground the plan in the actual repository. Do not edit or write files, change configuration, run formatters or code generation that rewrites tracked files, commit, or otherwise carry out the plan. Prefer existing functions and patterns over new machinery.
-
-              The tool catalog stays the same across modes for request-cache stability. These plan-mode rules override any later tool description or guidance that suggests using mutation tools; those tools remain listed to keep the tool catalog unchanged. Do not use todo_write to track this planning phase: it tracks implementation after an approved plan, while the plan itself belongs in exit_plan_mode.
-
-              Resolve discoverable facts by inspection. Use ask_user_question only for user-owned choices or material ambiguity that inspection cannot answer. Do not ask the user where code lives or how current behavior works when you can find out.
-
-              Make the plan decision-complete: state the goal and success criteria; group implementation changes by subsystem; identify public API, schema, and data-flow changes; cover edge cases, failure modes, tests, acceptance criteria, and explicit assumptions. Keep it concise enough to review but detailed enough that another engineer can implement it without making design decisions.
-
-              When ready, call exit_plan_mode with the complete plan markdown, starting with a # title. Make exit_plan_mode the only and final tool call in that assistant response: it presents the plan for approval, and implementation begins only in a later step after approval. Do not paste the final plan as a plain reply or ask "should I proceed?" through prose or ask_user_question. If review rejects it, incorporate the feedback and present again. If the review channel is unavailable or aborted, stay in plan mode and ask the user to switch modes manually; do not proceed with implementation.
-
-# ── compaction ──────────────────────────────────────────────────────────────
-
-# `compaction-basic` reads `toolResultPrune` through `ctx.get`, so the pruner must
-# share this realm rather than sit outside it.
-#
-# `tokenMeter` is deliberately NOT in this realm: the meter stays on the HOST
-# plane, and the rows here resolve that one instance. It takes no configuration,
-# keys every fold by Session, and owns the context-meter projection units the
-# terminal status line reads for every session — behind a realm those units
-# would come and go with whichever presets happen to be mounted. What a preset
-# chooses is whether its agent compacts at all, which is `compaction-basic`.
-- id: compaction
-  name: cordis:group
-  group: true
-  isolate:
-    compaction: true
-    toolResultPruner: true
-  config:
-    - id: compaction-basic
-      name: '@deepseek-ai/dsh-compaction-basic'
-
-    - id: command-compact
-      name: '@deepseek-ai/dsh-command-compact'
-
-    - id: tool-result-pruner
-      name: '@deepseek-ai/dsh-compaction-tool-result-pruner'
-      config:
-        thresholdChars: 8192
-        headChars: 4096
-        tailChars: 1024
-
-# ── delegation and workflows ────────────────────────────────────────────────
-
-# The `subagents` registry and its spawn/fork backends live in the HOST
-# composition: the registry is a process singleton, and a provider name may only
-# be registered once. This preset contributes the delegation TOOLS, which
-# resolve that host registry.
-#
-# `workflows` is different — nothing outside an agent reads it — so every row
-# that reaches it shares one entry-local realm here, and a consumer left
-# outside would resolve a host registry this preset does not populate.
-#
-# `tool-subagent-report` is host-plane for the same reason as the registry,
-# not because a preset may not want it: it registers a CONTINUABLE SETUP on
-# that singleton rather than a tool this agent calls, and the setup list is
-# not scope-aware — one copy per mounted preset means every child gets
-# `report` registered once per live session, which throws on the second.
-- id: delegation
-  name: cordis:group
-  group: true
-  isolate:
-    workflowEngine: true
-  config:
-    - id: tool-subagent-control
-      name: '@deepseek-ai/dsh-tool-subagent-control'
-
-    - id: tool-subagent-list-agents
-      name: '@deepseek-ai/dsh-tool-subagent-control/list-agents'
-
-    - id: tool-subagent
-      name: '@deepseek-ai/dsh-tool-subagent'
-      config:
-        provider: spawn
-        toolName: subagent
-        backgroundMode: continuable
-
-    - id: tool-subagent-fork
-      name: '@deepseek-ai/dsh-tool-subagent'
-      config:
-        provider: fork
-        toolName: subagent_fork
-        backgroundMode: continuable
-
-    # Product providers are host-plane singletons. Copy this preset, then
-    # remove `disabled` from either ordinary tool row to expose that product
-    # only to agents composed from the copy.
-    - id: tool-subagent-codex
-      name: '@deepseek-ai/dsh-tool-subagent'
-      disabled: true
-      config:
-        provider: codex
-        toolName: subagent_codex
-        enableRunInBackground: false
-        maxDepth: provider-managed
-
-    - id: tool-subagent-claude-code
-      name: '@deepseek-ai/dsh-tool-subagent'
-      disabled: true
-      config:
-        provider: claude-code
-        toolName: subagent_claude_code
-        enableRunInBackground: false
-        maxDepth: provider-managed
-
-    - id: workflow-worker-thread
-      name: '@deepseek-ai/dsh-workflow-worker-thread'
-      config:
-        provider: spawn
-
-    - id: tool-workflow
-      name: '@deepseek-ai/dsh-tool-workflow'
-
-    - id: tool-ralph
-      name: '@deepseek-ai/dsh-tool-ralph'
-      config:
-        subagentProvider: spawn
-        maxRounds: 64
-
-# ── remaining model-facing rows ─────────────────────────────────────────────
-
-- id: tool-ask-user
-  name: '@deepseek-ai/dsh-tool-ask-user'
-
-- id: tool-todo
-  name: '@deepseek-ai/dsh-tool-todo'
-  config:
-    allowParallelInProgress: true
-
-# The `web` service and its providers stay in the host composition; only the
-# model-facing tool is per-session. `fetch` is on here because a terminal
-# session has no browser beside it to open a result in.
-- id: tool-web
-  name: '@deepseek-ai/dsh-tool-web'
-  config:
-    fetch: true
-    searchTimeoutMs: 60000

package/agent-presets/code-cli/preset.yml

@@ -1,3 +0,0 @@
-name: 终端模式
-description: 具备标准模式的全部能力，并增加常驻终端会话与可选的 LSP 代码导航，面向 `dsh code` 的终端界面。
-order: 5

package/cordis.patch.yml

@@ -1,165 +0,0 @@
-# The codsh bundle patch: the interactive terminal surface over
-# dsh-base. It mounts no Host, HTTP server, Web runtime, or browser plugin —
-# the surface shares the process with the Agent, so it reads `ctx.agents`
-# directly instead of through the API gateway, which exists to carry
-# out-of-process clients.
-#
-# An ordinary provider plugin injects `cmdlineArgs`, parses this app's flags,
-# then the runner creates an Agent through the core registry, mounts the
-# preset the roster resolves, renders the session log to the TTY, and answers
-# approvals and questions from the keyboard.
-
-- id: system-prompt
-  config:
-    persona: >-
-      You are a coding agent powered by the {{model}} model. Your working directory is {{cwd}}.
-
-# The shared module-reload HMR row stays off; the launcher's watch-only
-# fallback still keeps the user patch layers live until the run exits.
-- id: hmr
-  disabled: true
-
-- id: tools
-  config:
-    # Keep the same temporary process-wide Code Mode opt-in as the Web surface.
-    mode: !!js process.env.DSH_TOOLS_MODE
-
-# ── per-agent rows move behind the preset ───────────────────────────────────
-#
-# Every model-facing row below is composed by the mounted preset instead, so
-# the tool registry's global layer stays empty and an agent sees exactly what
-# its preset grants. Disabling rather than deleting is deliberate: the base is
-# shared, and a row absent from a surface overlay would silently reappear the
-# day someone reorders the composition.
-#
-# `shell-env` STAYS in the host plane: a host row that injects a service is the
-# criterion for host-plane ownership — injection resolves before any session
-# exists, so there is no agent to key by.
-
-- id: tool-bash
-  disabled: true
-
-- id: tool-pwsh
-  disabled: true
-
-# The background-job REGISTRY stays on the host plane; only the model-facing
-# `job_*` controls move. Its producers are preset rows that resolve it with
-# `ctx.get`, and an entry-local realm around the registry is invisible to every
-# sibling row outside that realm. The registry is keyed by owning agent, so one
-# host instance serves every session.
-
-- id: tool-jobs
-  disabled: true
-
-- id: tool-fs
-  disabled: true
-
-- id: tool-fs-search
-  disabled: true
-
-- id: tool-str-replace-editor
-  disabled: true
-
-# The `skill` REGISTRY stays in the host plane, host+per-scope layered:
-# deployment-level providers register into its global layer while a preset's
-# `skill-filesystem` registers into that preset's layer, and each agent reads
-# the merged catalog its scope chain selects.
-
-- id: skill-filesystem
-  disabled: true
-
-- id: tool-skill
-  disabled: true
-
-# The goal SERVICE and its session driver STAY on the host plane; only the
-# model-facing tool moves. The registry is keyed by session, so one host
-# instance serves every session.
-
-- id: tool-goal
-  disabled: true
-
-- id: plan-mode
-  disabled: true
-
-# The token METER stays on the host plane; only the compaction backend that
-# reads it moves. It owns the context-meter projection units the terminal
-# status line reads, and that table is process-wide, so preset ownership would
-# make the meter a function of which presets happen to be mounted.
-
-- id: compaction-basic
-  disabled: true
-
-- id: command-compact
-  disabled: true
-
-- id: tool-result-pruner
-  disabled: true
-
-# The subagent registry and its backends STAY in the host plane. `subagents` is
-# a process singleton, and a provider registers under a globally unique name,
-# so a per-session copy would both starve that host row and collide on the
-# second session. What a preset chooses is which delegation TOOLS its agent
-# sees.
-
-- id: tool-subagent-control
-  disabled: true
-
-- id: tool-subagent-list-agents
-  disabled: true
-
-- id: tool-subagent
-  disabled: true
-
-- id: tool-subagent-fork
-  disabled: true
-
-- id: workflow-worker-thread
-  disabled: true
-
-- id: tool-workflow
-  disabled: true
-
-- id: tool-ralph
-  disabled: true
-
-- id: agent-instructions
-  disabled: true
-
-- id: tool-todo
-  disabled: true
-
-- id: tool-web
-  disabled: true
-
-- insert:
-    # Code Mode is a core execution capability, not a Web component.
-    - id: code-runtime
-      name: '@deepseek-ai/dsh-code-runtime-worker-thread'
-
-    # The preset roster. `config/agent-presets/` ships with the deployment and
-    # is read-only (its entries carry `system` trust); `$DSH_HOME/.agent-presets`
-    # is where a person — or an agent — authors their own, and carries the same
-    # trust as shell access because a preset IS a composition.
-    #
-    # Only the SHIPPED root is an assembly fact: it sits beside the installed
-    # app's own config, so `apps/cli`'s `composeProfile` resolves and patches it
-    # in. The writable root is `dsh-agent-presets`' own default
-    # (`includeUserRoot`), so a composition that never reaches that patch still
-    # finds a person's presets.
-    - id: agent-presets
-      name: '@deepseek-ai/dsh-agent-presets'
-      config:
-        default: code-cli
-
-    - id: coding-cli-startup
-      name: 'codsh-cli/startup'
-
-    # Reads its invocation from the ordinary codingCliStartup provider.
-    - id: coding-cli-runner
-      name: 'codsh-cli'
-      inject: [codingCliStartup]
-      config:
-        task: !!js ctx.codingCliStartup.task
-        resume: !!js ctx.codingCliStartup.resume
-        preset: !!js ctx.codingCliStartup.preset
-        print: !!js ctx.codingCliStartup.print