oh-my-openkilo / references
AGENTS.md9 starsChanged 21 days agoMITView on GitHub
How agentmemory wires into host coding agents via the connect command. Use when installing agentmemory into a specific agent, when asked which agents are supported, or when a connect adapter writes the wrong config path.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- KeyShiftLDN/ClaudeCodeedited, first seen Jun 9, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- KeyShiftLDN/ClaudeCode★ 0100% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,774 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository24 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- agentmemory-historySkill
- agentmemory-opsSkill
- agentmemorySkill
- caveman-commitSkill
- caveman-compressSkill
- caveman-reviewSkill
- cavemanSkill
- caveman-statsSkill
- codebase-designSkill
- code-reviewSkill
- delegationSkill
- documentationSkill
- git-commitSkill
- graphifySkill
- grillingSkill
- i-have-adhdSkill
- jev-decisionSkill
- megacaveSkill
- orchestrationSkill
- plansSkill
- resolving-merge-conflictsSkill
- ultracaveSkill
The file
We split this agents.md into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
After wiring, restart the host or run its MCP reload (for example /mcp in Claude Code) so it picks up the server.
- Very specific: line 20
Run agentmemory connect <name> using a name from the table in REFERENCE.md.
- Very specific: line 21
Verify: the host should show the full tool set with a server running.
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
agentmemory connect <agent> merges the memory server into a host agent's config and preserves any existing servers. REST is the underlying protocol; for MCP-only hosts the adapter wires the stdio MCP bridge.
Quick start
agentmemory connect claude-code # or cursor, codex, gemini-cli, ...After wiring, restart the host or run its MCP reload (for example /mcp in Claude Code) so it picks up the server. Then confirm the agent lists agentmemory's tools.
Workflow
- Detect the calling agent. If unknown, default to
claude-code. - Run
agentmemory connect <name>using a name from the table in REFERENCE.md. - Verify: the host should show the full tool set with a server running. Only 7 tools means the MCP shim could not reach a server (see ../../_shared/TROUBLESHOOTING.md).
Notes
- The action skills (remember, recall, and the rest) are installed separately with
npx skills add rohitg00/agentmemory.connectmakes tools available; skills teach the agent when to use them. - Windows: use WSL2. Native Windows runs the server but
connectis not supported there.
See also
- agentmemory-mcp-tools, agentmemory-rest-api, agentmemory-hooks.
Reference
The full adapter list with display names and protocol notes lives in REFERENCE.md, generated from src/cli/connect/.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.