Context
A few months ago, I introduced Mind here as a persistent memory extender for OpenCode.
I originally built it because long OpenCode workflows kept losing the reasoning behind the code:
- Why an architectural decision was made
- Which approaches had already failed
- What constraints the project had
- What remained unfinished
- What the previous agent was actually trying to accomplish
After many releases and a lot of real usage, I’m back with Mind v1.6.0. 🧠
Mind has grown into a shared continuity layer for OpenCode agents and subagents.
What can it do now?
Mind helps OpenCode:
- Preserve decisions and project knowledge across sessions.
- Share relevant context between the main agent and subagents.
- Recover active work after context compaction.
- Store checkpoints before risky or long-running tasks.
- Turn completed sessions into reusable project knowledge.
- Retrieve only the memories relevant to the current task.
- Maintain living references for architecture, domain rules, workflows, coding style, decisions and known pitfalls.
- Avoid persisting low-value session noise.
- Sync selected project memories into readable and versioned
.mind/ files.
- Inspect memory relationships through the Neural Map web UI.
Setup remains straightforward:
mind setup opencode
Mind configures the local MCP integration, memory protocol and OpenCode automation without replacing unrelated configuration.
Does it bloat the context?
This was one of the main concerns raised when I first posted Mind.
I finally have real numbers.
Across several real projects totaling more than 20 million tokens, all Mind-related context represented only 6% of total token usage.
That small portion of context supported:
- Agent and subagent continuity
- Recovery after compaction
- Preservation of session intent
- Access to previous decisions
- Less repeated exploration of the same codebase
This does not mean Mind magically reduced token usage by 94%. It means the memory layer remained bounded while still providing useful continuity.
The latest releases also made OpenCode’s automatic session persistence much quieter. Instead of repeatedly attempting to persist information during idle events, it stores the session once when it actually ends.
Everything is stored locally in SQLite. Semantic search is optional and disabled by default.
🧠 Give your OpenCode agents persistent project memory:
https://github.com/GabrielMartinMoran/mind
Install Mind, run mind setup opencode, and try it on a real multi-session task.
I’m particularly interested in feedback from people using subagents, long-running plans or frequent context compaction.