kingwl
5a8e3a14ee
The proposal survives contact with the code with three amendments, per the RFCs-are-proposals rule. (1) A mode transition logs a request/header-delta only when expressible: adding exit_plan_mode resorts the canonical tool list, and a pure reordering has no delta form, so entering plan mode logs the full fallback snapshot — the attributability claim holds either way. (2) The proposed/ skeleton converts to the implemented grammar: Proposal → Decision, the roadmap's staging (now history) drops to the standing Deferred list, and Acceptance criteria + Risks fold into Consequences (what holds, then the accepted costs, including the ACP v2 mode-removal migration). (3) The two recorded scenarios stay pending a with-key session, recorded in Deferred. The docs tail completes: the cookbook's plan-mode row upgrades from sketch to the shipped package, architecture.md gains the ctx.modes capability row (ceiling 1640 → 1650: a new capability service's table row does not fit the old budget), and every reference repoints to implemented/.
DeepSeek Harness
English | 中文
The DeepSeek Harness SDK is a plugin-based SDK for building agent harnesses.
Development
This monorepo is built on the Cordis framework (vendored as source under vendor/), microkernel-style: everything is a plugin.
pnpm install
pnpm run test # vitest
pnpm run demo:repl # REPL agent demo (needs DEEPSEEK_API_KEY)
pnpm run demo:acp # ACP server agent demo (needs DEEPSEEK_API_KEY)
For humans, start with the development guide for local setup, hooks, environment variables, and quality gates, then read the architecture design and documentation graph index before package work. Local context lives in packages/ and vendor/.
For agents, follow AGENTS.md.