OpenCode setup
My coding agent, with a memory that survives between sessions.
- Agents
- Developer tools
- Memory
Mission
Memory Palace
Sessions produce notes. Keep the useful ones, let repeats build confidence, and promote what is proven. Watch out for two writers at once.
Best: not set yet
Skip to the write-upEverything in the game is made-up data. Press Escape any time to pause.
Why I built it
A coding agent forgets everything when a session ends. I wanted mine to remember who I am, what each project is, and what went wrong last time, without me repeating it.
How it works
I run my own OpenCode setup with a memory directory. At the start of a session the agent reads my identity and the current project notes. During a session it writes down patterns it notices, and it checkpoints automatically. At the end it writes a summary. Observations that show up three times can be proposed as a permanent rule, and I approve or reject each one.
The memory files are version controlled, and a pre-commit hook scans for secrets before anything is committed.
The bug that taught me about locks
Two sessions once wrote to the same observations file at the same time, and one of them wiped most of it. I recovered it from git, then made every writer take a shared lock. Level 3 of the game is that bug.