Durable, git-verified repo memory for coding agents.
Agents Remember makes hard-earned lessons first-class infrastructure — the local invariants, naming rules, migration scars, cross-repo contracts, and "this looks safe but is not" facts that live in people's heads, old PRs, and team habits, exactly where coding agents miss them. It keeps that knowledge as versioned Markdown beside the code, drift-checked against Git and updated only after approved work lands.
src/orchestrator/core_editor.py
ar-memory/onboarding/src/orchestrator/core_editor.py.md
Agents reach that memory three ways:
- By path — a source file's own note, found directly from its path (as above). Needs nothing extra.
- By meaning — semantic search across the memory when you know the concept but not the file.
- By relationship — a code graph for callers, callees, and dependencies.
The by-path notes are the core; meaning and relationship are opt-in providers (see Concepts and Providers).
Modern coding agents can make clean, plausible edits while missing the project-specific rules that make those edits safe. A top-level instruction file can help, but it does not naturally reappear when the agent is deep in a file and deciding what to change.
Agents Remember fixes that: the matching note is reachable at the moment of the edit — most often by the very path the agent is already working in — so project rules surface exactly when a change is being made, not buried in a top-level file.
The memory layer rests on a small, strict discipline:
- Onboarding units: Markdown notes derived from source paths. A file such as
src/foo/bar.tsmaps toar-memory/onboarding/src/foo/bar.ts.mdin the default repo-local mode. - Memory quality control: Before an agent trusts onboarding,
C-02-memory-quality-controlchecks whether the source changed since the onboarding was verified. During closeout it also covers new-file onboarding and final memory quality checks. - Approval-gated updates: Onboarding records approved current state, not guesses or plans. Task-local notes stay task-local until the developer approves implementation.
The default setup stores durable memory in the target repository under ar-memory/. Teams that need separate memory repositories can use external memory under ar-coordination/memory-repos/ar-<repo>/.
This is the short path for a new workspace. The detailed walkthrough lives in Getting Started.
Ask your agent to:
- Wire the MCP server — Register Agents Remember MCP with this harness using
uvx, help you author the settings file, then restart the harness so it loads the server. - Install Agents Remember — Run
runtime_install, thenskills_install(scaffolding, skills, and provider images when providers are enabled). - Onboard your project — Run
C-13-install-and-onboard. It pre-checks the setup, installs the start hook (or places the directive for harnesses without one), sets up the memory repo (it asks: scaffold a new one or use an existing one), bootstraps onboarding, and starts the providers indexing.
The only hands-on steps for you is to restart once after step 1, and then continue from there.
After that, normal work starts in chat mode. The agent resolves the active context with C-08-ar-coordination-context-resolver, checks memory quality with C-02-memory-quality-control, reads relevant onboarding beside code, and updates onboarding after approved changes.
Different tools discover instructions and skills differently. Use the install page for your harness:
| Harness | Setup guide |
|---|---|
| Codex | docs/install/codex.md |
| Claude Code | docs/install/claude-code.md |
| Cursor | docs/install/cursor.md |
| Antigravity | docs/install/antigravity.md |
| VS Code + GitHub Copilot | docs/install/vscode-copilot.md |
| Hermes.md | docs/install/hermes.md |
| Pi.dev | docs/install/pi.md |
| OpenClaw | docs/install/openclaw.md |
- Getting Started - a fuller first-run setup.
- Concepts - onboarding units, memory roots, drift, and approval gates.
- Architecture - runtime, coordination, internal memory, and external memory.
- Workflows - chat, light task, heavy task, and when to use each.
- Benchmark Methodology - how paired
codex exec --jsonruns are captured and compared. - FAQ - design principles, objections, and comparisons.
- External Memory Guide - separate memory repos for selected code repos.
- Cost-aware Bootstrap - model and wave-sizing choices for token-heavy repository bootstrap.
- Settings Reference - memory-layer
system/settings.jsonand MCP authority settings. - Skills Reference - the installed skill families.
agents-remember-md/
AGENTS.md # source checkout instructions
README.md # public front door
mcp/ # package-local MCP server and services
src/agents_remember/package_data/
runtime/
agents-md-files/ # installed AGENTS.md templates
skills/ # installed skill source tree
system/defaults/examples/ # scaffold examples used by initialization
benchmarks/ # optional benchmark package source
docs/ # user-facing documentation
roadmap/ # design notes and historical planning
The installed runtime lives in ar-coordination/, not in the source checkout:
ar-coordination/
AGENTS.md
skills/
system/
memory-repos/
benchmarks/ # optional, installed with --include-benchmarks
tasks/
notes/
worktrees/
temp/
Agents Remember is an active greenfield project. The public docs describe the current intended setup: install the runtime into ar-coordination, expose installed skills to your harness, and let repository memory live either in repo-local ar-memory/ or in selected external memory repos.
Contributions should make the memory layer clearer, safer, and easier to apply consistently. Start with CONTRIBUTING.md and keep the core rules intact: drift check before planning, approval before implementation, and onboarding updates only after approved changes.