Memory
The notes store, durable markdown memories, recall and remember, and the nightly consolidation pass.
Two stores sit behind one pair of tools. recall searches both. remember writes
to whichever fits.
The notes store
Operational state, machine-local, mode 0600, never leaving the box. Four record kinds share one file because they share one lifecycle: written once, searched often, occasionally closed.
| Kind | What it holds |
|---|---|
fact | a standing truth about you or the world you operate in |
loop | something owed, by you or to you, with an optional due date |
saved | a link, document or clipping parked for later |
write | an outbound change Otto made, plus how to reverse it |
This exists because before it, the only places a fact could live were CLAUDE.md edited by hand, the session's own memory which a fired trigger never sees, and trigger action text, which recipes had started abusing as a database. The price-watch recipe stored last week's price inside its own prompt and rewrote the prompt to update it. That is a key-value store spelled as a paragraph.
Search is substring-and-token, deliberately not fuzzy. The caller is a language model that can retry with a different word, and a scoring function that surfaced near-misses would let a stale fact answer a question it does not actually cover. Results sort due things first, soonest first, then most recently touched.
Loops are the part you feel
When you say you will do something, or you are waiting on someone else, it is
recorded with a due date if there is one, and it keeps surfacing in the brief
until it is closed. Closing is explicit: done or dropped.
How loudly a loop is allowed to speak is the escalation curve.
Loop hygiene
Nightly, after consolidation, a pass closes loops the evidence already closed — never on a guess. An auto-filed crash-loop note closes once no crash has recurred for fourteen days by default, unless it filed a failing regression test, in which case quiet alone is not enough: it is proposed once, or closed when that test file is gone. Exact duplicate loops collapse, keeping the oldest. Everything else ambiguous — old and untouched, undated, unreadable — is proposed once with keep and drop buttons, never closed outright, and never asked about again either way. Reopening a loop stops it from ever being auto-closed again.
The same pass names avoidance once: a loop whose due date keeps getting pushed later, past a threshold, gets one plain sentence stating the pattern as a fact. It is never raised again after that, and a loop is either named for avoidance or proposed for closing, never both.
Nothing is ever deleted. loop_hygiene runs the pass on demand — dry run by
default, apply:true to actually close, recent:true to see what it already
closed and why.
House rules
Corrections pile up as near-duplicate feedback memories — "no emoji", "don't
use emoji in replies" — that a search returns three of and nobody re-reads.
Nightly, global-scope feedback memories are compiled into one deduplicated,
size-capped, newest-first house-rules memory: two corrections merge only when
they say the same thing, so short instructions that differ by one word stay
separate. It never overwrites a hand-written memory of that name, and it never
reads its own output.
Memory audit
recall counts what it returns, and logs a query that returns nothing from
either store — a repeated miss is a gap worth writing down, not a coincidence.
memory_audit reports what that instrumentation has learned: memories never
returned, memories unused for months, unresolved misses, and the compiled house
rules. Read-only, and nothing here is a reason to message you unprompted.
Writes and undo
After every calendar event or task Otto creates, it records a write note whose
undo field says exactly how to reverse it, in plain English, executable with no
other context. That is what makes "undo that" answerable tomorrow rather than only
in the conversation where it happened.
Durable memories
Knowledge that should outlive the channel lives as markdown files under the Claude
memory directories, so every Claude Code session in every project can read it.
Four types: user, feedback, project, reference.
The files are the source of truth. There is no index to rebuild.
recall reads them directly and forget deletes one. Because they are plain
markdown with frontmatter, they are equally editable by hand.
Nightly consolidation
At 04:00 the session distils itself into memory: what happened, what was decided,
what is worth keeping. consolidate_memory forces a pass out of band.
The division of labour matters. Do not hand-write memories the nightly pass would have caught anyway; do write the things only Otto saw, in the moment, on Telegram.
Surviving compaction
The session runs for weeks, and when its context compacts, anything that lived only in the conversation goes with it: a draft shown but not yet approved, a trigger armed a minute ago, the thread being worked. Durable state survives because it is on disk. Conversational state does not, and the first sign of the loss is Otto answering "approve it" with a blank look.
A hook fires before compaction and writes one note: what is held in the send queue, what fires within six hours, and the last few exchanges. The post-compact turn reads it back instead of asking.
It cannot serialise understanding, and it does not try. It writes down the facts that make recovery cheap, and it is deliberately forgiving: any failure inside it is swallowed, because a wedged compaction would be worse than a lost note.
When to reach for recall
Before answering anything about your history, your preferences, or a decision already made. Before asking you something you may already have said. When a trigger or a scan names a person or project with no context attached.
Nothing found is not evidence that it never happened.