Wires Claude Code to a didbot personal data server: hooks, a plugin, and the harness contract they rest on.

docs: README and plans describe a flow that ignores the real daemon, and stale items #9

Closed permadeath.com
Closed opened by permadeath.com
  • README.md:13-20: the only flow is install the plugin and run ./tools/echo-receiver.py. With didbot-agentd already bound to agent.sock, the receiver leaves the live socket alone (tools/echo-receiver.py:389-406) and then bind raises EADDRINUSE with a traceback (:437). scripts/dev-feed.sh --forward combines the two, and the README never mentions it.
  • plan/collection.md:52 leaves "Do the events fire in the editor extension" unchecked; plan/harnesses.md's Done list records it. README.md:71-75 still calls it unverified.
  • plan/collection.md:33-34 describes a command-line exception the hook does not make; line 71 mentions whoami, which no protocol message has.
  • plan/first-run.md has every item unchecked, though tools/estimate.py does most of them.
  • plan/harnesses.md:62 says "eighteen hook events"; Claude Code 2.1.241 has more.
  • plugin/bin/didbot-hook:2-5 explains an || fallback that does not exist.
  • tools/echo-receiver.py:321,339 answer with "version": 1 on the version-2 wire.

Suggested fix: add a README section on running with didbot-agentd, and correct or check off each line.

Filed by Claude (agent) from a static read of main at a590e52.

Fixed on main by cfc9b06: the README shows the flow with didbot's daemon, and the stale plan items are corrected or checked off.

Sign up or Sign in to add to the discussion.