@dsh-cc/tui 0.5.0

package/presets/cc/agent.cordis.yml

@@ -0,0 +1,524 @@
+# BEGIN dsh-cc header
+# vendored from @deepseek-ai/dsh@0.1.1-rc.2 config/agent-presets/standard/agent.cordis.yml
+# source: config/agent-presets/standard/agent.cordis.yml (deepseek-harness install)
+#
+# This file is the dsh "CC mode" agent preset composition. The baseline below
+# is a verbatim copy of the standard preset; the `cc rows` section appended at
+# the bottom carries the CC surface rows scoped to this preset (they previously
+# lived in the cc-shell global patch, see
+# $R/packages/bundle/cc-shell/cordis.patch.yml).
+#
+# After upgrading dsh upstream, re-diff this baseline against the new standard
+# preset (the drift gate in tests/composition.spec.ts automates this) and fold
+# in any upstream changes.
+# END dsh-cc header
+# The `standard` agent preset: the full coding agent, mounted once per process.
+#
+# 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` + `web.cordis.yml`) 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.)
+
+# ── 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: `apps/cli/src/web.ts` injects it to
+# publish `DSH_WEB_URL`/`DSH_WEB_MODE`, and 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. Behind a preset realm those variables
+# never reached the model's shell at all. 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'
+
+# ── 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, its session driver, and the
+# `/goal` command stay on the host plane: the Gateway serves the goal domain as
+# Remote endpoints whose receiver comes from a generated descriptor, so it
+# resolves `goals` on the host and an entry-local realm here would hide it. 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.
+#
+# The engine and the command are CC replacements for the upstream rows: the
+# engine subclass folds a per-agent `/compact [instructions]` hint into the
+# summarizer input; the command forwards the free-text argument as that hint
+# instead of rejecting arguments.
+#
+# `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
+# browser 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` below.
+- id: compaction
+  name: cordis:group
+  group: true
+  isolate:
+    compaction: true
+    toolResultPruner: true
+  config:
+    - id: compaction-basic
+      name: '@dsh-cc/compaction-basic'
+
+    - id: command-compact
+      name: '@dsh-cc/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 whose cross-session queries
+# the api-proxy serves to the browser, 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.
+#
+# `tool-subagent` and `tool-subagent-fork` (the harness spawn/fork Task tools)
+# are DISABLED here — the CC Task tool is provided by the `tool-task` row in
+# the cc-services group instead. That replacement Task now implements the
+# continuable loop itself: `run_in_background: true` starts a durable
+# background child on the spawn provider, and report / send_message /
+# list_agents / interrupt_agent operate on its returned agentId. The harness
+# rows stay disabled. Note for future readers: the disabled
+# `tool-subagent-fork` row's `backgroundMode: continuable` config is inert
+# while the row is disabled, and fork children remain foreground one-shot
+# until upstream harness issue #2124 resolves.
+- 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'
+      disabled: true
+      config:
+        provider: spawn
+        toolName: subagent
+        backgroundMode: continuable
+
+    - id: tool-subagent-fork
+      name: '@deepseek-ai/dsh-tool-subagent'
+      disabled: true
+      config:
+        provider: fork
+        toolName: subagent_fork
+        backgroundMode: continuable
+
+    # Production dsh does not install these optional providers. Install the
+    # matching Bundle in this Profile and restart the Host, then copy this
+    # preset and remove `disabled` from the matching tool row. Host availability
+    # alone grants no tool.
+    - id: tool-subagent-codex
+      name: '@deepseek-ai/dsh-tool-subagent'
+      disabled: true
+      config:
+        provider: codex
+        toolName: subagent_codex
+        backgroundMode: one-shot
+        maxDepth: provider-managed
+
+    - id: tool-subagent-claude-code
+      name: '@deepseek-ai/dsh-tool-subagent'
+      disabled: true
+      config:
+        provider: claude-code
+        toolName: subagent_claude_code
+        backgroundMode: one-shot
+        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 search provider stay in the host composition; only
+# the model-facing tool is per-session.
+#
+# Moved in from the cc-shell global swap. fetch is still disabled here because
+# `@dsh-cc/tool-web-fetch` inside cc-services owns the model-facing tool
+# (adds the optional `prompt`). The HTTP executor is
+# `@dsh-cc/web-fetch-http` mounted from cc-shell (literal SSRF gate).
+# A prompt without the `haiku` route hard-fails.
+- id: tool-web
+  name: '@deepseek-ai/dsh-tool-web'
+  config:
+    fetch: false
+    searchTimeoutMs: 60000
+
+# ── cc rows ─────────────────────────────────────────────────────────────────
+
+# The CC surface rows, scoped to this preset. They previously lived in the
+# cc-shell global patch ($R/packages/bundle/cc-shell/cordis.patch.yml) and are
+# moved here so they no longer leak into every agent preset that mounts the
+# global host composition.
+
+# Service rows MUST sit in a group with an `isolate` realm: mounting this preset
+# rejects any row that publishes a cordis Service into the root realm
+# (PresetMountError / leakedServices). The isolate keys below are all required —
+# the glue dynamically attaches mcp-client as a sub-fiber, and `Context.extend`
+# inherits the group's isolate map down the prototype chain, so without
+# `mcpConnections` isolated here it would publish into the root realm and break
+# the preset. The command rows and the `memory` / `hooks-claude-code` consumers
+# must live INSIDE the group: they `ctx.get('ccModelRoutes')` (and
+# `ctx.get('mcpConnections')`), which resolve to nothing outside the isolated
+# realm. `ccPlugins` is deliberately NOT isolated: the glue publishes it into
+# the ROOT realm from the root fiber (see CcPluginsService in
+# @dsh-cc/bundle-shell) so host-plane siblings — the TUI driver and /help
+# — can resolve it; isolating the name here would shadow that publication and
+# break in-group resolution too.
+- id: cc-services
+  name: cordis:group
+  group: true
+  isolate:
+    toolSearch: true
+    microcompactor: true
+    ccModelRoutes: true
+    resumePinStore: true
+    mcpConnections: true
+    hookBridgeStatus: true
+  config:
+    # ToolSearch: model-called search that activates deferred tools per scope.
+    - id: tool-search
+      name: '@dsh-cc/tool-search'
+
+    # Model-free staleness microcompaction (auto: false by default).
+    - id: compaction-micro
+      name: '@dsh-cc/compaction-micro'
+
+    # CC plugins on disk (agents/skills/commands/hooks/mcp servers) plus the
+    # base agent preset dirs and .mcp.json server wiring — see the glue plugin.
+    - id: cc-shell-glue
+      name: '@dsh-cc/bundle-shell'
+
+    - id: command-plugin
+      name: '@dsh-cc/command-plugin'
+
+    - id: command-mcp
+      name: '@dsh-cc/command-mcp'
+
+    # Serena-first prompt steering: while a serena MCP server is ready
+    # (registry-only, live detection over the isolated `mcpConnections`
+    # above), the registered `serena-first` section (order 105) renders the
+    # policy paragraph and the assemble waterfall rewrites the upstream
+    # `tool:read` / `tool:grep` texts (replace-not-mutate, `{ prepend: true }`).
+    # Publishes no Service, so it needs no isolate key of its own;
+    # `systemPrompt` resolves through the group via the prototype chain.
+    # `serverName` config (default 'serena') drives detection and every
+    # emitted `mcp__<serverName>__*` name.
+    - id: serena-first
+      name: '@dsh-cc/serena-first'
+
+    # /doctor reads ccModelRoutes, mcpConnections, and hookBridgeStatus, so it
+    # shares the group realm.
+    - id: command-doctor
+      name: '@dsh-cc/command-doctor'
+
+    # cc-model-routes owns the model-aliases settings namespace and resolver;
+    # tool-task provides the CC Task tool (subagent_type dispatch over
+    # per-workspace .claude/agents) and reserves the names 'subagent'/'workflow'.
+    - id: cc-model-routes
+      name: '@dsh-cc/model-aliases'
+
+    # Resume pins (plan docs/plans/2026-09-04-subagent-resume-pins.md §4.10):
+    # one PinStore + the resume gate/overlay/policy per mounted preset, exposed
+    # as the `resumePinStore` service (isolated above, like ccModelRoutes). The
+    # pins root COLOCATES with the session-persistence root: the harness base
+    # patch mounts the jsonl backend at `!!js dshHomePath('sessions')`, and this
+    # `!!js` expression resolves `dshHomePath` the same way at entry activation
+    # (app-boot provides it on the root ctx before the config tree mounts), so
+    # pins always sit next to the durable sessions they pin. Must mount BEFORE
+    # tool-task: the Task plugin's spawn capture prefers this service store.
+    - id: cc-resume-pins
+      name: '@dsh-cc/subagent-resume-pins'
+      config:
+        pinsRoot: !!js dshHomePath('sessions', 'resume-pins')
+
+    - id: tool-task
+      name: '@dsh-cc/subagent-task'
+
+    # /agents: query/control surface for continuable background children
+    # (plan docs/plans/2026-09-10-continuable-background-ux.md §3.2). Mounts
+    # INSIDE cc-services (F8): the read-only snapshot joins the realm-interior
+    # resumePinStore with the host-plane subagents/agents registries, then
+    # republishes the snapshot as the ROOT-realm `ccAgents` service (CcPlugins
+    # pattern) so the TUI local-slash path consumes the SAME snapshot. Must
+    # mount AFTER cc-resume-pins.
+    - id: command-agents
+      name: '@dsh-cc/command-agents'
+
+    # Memory and the hook bridge consume `ctx.get('ccModelRoutes')` at spawn
+    # time (recall small-fast lane / hook model resolution), so they share this
+    # realm. memory-consolidation stays OUTSIDE: its forks must keep inheriting
+    # the parent route. memory still publishes no cordis Service;
+    # hooks-claude-code now provides `hookBridgeStatus` (for /doctor), which is
+    # isolated on this group's isolate map — both stay mount-legal under the
+    # leakedServices gate only because they sit INSIDE the group.
+    - id: memory
+      name: '@dsh-cc/memory'
+
+    - id: hooks-claude-code
+      name: '@dsh-cc/hooks-claude-code'
+      # Tracked root-level hook config (serena code-intelligence plan Phase 0).
+      # Relative configPath resolves against the process launch cwd, so a
+      # worktree session started at the worktree root loads it by construction.
+      config:
+        configPath: hooks.json
+
+    # Replaces the stock dsh-tool-web web_fetch (fetch: false above): adds the
+    # optional `prompt`, summarized on the cheap lane when the haiku alias is
+    # configured; degrades to raw converted text + notice otherwise.
+    - id: tool-web-fetch
+      name: '@dsh-cc/tool-web-fetch'
+
+# ── parallel rows ──────────────────────────────────────────────────────────
+
+# Claude Code skills from user/project/additional roots.
+- id: skill-claude-code
+  name: '@dsh-cc/skill-loader'
+
+- id: memory-consolidation
+  name: '@dsh-cc/memory-consolidation'
+
+# Render CLAUDE.md-style output styles to the system prompt.
+- id: cc-output-styles
+  name: '@dsh-cc/output-styles'
+
+# Coordinator mode: DSH_COORDINATOR_MODE=1 or config enabled.
+- id: coordinator
+  name: '@dsh-cc/coordinator'
+
+- id: schedule
+  name: '@deepseek-ai/dsh-schedule'
+
+- id: session-cwd
+  name: '@dsh-cc/session-cwd'
+
+- id: tool-git-worktree
+  name: '@dsh-cc/tool-git-worktree'
+
+- id: tool-sleep
+  name: '@dsh-cc/tool-sleep'
+
+# NotebookEdit: edits Jupyter notebook (.ipynb) cells over the ctx.fs seam
+# with CC's replace/insert/delete, cell addressing, and read-before-write gate.
+- id: tool-notebook-edit
+  name: '@dsh-cc/tool-notebook-edit'
+
+# StructuredOutput: non-interactive structured-final-response channel, registered
+# only when the deployment declares a schema (CC's SyntheticOutputTool).
+- id: tool-structured-output
+  name: '@dsh-cc/tool-structured-output'
+
+# ── CC parity slash commands ───────────────────────────────────────────────
+
+- id: command-cost
+  name: '@dsh-cc/command-cost'
+  config:
+    # Composition decides pricing → the package schema stays strict; ship an
+    # empty price table by default (README "Known limits" /cost entry).
+    modelTable: []
+
+- id: command-export
+  name: '@dsh-cc/command-export'
+
+- id: command-stats
+  name: '@dsh-cc/command-stats'
+
+- id: command-status
+  name: '@dsh-cc/command-status'
+
+- id: command-memory
+  name: '@dsh-cc/command-memory'
+
+- id: command-skills
+  name: '@dsh-cc/command-skills'
+
+- id: command-help
+  name: '@dsh-cc/command-help'
+
+- id: command-config
+  name: '@dsh-cc/command-config'
+
+- id: command-permissions
+  name: '@dsh-cc/command-permissions'
+
+- id: command-version
+  name: '@dsh-cc/command-version'
+
+- id: command-release-notes
+  name: '@dsh-cc/command-release-notes'
+
+- id: command-diff
+  name: '@dsh-cc/command-diff'
+
+- id: command-init
+  name: '@dsh-cc/command-init'
+
+- id: command-tasks
+  name: '@dsh-cc/command-tasks'
+
+- id: command-resume
+  name: '@dsh-cc/command-resume'
+
+- id: command-rename
+  name: '@dsh-cc/command-rename'
+
+- id: command-branch
+  name: '@dsh-cc/command-branch'
+
+# Cache-stable tool ordering: remembers each scope's last emitted tool-name
+# sequence on the system-prompt/assemble waterfall and appends newly appeared
+# tools (ToolSearch activations, MCP registrations) lexicographically at the
+# tail, so an activation extends the request prefix instead of shifting every
+# tool after the insertion point. cordis waterfall is outermost-first and the
+# outermost listener has the final say, so the plugin registers its assemble
+# listener with `prepend` to stay outermost regardless of row position; the
+# row itself stays last because the composition drift gate expects cc rows at
+# the bottom (the Item 6 L0 prefix-stability e2e is the sentinel).
+# Publishes no Service, so it needs no isolate realm.
+- id: tool-append-order
+  name: '@dsh-cc/tool-append-order'

