Repo: https://github.com/kninetimmy/memhub I’ve been using Claude Code and Codex a lot on side projects, and the thing that kept annoying me was not really “context window size” by itself. It was having to re-explain the same project facts every session. Stuff like:
- what the build/test commands are
- why a design decision was made
- what tasks were in flight
- what files/docs matter
- what the agent already learned last session
- what should not be rewritten again because we already made that call So I built memhub. The basic idea is pretty simple: each repo gets its own .memhub/project.sqlite, and Claude Code/Codex can both use it as a shared project memory. It’s local-first. No account. No cloud service. No daemon. No hosted database. Just a Rust binary and a SQLite file next to the repo. What it does right now:
- stores facts, decisions, tasks, commands, session notes, and project state
- lets Claude Code and Codex recall project context through MCP
- supports both FTS and hybrid recall
- can ingest reference docs so the agent can search them later instead of me pasting the same markdown/specs into prompts
- has a /wrap-up flow where agent-proposed facts/decisions get staged first
- has a local dashboard for recall/debug/token-ish metrics The important part for me was the write model. I don’t want an agent permanently writing “facts” just because it sounded confident. So agent-written facts and decisions go into a pending review flow. During /wrap-up, I approve/reject them. Tasks and session notes can be lower-friction because they’re not really durable truth. So the workflow is basically: Ask agent something agent recalls relevant project memory agent works agent proposes facts/decisions/tasks /wrap-up I approve what should become durable project memory. It’s been especially nice to drop in ui design markdown files or coding style guides and have the agent follow those in its decision making. I know this isn’t the be all end all to agent memory. It’s just a practical tool I wanted for my own Claude Code/Codex projects that isn’t some over kill obsidian or tool set that I won’t use 80% of the things it does. The design bias is:
- boring storage over magic
- repo-local over global brain
- explicit review over “agent said so”
- searchable memory over giant markdown files loaded every session
- easy delete/export over lock-in I built it because I got tired of re-teaching agents the same repo every few days and wanted something local that I could inspect/delete/export. It’s mainly for myself but i figured someone might find it useful for those who dont want something over the top. submitted by /u/kninetimmy1
Originally posted by u/kninetimmy1 on r/ClaudeCode
You must log in or # to comment.