Foxfire1st/agents-remember

<h1 align="center"> Agents Remember </h1> <h3 align="center"> Git-verified records for what your coding agents know. A control plane for what they do. </h3> <p align="center"> <img alt="NPM License" src="https://img.shields.io/python/required-version-toml?tomlFilePath=https%3A%2F%2Fraw.githubusercontent.com%2FFoxfire1st%2Fagents-remember%2Fmain%2Fmcp%2Fpyproject.toml"> </p> <p align="center"> 📖 <b>Current docs:</b> https://foxfire1st.github.io/agents-remember/</br> 🤖 <b>Machine-readable summary:</b> https://foxfire1st.github.io/agents-remember/llms.txt</br> <i>Note: caches and search snippets may serve an outdated copy of this README — the docs site above is canonical and always current.</i> </p>

Table of Contents

1. Why It Exists
2. Core Features
3. What It Looks Like In Practice
4. Live Demo
5. Requirements
6. Quickstart
7. Documentation
8. Repository Layout
9. Status
10. Stability
11. Contributing

Why It Exists

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.

Core Features

Agents Remember gives coding agents project memory they can verify and act on. It turns local invariants, naming rules, migration scars, cross-repo contracts, and "this looks safe but is not" facts into versioned Markdown beside the code, checks that memory against Git before use, and updates it only after approve