mirror of
https://github.com/deepseek-ai/deepseek-harness
synced 2026-08-15 21:04:50 +00:00
6227cfd03d
architecture.md is the behavior map: layering, service map, seam pattern, and the loop — everything else defers to its owning tier. - Seam narrations compress to two-to-four sentences plus links to the RFC and type-catalog homes that carry the detail (turn-end variant semantics -> session.md, derivation mapping -> session.md, StreamChunk conventions -> llm-streaming.md + source). - The MVP feature-to-mechanism checklist moves de-statused into the extension cookbook as 'The feature -> mechanism map' — mechanisms only, no implementation-status bolding to rot; the microkernel RFC's proof-obligation pointer follows it. - The layering diagram describes layers by family instead of enumerating packages (the stale 'future plugins: hooks, compaction' row is gone); the dependency rule defers to packages/README.md. - The loop pseudocode, the three externally-cited anchors (the vocabulary, event taxonomy, waterfall semantics), and the filename are unchanged. - Budget ratchet: docs/architecture.md 3897 -> 1800 (now 1,797 words); the doc-tiers RFC's deferred list prunes the item this ships.
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 before package work. Local context lives in packages/ and vendor/.
For agents, follow AGENTS.md.