- Python 97%
- Shell 3%
didbot-claude #
Wires Claude Code to a didbot personal data server: the hook the harness runs, the plugin that installs it, and the measured contract they rest on.
Nothing here signs, holds a credential, or knows a product's record types. Everything reaches a personal data server through the local daemon's socket. CLAUDE.md says why each of those is a rule.
Watching what your agents are doing #
Install the plugin, start the receiver, and every session on the machine narrates itself:
claude plugin marketplace add git@tangled.org:permadeath.com/didbot-claude
claude plugin install didbot@didbot
./tools/echo-receiver.py
10:16:43 2ef76bde session started ~/work/thing
10:16:49 2ef76bde main Agent
10:16:49 2ef76bde spawned adb7fdf6 general-purpose
10:16:51 2ef76bde adb7fdf6 general-purpose Bash
10:16:54 2ef76bde adb7fdf6 general-purpose Bash
10:16:57 2ef76bde finished a turn adb7fdf6 general-purpose
10:17:01 2ef76bde session ended ~/work/thing
A running count sits pinned below the feed:
────────────────────────────────────────────────────────────────
sessions 3 (1 open) agents 9: 2 working, 7 resting resumed 1
calls 247 main 180 sub 67 failed 2
anomalies: forks 12 unspawned 1
A stop ends a turn, not an agent, so what is working is a refcount rather
than a flag. forks counts stops carrying no start and no type — the harness's
own internal forks, which are never allowed to become agents — and unspawned
counts calls from an agent nothing was seen to spawn.
--json prints records instead of the feed, --quiet keeps only the count,
and --log <path> keeps everything either way. kill -USR1 prints a fuller
summary without stopping it, and so does exiting.
Nothing here authenticates, and nothing leaves the machine. Removing it is
claude plugin uninstall didbot@didbot.
Field names and identifiers are recorded. Values are not — a payload carries prompts, tool arguments and file paths, and none of that answers a question plan/collection.md asks.
What it will cost, before you install it #
tools/estimate.py counts what the harness has already written on this
machine — one transcript per session, one sidecar per subagent — and says how
many agent contexts that implies per month. File names and timestamps only; no
transcript is opened.
It reports a range rather than a number on purpose: on the machine this was built for, thirty days averaged 1,500 contexts a month while the last two days ran at 5,300. Either figure alone would be wrong within a week, and the spread is the finding.
What is measured, and what is assumed #
plan/harnesses.md is the register. An entry says how it was observed: which version, which surface, what the run was. What is left unmeasured is rates over long sessions — background subagents, resumed contexts — which is what plan/collection.md is for.