7e95a00c8a
A max-tokens response that included a tool call persisted assembler-transformed content next to replay metadata projected from the untransformed native message, so the next request died in history reconstruction with INVALID_REPLAY_STATE and the session stayed permanently stuck. Write side: the finish chunk's replayState becomes a typed ReplayEnvelope — opaque response-level metadata plus optional per-block entries aligned with the emitted block sequence. BlockAssembler computes one keep/drop decision for blocks and entries together, so stored metadata always describes stored content and retained blocks keep their signatures. pi-ai splits its state into a version-2 response half and per-block signature entries. Read side: durable content is authoritative. toPiAssistant degrades any unusable state — foreign kind, other versions (including the flat v1 form already on disk), malformed metadata, or content/block mismatches — to the existing provider-neutral conversion with an onReplayDegrade diagnostic instead of failing the request, which un-bricks sessions poisoned before this change. Covered by assembler and replay unit tests, an agent-loop continuation regression, keyless real-composition continuation tests (native pruned-envelope replay and legacy flat-state degrade), and the authored keyless snapshot scenario max-tokens-continue through the assembled ACP app. |
||
|---|---|---|
| .. | ||
| tests | ||
| advanced.cordis.snapshot.yml | ||
| advanced.cordis.yml | ||
| agent-instructions.cordis.snapshot.yml | ||
| agent-instructions.cordis.yml | ||
| background-job-admission.cordis.snapshot.yml | ||
| background-job-admission.cordis.yml | ||
| both-mode.cordis.snapshot.yml | ||
| both-mode.cordis.yml | ||
| child-question.cordis.snapshot.yml | ||
| child-question.cordis.yml | ||
| code-mode-workspace-context.cordis.snapshot.yml | ||
| code-mode-workspace-context.cordis.yml | ||
| code-mode.cordis.snapshot.yml | ||
| code-mode.cordis.yml | ||
| composition.md | ||
| cordis-tools.cordis.yml | ||
| cordis.snapshot.yml | ||
| cordis.yml | ||
| depth-two.cordis.snapshot.yml | ||
| depth-two.cordis.yml | ||
| fs.cordis.snapshot.yml | ||
| fs.cordis.yml | ||
| image-text-route.cordis.snapshot.yml | ||
| image-text-route.cordis.yml | ||
| image.cordis.snapshot.yml | ||
| image.cordis.yml | ||
| package.json | ||
| partial-landlock.cordis.snapshot.yml | ||
| partial-landlock.cordis.yml | ||
| product-subagent-both.cordis.snapshot.yml | ||
| product-subagent-both.cordis.yml | ||
| product-subagent-codex.cordis.snapshot.yml | ||
| product-subagent-codex.cordis.yml | ||
| pty-snapshot-backend.mjs | ||
| pty.cordis.snapshot.yml | ||
| pty.cordis.yml | ||
| README.i18n.yaml | ||
| README.md | ||
| README.zh.md | ||
| retry.cordis.snapshot.yml | ||
| retry.cordis.yml | ||
| session-query.cordis.snapshot.yml | ||
| session-query.cordis.yml | ||
| session-sandbox-root.cordis.snapshot.yml | ||
| session-sandbox-root.cordis.yml | ||
| session-title.cordis.snapshot.yml | ||
| session-title.cordis.yml | ||
| subagent-continuable-inheritance.cordis.snapshot.yml | ||
| subagent-continuable-inheritance.cordis.yml | ||
| subagent-durability-failure.cordis.snapshot.yml | ||
| subagent-durability-failure.cordis.yml | ||
| subagent-report-quiet.cordis.snapshot.yml | ||
| subagent-report-quiet.cordis.yml | ||
| web-fetch-fixture-server.mjs | ||
| web.cordis.snapshot.yml | ||
| web.cordis.yml | ||
acp-agent example
English | 中文
Automation-oriented Agent Client Protocol server over JSON-RPC stdio. It is intended for parent agents, subagent providers, and other programmatic clients, not as the product UI.
pnpm run demo:acp # needs DEEPSEEK_API_KEY (repo-root .env or env)
pnpm run demo:code-mode # same protocol with the Code Mode tool transport
The leaf loads the ACP app, DeepSeek adapter, sandboxed bash and filesystem stacks, one-shot approval policy, compaction, subagents, workflows, hooks, a derived session-query index, and repeat guard. The app creates one fresh agent per session/new, persists sessions to JSONL, and keeps stdout protocol-pure. Optional overlays add session queries, filesystem spill storage, Code Mode, or web fetching.
Protocol channel
Stdout carries only newline-delimited ACP JSON-RPC. @deepseek-ai/dsh-acp-demo installs no stdout logger; leaf additions must use stderr for diagnostics.
The automation contract — supported methods, baseline prompt content, committed-text output, and the intentionally absent UI surfaces — lives in @deepseek-ai/dsh-acp.
Session workspaces and permissions
Each session/new supplies an absolute cwd. Sandboxed bash and filesystem mutations resolve workspace-write against that session cwd, so concurrent sessions can use separate project roots; platform temporary roots remain shared writable scratch space (sandbox contract). DSH_PERMISSION_MODE selects workspace-write or danger-full-access for the deployment.
Under workspace-write, a model retry requesting wider sandbox access triggers session/request_permission with allow_once and reject_once. The client decides programmatically; dismissal or an unavailable answer fails closed. The selected outcome applies only to that retry and is recorded through the normal tool-result/audit path. The server never exposes a permission picker or persists client policy.