Recalling from agent memory
Requires the brain_recall tool. It exists only when the surrealfs server
has an agent memory key. If you do not see it, stop here: use the brain skill and
answer from the files, which are complete on their own.
Agent memory is the memory layer behind SurrealFS. Every text file written through the server is mirrored into it automatically, so it keeps every version that was ever filed plus the entities and relationships it extracted from the prose. That is what makes it worth asking: it answers what the current files no longer say.
How to use it
- Read the files first.
lsandcatunder/brain/per thebrainskill. Recall is not a search over the files —searchis that. Calling recall instead of reading them gives you a worse answer more slowly. - Ask a question, not a keyword. "What is blocking the SOC2 audit" recalls; "SOC2" does not. Each hit comes back labelled with the SurrealFS path it was filed from, so open that file next when it looks relevant.
- Say where a claim came from. If a claim came only from recall, mark it as such — it means nothing in the filesystem backs it up yet, and that is usually worth fixing by writing it down.
What it is good for
- Why the current state is what it is. A risk file says what is true now; recall has the versions that said otherwise, and the wording that changed.
- A risk that was pruned. A long-resolved risk removed from the board is still
recallable, so
brain_recallcan rebuild the file if it turns out to matter. - What the files omit. A relationship between two findings that nobody wrote down, or a note filed by a routine or a colleague's session you never saw.
Pitfalls
- It is behind the files, not instead of them. An answer built on recall alone, with the current files unread, is usually out of date.
- Nothing you say in chat reaches it. Only what you write through the SurrealFS tools gets mirrored — so file the outcome.
write_bytesis not mirrored. Agent memory indexes prose.