mirror of
https://github.com/deepseek-ai/deepseek-harness
synced 2026-08-15 21:04:50 +00:00
ab8dc1ec72
The RFC seated the exit approval on the approval seam because that was the only asking machinery in flight when it was written. ask_user_question has since merged (PR #108): the exit moment is a question, not a permission — the user-interaction seam gives the review options plus a free-text channel, so a keep-planning answer carries the user's feedback to the model verbatim, and an approval can later grow options. The gate no longer returns ask (that vocabulary stays free for genuine permission gating); the tool conducts the review inside its own execution and degrades to manual mode-toggling without a provider. The approval-seam shape moves to Alternatives considered with the reasoning. Consequences: the roadmap's hard prerequisite on the sandbox branch disappears (this stack bases on master), the recorded scenarios script elicitation answers instead of permission answers, and the ACP v2 session-mode-removal direction is recorded as an accepted migration risk.
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.