Adding memory to MiMo-Code

OpenCode's SQLite store and plugin loader under ~/.config/mimocode

MiMo-Code (mimo) is an OpenCode fork that keeps its conversation history in ~/.local/share/mimocode/mimocode.db (or under XDG_DATA_HOME/mimocode, relocated by MIMOCODE_HOME or MIMOCODE_DB). Its tables use OpenCode's message schema unchanged, so deja reads and writes back sessions through the same SQLite reader.

Adding recall

deja install mimo

That writes three things under ~/.config/mimocode (or MIMOCODE_CONFIG_DIR):

• The MCP server, into mimocode.jsonc (or mimocode.json when already present) under the mcp.deja block.
• The deja-history skill, at ~/.config/mimocode/skills/deja-history/SKILL.md.
• The /deja command, at ~/.config/mimocode/commands/deja.md.

Session-start and per-prompt recall

deja install mimo-auto

Everything above, plus ~/.config/mimocode/plugins/deja.js and the TUI status plugin ~/.config/mimocode/plugins/deja-status.tsx registered in tui.json. The plugin injects the project digest on the first turn, recalls relevant sessions per prompt, captures compactions, and surfaces file history and past error fixes on tool calls.

The part that is not about this harness

The index covers every agent's transcripts on the machine — forty-seven of them today, each in its own format — so a fix found in Claude Code or Codex answers a question asked in MiMo-Code, and the reverse. Indexing and search stay local, and credentials are stripped as the index is built.

Getting started · Switching between agents · The MiMo-Code session format

Found this useful? Star deja-vu on GitHub.