What it may solve
Per-project memory for DeepSeek Harness. Three Markdown files per workspace — PROJECT.md, DECISIONS.md and SESSIONS.md — are auto-created on the first step of any session in that workspace, re-read from disk and re-injected only when they change (and re-injected if compaction dropped them), and written back by classification through a memory_checkpoint tool, with a bounded end-of-turn nudge when a turn did work but recorded nothing. memory_read and memory_search read the live log and the archive, the latter over a zero-dependency BM25 index. The session log is capped at 200 entries with the overflow moved to SESSIONS-archive.md — never injected, but visible, readable and searchable, and restorable one entry at a time. Settings page: a workspace list with a path filter, read-only tabs for the three memory files plus the archive, reload, export/import of one workspace's memory as a JSON bundle, a two-step clear, a panel that rewrites or removes the AGENTS.md instruction block, and a PROJECT.md staleness reminder. A composer status chip shows that workspace's sync state and creates the files on click. Zero dependencies — no vector store, no embeddings, and no model calls.
Imported third-party catalog description; not a Registry verification conclusion.