mirror of
https://github.com/deepseek-ai/deepseek-harness.git
synced 2026-08-29 04:26:38 +00:00
_Kerman
501f387b46
The json backend now serves two layouts. single (the default) keeps the whole unit as one document at <root>/<name>.json; per-record keeps one version-stamped document per record at <root>/<name>/<table>/<key>.json (plus global.json), so one write rewrites one record instead of the whole unit. The per-record unit is stateless — the directory is the state, loadAll re-reads the tree, and every write is a single durable file operation — while single keeps its authoritative in-memory state and whole-file publish. Records keys must be path-safe ([a-zA-Z0-9_-]+); an unsafe key rejects. A record document that is malformed or stamped with another version reads as an absent record: one bad or stale file never bricks the unit, and a version bump discards stale records instead of migrating them. DomainSpec and KvUnitDescriptor gain the optional layout field (defineDomain validates it, descriptorOf projects it).
DeepSeek Harness
English | 中文
DeepSeek Harness (dsh) is an open-source agent harness developed by DeepSeek AI.
It uses an architecture where everything is a plugin, and is powered by Cordis, whose design is described in A Programming Paradigm for Spatiotemporal Composability.
Developer preview
DeepSeek Harness is currently in developer preview and is iterating rapidly. THERE WILL BE COMPATIBILITY-BREAKING CHANGES.
Run
Run from npm
Install Node.js, then run:
npx @deepseek-ai/dsh web
The command starts the Web UI, served at http://127.0.0.1:3080 by default. 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
Community and support
- Feel free to 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.