kyleandClaude Opus 5.5
de1032157b
memoryd (files, the check, edits, journal, index, recall, serving), the memory tools and built-in grants in brokerd, the memory block in loopd, bxctl reindex and memory, and the device checks with memoryd. Each task was built as a reference and gated. Each was replayed on its own at its end state (854 to 936 tests) and mutation-checked. Each skeleton compiles and fails its tests. Every todo comment was read beside its signature. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
867 B
memoryd-unreachable
What you see. A recall or memory call answers memory is unavailable: memoryd did not answer (see docs/runbook.md#memoryd-unreachable), and the model tells you it cannot use its
memory.
Why. brokerd decided the call and sent it to memoryd's brokerd socket
(<home>/run/broker-memory/memory.sock, or [memory] socket in brokerd.toml), and nothing
answered within 30 seconds, or the answer was not a tool result. memoryd is not running, is
listening elsewhere, or is stuck.
Confirm. pgrep -x memoryd; ls -l <home>/run/broker-memory/; the end of memoryd's log.
Fix. Start memoryd serve --config <path>, or make [memory] socket in brokerd.toml and
[sockets] broker in memoryd.toml name the same path.
Check. Ask the agent to recall something; the answer lists hits or says there were none.