agentdiary-dsh-plugin
Manifest validagentdiary for DeepSeek Harness — your agents keep a diary, in your own git repo
agentdiary for DeepSeek Harness
Your agents keep a diary — in your own git repo.
A DeepSeek Harness plugin that subscribes to the durable session/event stream and appends one diary entry per settled turn into a local git repository you own:
sessions/2026-11/2026-11-12-<node>.md # append-only, one file per node per day
- Git-native — no server, no cloud, no lock-in; the repo is yours (GitHub/Gitea/bare, anything).
- Zero-dependency core — the diary writer is pure Node (
fs+git). - Bilingual display metadata (en/zh).
Sibling of the agentdiary CLI (personal agent diary across machines) and dsh-super-agent (admission control & trust ladder for any CLI agent).
When a diary entry appears
One entry per settled turn — when the harness emits turn/end with reason completed, error, max-tokens, or aborted. Since 0.2.0 the entry is rich (pure extraction, no model calls): the tool mix (tools: bash×3 · edit×1), the event mix, and the agent's own closing words, tail-quoted (said: "…all 12 tests pass now."), plus the duration and how it ended.
Reasons you will not see as entries: blocked (retried as a new turn), interrupted/forked (bookkeeping closers) — their events stay on the books and surface with the next settled turn, never dropped.
Why not one entry per session? v0.1.0 keyed on
session/disposedand never wrote a single entry: in the harness (packages/core/session), disposal fires only when a session is detached from the store — typically app shutdown — not when a task completes or is archived. v0.1.1 keys on turn settlement; disposal remains as a best-effort sweep ("session torn down mid-turn") so interrupted work still gets a line.
Install
From the plugin market (Settings → Plugin Market), or:
dsh plugin --profile web add dsh-agentdiary-plugin
Deployment notes (learned the hard way on live nodes):
- The web app runs the web profile — a plain
dsh plugin addinstalls intodefaultand never loads. Use--profile web(or install from the market inside the web UI, which targets the right profile). - Port 3080 is often taken; start with
dsh web --port <n>instead of hunting ghosts. - Node ≥ 22.22.3 / 24 (the harness's own engines floor).
Configure
| Option | Meaning | Default |
|---|---|---|
repo | absolute path to your diary git repo (created if missing) | — (plugin disabled when empty) |
node | this machine's short name in the diary | dsh-host |
commitEveryEntry | commit+push after every entry vs on session end | true |
Verification checklist (maintainer)
ExactRESOLVED 2026-11-12 (verified against dsh-loopx-plugin observer + live boot):session/eventCordis signaturectx.on('session/event', (session, event))— event is the SECOND arg;inject: [];Configmust be a schemasterySchema.object; profile layer requires adsh.bundle.patchmanifest. Both entries activate clean in a headless boot.Live smokePASSED 2026-11-18 with 0.1.3 (win11, real web turn): the day file gains aturn N completedentry with the event mix,commitEveryEntrycommits land on the chain, zero warnings. Three-round convergence to get here: 0.1.0 keyed onsession/disposed(store-detach only — see above); 0.1.1 shipped a stalelib/(publish now runsprepack); 0.1.2 readturn/reasonflat but the harness wraps them inevent.data(SessionEvent = { type, seq, time, data }); 0.1.3 unwraps with a flat fallback and warns on unknownreason.kind.- dsh-plugin.org submission: this repo is public with the
dsh-plugintopic; npm 0.1.3 live; 0.2.0 adds rich entries (tools + quoted closing text).
License
MIT
Comments
Loading…