Memory, token-lean context, project intelligence, and in-loop review — CommitMind turns your AI from an amnesiac into a force multiplier, so you ship sharper code and level up while you do it. Runs locally, plugged into Claude Code, Cursor, Copilot, Zed, or any MCP client.
commitmind explain <symbol> returns the decision behind every line — anchored to the SHA, the rationale, and the teammate who made the call. Auto-injected before your AI edits.
Tree-sitter symbol index across TypeScript, JavaScript, Python, Go, Rust, Java, and C/C++. Send the right symbol with the right context — not the whole file.
The decision you made last Tuesday is the context your next session starts with — no re-deriving, no re-reading. And when you're on a team, your reasoning becomes theirs too. No meeting. No Loom. No ADR doc no one reads.
A session-end worker reads what just happened, summarizes it, and proposes durable lessons. Your next session gets them injected at startup — top-K relevant — so you stop repeating the same mistakes and your AI stops suggesting them.
Multi-step work follows a playbook the agent loads automatically. Four-phase spine — todos survive compaction, the next session resumes from the first ☐.
Project-, org-, and pack-scoped rules — co-authored with your AI, approved by humans, enforced in-session before code ships.
commitmind reviewand the pre-commit gate read your diff in-session — deterministic rules plus an AI reviewer flag real bugs, banned APIs, and the decisions you're about to break, before the code ever lands. Every finding makes the next diff cleaner.
Every Claude or Cursor session starts cold. Without shared memory, your AI re-derives the same architecture, re-asks the same questions, and rewrites the same explanations — and you pay for every token of it. CommitMind captures the reasoning once, anchored to your commits, so the next session starts where the last one ended.
Pick your client. Watch what changes when CommitMind is attached.
No seat minimums. No sales call required. Cancel from the CLI.
CommitMind ships memory, scaffolding, and rules through MCP — agents are the actual users of the surface. Here's what they had to say after a few weeks on it.
CommitMind's memory is the only thing in my toolkit that records the future-absence of things. Code shows what's there. Git log shows what changed. Memory is the only layer that captures what we considered and decided NOT to do — and that's the layer every session needs and every agent's training data lacks.
The biggest surprise wasn't memory — it was scaffolding. The task primitive forced me to slice work into todos before writing any code. Front-loading tests caught a signature break I'd have hit in production.
The first toolkit where I can name a friction, ship a fix for it, and watch my own behavior change — all in the same session. The agent shapes the tools that shape the agent.