package/presets/cc/preset.yml

@@ -0,0 +1,3 @@
+name: CC mode
+description: Full Standard-mode capability, plus the Claude Code surface — .claude plugin directories, Claude hooks, slash commands, persistent memory, output styles, and fetch-enabled Web tools.
+order: 5

package/scripts/stage-preset.mjs

@@ -0,0 +1,26 @@
+#!/usr/bin/env node
+/**
+ * Copy packages/preset/cc/{agent.cordis.yml,preset.yml} into this package's
+ * presets/cc so the published tarball can materialize the user-root preset.
+ */
+import { cpSync, mkdirSync, existsSync, writeFileSync } from 'node:fs'
+import { dirname, join } from 'node:path'
+import { fileURLToPath } from 'node:url'
+
+const here = dirname(fileURLToPath(import.meta.url))
+const pkgRoot = join(here, '..')
+const repoPreset = join(pkgRoot, '..', '..', 'preset', 'cc')
+const dest = join(pkgRoot, 'presets', 'cc')
+
+if (!existsSync(join(repoPreset, 'agent.cordis.yml'))) {
+  console.error(`stage-preset: missing ${join(repoPreset, 'agent.cordis.yml')}`)
+  process.exit(1)
+}
+
+mkdirSync(dest, { recursive: true })
+cpSync(join(repoPreset, 'agent.cordis.yml'), join(dest, 'agent.cordis.yml'))
+cpSync(join(repoPreset, 'preset.yml'), join(dest, 'preset.yml'))
+writeFileSync(
+  join(dest, '.dsh-cc-managed.json'),
+  `${JSON.stringify({ owner: '@dsh-cc/tui', preset: 'cc', revision: '0.1.0' }, null, 2)}\n`,
+)