Connect agentmemory to coding agents such as Claude Code and Codex while preserving existing server settings. It guides configuration, host restarts, and checks that memory tools are available and can save and retrieve information.
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.
Review the instructions the agent will receive before you install.
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.
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, or a new session after devin mcp list in Devin CLI) so it picks up the server. Then confirm the agent lists agentmemory's tools.
Devin CLI and Devin Desktop can also install the whole plugin with devin plugins install rohitg00/agentmemory#plugin, which adds the skills, the MCP server, and the capture hooks in one step. Cloud Devin sessions cannot reach a local agentmemory server, so the plugin is for local sessions only.
agentmemory connect <name> using a name from the table in REFERENCE.md.npx skills@1.7.1 add rohitg00/agentmemory --agent hermes-agent --skill '*' or use --agent openclaw. Choose the intended host; add --global only for a user-wide installation. Verify skill discovery and read a skill's local support file in that host.connect is not supported there.The full adapter list with display names and protocol notes lives in REFERENCE.md, generated from src/cli/connect/.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Explain how agentmemory stores and retrieves coding agents’ memories, including its engine, search methods, memory lifecycle, ports, and web viewer. Useful for understanding the system or planning extensions to its functions.
Set up and troubleshoot a local agentmemory server by checking MCP connections, authentication, ports, and environment settings. Understand which optional memory features require additional configuration, model downloads, or token usage before enabling them.
Understand how agentmemory automatically records tool activity, prompts, and session boundaries through hooks, actions triggered by session events. Use it to check integration setup, investigate missing records, and distinguish capture from optional summaries and context injection.
Helps agents choose the right agentmemory tool through MCP, a protocol for connecting agents to tools. It explains tool roles and points to parameter references for saving, retrieving, organizing, and maintaining stored knowledge.
Guides HTTP integration with the agentmemory server for saving and searching knowledge. It explains authentication, request conventions, and endpoint references, including how to connect systems that do not support MCP, the agent tool connection protocol.
Trace a file, function, or line through Git history to the agent session linked to its commit. It presents recorded commit details, session summaries, and important observations to help explain the change.