memory-happens · recorded example · technical beta
“Why did we disable automatic retries?”
The context is gone. The conversation and handover note are still there. Give your agent a way to look them up.
This example uses invented records. The search and reads below were executed through MCP on the released code. It is a replay, not a live search or a model answering your question.
What was connected
Two synthetic Codex sessions, exported with the supplied archiver, and one Markdown note. One session discusses invoice delivery; the other discusses image uploads. No model or vector database was used.
A manually chosen search word
search(query="invoice", characters=8000)
Two findings: one session and one note.The unrelated upload session was not returned. These results do not measure retrieval quality on a larger corpus.
sessions · billing.md start=10
The earlier conversation
The reason was recorded here.
Open the recorded passage
## 2026-04-08T10:00:00Z [user] L2:B0
The invoice request timed out, but the customer received two invoices. How did that happen?
## 2026-04-08T10:01:00Z [assistant] L3:B0
The provider accepted the first request before our timeout. Our retry sent it again. The provider does not support an idempotency key on this endpoint.
## 2026-04-08T10:02:00Z [user] L4:B0
Disable automatic retries for invoice sends. After a timeout, check the provider dashboard before anyone resends.
notes · billing.md start=3
The handover note
The instruction survived here.
Open the recorded passage
# Billing handover
Invoice sends: automatic retries are disabled. After a timeout, check the provider dashboard before resending.
Read what was said then
The cards identify the search hits. Each recorded read requested a wider window from line 1; the session header is omitted here.
The recorded conversation says the first request reached the provider before the timeout; retrying sent it again. The note preserves the instruction to check the provider dashboard before resending.
Those are the synthetic sources. Deciding what they mean for today's code remains with the person or agent reading them.
A miss in the same corpus
search(query="duplicate", characters=8000) returned zero findings. The conversation describes two invoices, but never uses that word.
The result suggests other words, a wider period or another connected source. Empty results are not proof that an event never happened.
Try one question from your own past work
Start with the isolated demo, then connect a source you choose. Supported raw session logs need an export; Markdown notes can be connected directly.