dsh-honcho

dsh-honcho

English | 中文 | Русский

Persistent memory for DeepSeek Harness, powered by Honcho.

dsh forgets everything when a session ends. This plugin gives it memory that doesn't: what you're building, how you like to work, what you decided last week and why. It reads the same ~/.honcho/config.json as the other Honcho integrations, so there is one place to configure all of them — and pointing two of them at the same workspace gives them one shared memory. Install

Then put your API key and name in ~/.honcho/config.json:

Get a key at app.honcho.dev. HONCHO_API_KEY in the environment also works on its own — the config file is only needed to change defaults. What it does

Injects what Honcho knows at the start of a session — your peer card, a summary of this project's session so far, and the conclusions Honcho has drawn that are relevant to what you just asked. One API call, shaped to a character budget, refreshed as you work.

Captures every turn. User and assistant messages go to Honcho in the background, debounced, and flushed at turn boundaries, before compaction, and on shutdown. Common secret formats are redacted first (API keys and tokens, password:/secret: fields, private keys, JWTs, cookies, connection strings, credential URLs). This is regex matching, so it is best-effort: an unusual format, or a bare high-entropy string with no label, can still get through. Add your own with capture.noisePatterns, or turn capture off with capture.saveMessages.

Gives the model three tools: /honcho shows status and a link to the session in the Honcho dashboard — see Commands below. Configuration

Everything behavioral lives in ~/.honcho/config.json under hosts.dsh — the same file claude-honcho, codex-honcho, and the other integrations read. Root holds identity and connection; the host block holds behavior.

The file is read as strict JSON: the comments and trailing commas below are annotation only. Leave them in and the whole file is skipped without a warning, so every setting falls back to its default.