Focus board for DeepSeek Harness agents: durable, model-maintained notes in the session workspace that pin the objective, constraints, and decisions across compaction and sessions, with automatic context injection, archive on clear, and an optional web panel.
Install
# from npm (prebuilt)
dsh plugin --profile web add dsh-plugin-focus
# from GitHub (first run asks for allowBuilds approval — follow the hint, retry)
dsh plugin --profile web add github:863683348/dsh-plugin-focus
Any plugin you install runs third-party code with your own permissions — it can read your files, use your credentials, and reach the network, and tool approvals don’t sandbox it. GitHub-sourced plugins also run build scripts at install time — pnpm blocks those until you allow them, so an install can stop with ERR_PNPM_GIT_DEP_PREPARE_NOT_ALLOWED or ERR_PNPM_IGNORED_BUILDS; dsh prints the exact key to add under allowBuilds in your profile’s pnpm-workspace.yaml, and the install works on the next run. Allowing a build is a trust decision: only install sources you trust, and pin a commit (github:owner/repo#sha).
README
A real, installable DSH plugin (DeepSeek Harness / Cordis profile bundle) that gives the agent a focus tool and a durable focus board — a small note file (default .dsh/focus.md) in the session workspace that pins the objective, hard constraints, and decisions across context compaction and across sessions on the same workspace. The todo list tracks what to do next; the focus board tracks why we are doing it and what must not drift.
Compatibility
Tool schemas are validated against the @deepseek-ai/dsh-tools value-schema DSL at plugin load (checked against dsh-tools 0.1.0-rc.6 and 0.1.1-rc.2). Earlier releases used JSON-Schema required at the root of output.schema and closed nested objects without declared properties, which made the host abort the whole profile boot with unsupported JSON schema: schema.required is not supported by the value schema DSL and could reject the tool's own results. Current releases fix both; if an affected version left your DSH unable to start, remove the plugin from the profile (or upgrade) — no data is lost.
Features
| Feature | Status |
|---|---|
focus tool — set / get / append / summary / clear |
✅ stable |
Structured entries — tag notes with kind (objective / constraint / decision / note) and status (open / done), grouped by summary |
✅ stable (v1.1) |
Prompt guidance section (focus:instructions) |
✅ stable |
| Automatic injection — board is re-injected into model context at every turn start and whenever it changes | ✅ stable |
Archive on clear — clear moves the old board to .dsh/focus.md.bak (accumulates) |
✅ stable |
focusBoard session projection for UIs |
✅ stable |
| Read-only web panel (composer dock) | 🧪 experimental (loader-format client bundle, not verified against a running web instance) |
How it works
- The board is a plain, append-friendly text file. Entries are timestamped and ordered;
getrenders newest-first with a configurable character cap (the file is never trimmed by rendering). - The plugin is a single Cordis plugin: the host face (
lib/index.js) registers the tool, the projection, and the auto-injection; the browser face (lib/client.js) renders the panel. The same composition row covers both faces via the package'sdsh.bundle+dsh.clientmanifest sections. - All file access goes through the host
ctx.fsservice, and every resolved path is containment-checked against the agent's session workspace — the board can never escape it. - Auto-injection mirrors the in-box
dsh-time-contextmechanism: anagent/pre-stepwaterfall listener appends a plugin snapshot message carrying the board text (step 1 of every turn, plus mid-turn whenever the text changes). Resumed sessions get the board back on their first step.
Install
The package declares "dsh": { "bundle": { "patch": "./cordis.patch.yml" } }, so it goes through DSH's official plugin management:
# from a local checkout (equivalent to pnpm add <path> + auto-reconcile of the bundles list)
dsh plugin --profile <profile> add /path/to/dsh-plugin-focus
# or after publishing to npm
dsh plugin --profile <profile> add dsh-plugin-focus
Restart DSH. The focus tool is registered host-wide; the read-only panel appears in the web UI on a web profile.
Alternative: mount on one agent preset only
- Copy a built-in preset to
$DSH_HOME/.agent-presets/<id>/(never edit the deployment's own preset — an upgrade overwrites it). - Append to
agent.cordis.yml:
- id: focus
name: 'dsh-plugin-focus'
config:
file: '.dsh/focus.md'
- Make sure
dsh-plugin-focusresolves (installed in the profile'snode_modulesor the module fallback directory).
Usage (model side)
| action | args | behavior |
|---|---|---|
set |
note (required) |
append an entry pinning the current focus / constraints |
append |
note (required) |
append a log entry (decision, discovery, reversal) |
get |
— | read the whole board (newest first, capped, omitted-count footer) |
clear |
— | empty the board; the old board is archived to the archive file |
The plugin also injects a focus:instructions prompt section (disable with personaSection: false) and re-injects the board into context automatically (disable with autoInject: false).
Configuration
All optional, on the composition row's config:
| key | default | meaning |
|---|---|---|
file |
.dsh/focus.md |
board path, relative to the session workspace; cannot escape it (runtime-enforced) |
archiveFile |
.dsh/focus.md.bak |
archive path for clear |
archive |
true |
whether clear archives first |
maxEntries |
60 |
max entries kept on disk (oldest dropped) |
maxChars |
8000 |
render cap for get / auto-injection (view truncation only) |
autoInject |
true |
inject the board into model context at turn start / on change |
personaSection |
true |
register the prompt-guidance section |
sectionOrder |
5 |
prompt section order (persona is 0, ascending) |
File format
# Focus Board
<!-- dsh-plugin-focus v1 -->
## [2026-08-14T23:12:00.000Z] set
<note, may span lines>
## [2026-08-14T23:13:00.000Z] append
<another note>
Clearing appends an archive block (stamped with the clear time) to the archive file, so history accumulates.
Design
- Pure logic separated from the runtime:
lib/board.jshas zero DSH/Cordis imports (parse / render / mutate / archive) and is unit-tested in isolation;lib/index.jsis the Cordis plugin. - Safety: every path resolves through
ctx.fsand is containment-checked withctx.fs.containsagainst the session workspace. - Lifecycle: tool registration, projection, injection listener, and prompt section are all Cordis-scope-managed; stopping/removing the plugin cleans them up.
- Two faces, one row: the host loader imports
., the browser loader imports./client(via thedsh.clientmanifest). ThefocusBoardsession projection (eventfocus/write) is the data seam any future UI can read withuseProjection('focusBoard').
Tests
node --test test/
Uninstall
dsh plugin --profile <profile> remove dsh-plugin-focus
Roadmap
- Verify the web panel against a live web instance and iterate on the slot UI.
- Expose board mutations from the panel (edit / clear buttons).
- Optional: attach the board to
turn/startevents for explicit snapshot semantics.
License
MIT
FAQ
- The board is empty in a fresh session — where did it go? The board is per-workspace, not per-session:
focus setin a session whose workspace already has a.dsh/focus.mdreads the existing entries. Each agent session resolves the board from its ownsession.header.cwd. - Does the injection cost tokens? The board is injected once per turn start (plus mid-turn only when the text changes), capped at
maxChars. An empty board injects nothing. - Can the board escape my workspace? No. Every path is resolved through
ctx.fsand containment-checked against the session workspace; a configured path outside it fails loud. - The web panel is marked experimental — why? The client bundle is hand-written in the loader format without a bundler and has not been verified against a running web instance yet.
- How do I publish this to npm?
npm publish(aprepublishOnlytest run is wired in). Thendsh plugin add dsh-plugin-focusinstalls it without a build step.
Links
More in this category
vectorize-io/hindsight#coding-agents★ 42988
Hindsight, agent memory that learns: long-term project memory with auto recall and retain, knowledge pages, deep reflection, and per-repo memory banks.
volcengine/OpenViking#examples/dsh-memory-plugin★ 38990
OpenViking memory and context bundle for DeepSeek Harness: pre-step auto-recall and profile injection, session capture, `viking://` URI guarding, and recall/write memory tools backed by an OpenViking server.
agentscope-ai/ReMe#dsh★ 3534
Connects DeepSeek Harness to ReMe's local-first, self-evolving personal knowledge base: automatically captures completed main-agent conversations as user-owned Markdown memory, searches conversations and source material through reme_search with BM25, optional embeddings, and wikilink expansion, and schedules daily memory consolidation.
zilliztech/memsearch#MemSearch★ 2682
Shared Markdown memory for DSH and other coding agents, with automatic capture, pre-step context injection, searchable recall, and memory-to-skill self-evolution through a review panel.
vshulcz/deja-vu#extensions/dsh★ 1093
Reads the session files thirty-three other coding agents on this machine already wrote — Claude Code, Codex, Cursor, VS Code Copilot Chat, opencode, OpenClaw, Hermes, Kimi, Cline, Zed and more — including sessions from before it was installed: six tools (deja_recall, deja_session, deja_blame, deja_fix, deja_how, deja_remember), a /deja command, and optional automatic recall added to the runtime context. Local BM25 index, no LLM, no embeddings, no network (dsh plugin --profile web add dsh-deja).
adoresever/graph-memory★ 633
Traceable, searchable cross-session memory for DeepSeek Harness — conversation knowledge as typed graph nodes (TASK/SKILL/EVENT) and typed edges.
Community comments
Comments are public GitHub Discussions. Loading them connects to GitHub and Giscus; a GitHub account is required to post.