The session_projcache domain declares compatibleVersions: [3, 4] and invalidRecords: 'backup-and-skip'. The two lineage identity fields become optional — records admitted from older versions predate them, and the single reader (identityMatches) interprets absence as the unseeded lineage: exact for unseeded sessions, while a seeded caller fails the match and refolds cold, so the lineage binding keeps its protection. Upgraded homes therefore boot and serve their cached listing titles immediately, including homes whose new tree already holds current-stamped documents without lineage fields, and a record failing validation anyway is backed up and skipped instead of refusing the plugin tree. tests/fixtures/ archives the real on-disk media of every shipped generation (v3 whole-unit file, v4 and v5 per-record documents, and the lineage-less current-stamped shape); fixtures.spec.ts proves each recovers through the real storage stack, rewrites to the current format on the next live write, and that a hopeless record is salvaged without costing the boot. |
||
|---|---|---|
| .agents | ||
| .claude | ||
| .github | ||
| apps | ||
| docs | ||
| native | ||
| packages | ||
| patches | ||
| python | ||
| scripts | ||
| snapshots | ||
| vendor | ||
| website | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .jscpd.json | ||
| .oxlintrc.json | ||
| .oxlintrc.staged.json | ||
| .rgignore | ||
| AGENTS.md | ||
| BENCHMARK.md | ||
| BRAND_GUIDELINES.i18n.yaml | ||
| BRAND_GUIDELINES.md | ||
| BRAND_GUIDELINES.zh.md | ||
| CLAUDE.md | ||
| CONTRIBUTING.i18n.yaml | ||
| CONTRIBUTING.md | ||
| CONTRIBUTING.zh.md | ||
| lefthook.yml | ||
| LICENSE | ||
| package.json | ||
| pnpm-lock.yaml | ||
| pnpm-workspace.yaml | ||
| pytest.ini | ||
| README.i18n.yaml | ||
| README.md | ||
| README.zh.md | ||
| SAFETY.i18n.yaml | ||
| SAFETY.md | ||
| SAFETY.zh.md | ||
| THIRD_PARTY_NOTICES.md | ||
| tsconfig.base.client.json | ||
| tsconfig.base.json | ||
| tsconfig.client.json | ||
| tsconfig.host.json | ||
| tsconfig.json | ||
| tsdown.config.ts | ||
| vitest.config.ts | ||
| vitest.e2e.config.ts | ||
| vitest.expected.config.ts | ||
| vitest.shared.ts | ||
| vitest.snapshot.config.ts | ||
| vitest.web-stress.config.ts | ||
| vitest.web.config.ts | ||
| vitest.web.perf.config.ts | ||
DeepSeek Harness
English | 中文
DeepSeek Harness (dsh) is an open-source agent harness developed by DeepSeek AI.
It is built on an everything-is-a-plugin architecture and powered by Cordis, whose design is described in A Programming Paradigm for Spatiotemporal Composability.
Documentation: https://deepseek-harness.github.io/deepseek-harness/
Developer preview
DeepSeek Harness is in developer preview and iterating rapidly. THERE WILL BE COMPATIBILITY-BREAKING CHANGES.
Review the safety notice before running the project.
Run
Run from npm
Install Node.js, then run:
npx @deepseek-ai/dsh web
The command starts the Web UI at http://127.0.0.1:3080 by default and opens it in the default browser for a local launch. An SSH launch only prints the host URL because the SSH client or editor owns the local forwarded address. Pass --no-open to run the server without opening a browser. See Web UI guide.
Run from source
To run from a repository checkout:
git clone https://github.com/deepseek-ai/deepseek-harness.git
cd deepseek-harness
pnpm install
pnpm run build
pnpm dsh web
pnpm run build prepares the repository artifacts. pnpm dsh web uses those built artifacts without rebuilding.
Community and support
- Submit feedback or bug reports through GitHub Discussions.
- Add the
dsh-plugintopic to your plugin repository for discoverability. - Join DeepSeek Harness Discord community.
Contributing
See CONTRIBUTING.md.
Development
Start with the development guide and architecture documentation.
For agents, follow AGENTS.md.
License
Third-party dependencies and their licenses are disclosed in THIRD_PARTY_NOTICES.md.