Code Memory 0.9.0 — local context for DeepSeek Harness

Code Memory 0.9.0

First public, packaged community release for DeepSeek Harness 0.2.0-rc.2. Unofficial; independently maintained and not endorsed by DeepSeek.

Included

• Automatic source context before the first Harness model step, with direct file/symbol routes, local MiniLM/LanceDB retrieval, and dependency graph expansion.
• Freshness checks and suppression of repeated unchanged whole-file content already supplied to Harness.
• Local MCP server, CM Atlas, and the optional native-client context hook and warm daemon already present in the preceding source commits.
• English README and Windows installation guide; the previous Russian README is preserved.
• A Windows ZIP containing the bootstrap and prebuilt package. No source checkout or local TypeScript build is required to install it.

The automatic-context procedure is enabled by the installer for Harness. Codex and Claude Code receive MCP connections; their UserPromptSubmit hook remains a separate manual setup. This release does not change the retrieval/model procedure or add new model A/B results.

Download and installation

Download CM-0.9.0-Windows.zip and SHA256SUMS.txt from this release. Verify the ZIP against the checksum file, extract it, then run:

powershell -NoProfile -ExecutionPolicy Bypass -File .\install_cm.ps1 -ProjectRoot 'C:\path\to\your-project' -Clients harness

Setup prints launch paths and a diagnostic command. Initial npm dependencies and embedding weights require internet access. A compatible Node.js is reused or a private runtime is downloaded; administrator rights are not required. Indexed project code is not executed. Full installation guide.

Evidence and scope

The existing Harness benchmark reports 45–66% fewer total model tokens and 18–37% lower session time across three small evaluation series. This is one JavaScript/TypeScript project and six task types. Installation/indexing are separate costs; successes and failures are retained. These percentages are not a promise for other projects or clients. Native-client results and earlier unsuccessful approaches remain available.

The release packaging is checked separately by the required build/docs/unit/fixture suite, actual Harness ToolRuntime smoke, and installation from the extracted ZIP on a disposable project, followed by MCP diagnostics and retrieval. Publication checks verify the tag's commit and the downloaded asset hashes; they do not constitute a new model benchmark.

Limits

Windows bootstrap; pinned Harness version; JavaScript/TypeScript only; corpus limit of 500 files and 8 MiB source. macOS/Linux bootstrap, automatic updates/rollback, cloud subscriptions, and guaranteed savings are not included. Local retrieval does not prevent a cloud model provider from receiving selected source context.