Home

The memory that follows your coding agent — so you get the assistant you actually wanted.

_{Works with Claude Code + Antigravity — see compatibility}

AgentM gives your coding agent a permanent memory. It writes what it learns — about you, and about each project — as plain Markdown notes in a folder you own: no hidden database, nothing you can't read or edit yourself. Memory splits into two tenants — personal notes on how you like to work, and a per-project record of decisions and open threads — so a fresh session can pick up exactly where the last one left off. It brings the right notes back at the right moment, and looks after the collection over time so it gets better instead of messier.

Said differently, AgentM is the memory and self-improvement layer — it dreams and learns between sessions. A phase-gated development workflow (setup · plan · work · review · release · bugfix) can run on top of it, provided by a companion toolkit rather than by AgentM itself. Its customization system extends AgentM's own abilities through plugins that enable long-running, nuanced development workflows, automated project management, and more. Its opinion system is designed to layer in personas focused on a specific kind of work — activation is the next build slice.

AgentM works best paired with crickets — the toolkit of plugins (capabilities, skills, hooks, and sub-agents) that make it even more useful.

🚀 Get started

AgentM installs alongside your coding agent — Claude Code or Antigravity — so you can be up and running in a few minutes. See requirements.

Install AgentM and crickets with the recommended configuration and a Google Drive vault:

# Point the vault at a Google Drive folder named "Agent" (the recommended default)
export MEMORY_VAULT_PATH="<your-google-drive>/Agent"

# Install AgentM for every project on this machine (user scope) + verification hooks
bash ~/agentm/install.sh --hooks --scope user

# Add the crickets plugins (Claude Code + Antigravity)
curl -fsSL https://raw.githubusercontent.com/alexherrero/crickets/main/bootstrap.sh | bash

Step-by-step, with the vault and hooks explained: Install machine-wide (recommended). More on the available configurations here.

📖 Learn more

The wiki covers everything there is to know about AgentM. A few links to get you started.

• Why we built it — the problem, the solution and the reason.
• Architecture — how it's made.
• Reference — fields, flags, schemas and more.
• What we built, when — the combined build timeline for AgentM and crickets, plus the roadmap-era-to-release-tag decoder.

🗂️ Browse by kind

The memory vault itself is browsable by kind — every note groups into a generated Map of Content (MOC) alongside its siblings of the same kind (fix, pattern, decision, and dozens more), so you can scan every entry of a kind without a search. See MOC generator for how the pages are built, and Kind-taxonomy registry for the kinds it recognizes.

---

Note

Latest release: v9.5.0. A recalled memory's score breakdown used to exist for one prompt turn, then vanish — memory-recall trace <slug> now explains why any past recall surfaced what it did, kept in the existing per-recall ledger.