kyle/boxmaker
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

brokerd: memory calls to memoryd with the session's state; labels only stricter

Browse Source 
Implemented-By: OpenCode session (model recorded in docs/implementer-log.md)
This commit is contained in:
kyle
2026-09-25 16:41:44 -07:00
committed by kyle
parent fcfd590687
commit e167fc871b
11 changed files with 410 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/runbook.md
+18
View File
@@ -617,3 +617,21 @@ cannot be a socket). It will not start without the memory it owns.
move it aside and start `memoryd`, which rebuilds it (see `memory-index-damaged`).
**Check.** `memoryd serve --config <path>` prints `memoryd: serving`.
## 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.