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.
The agentmemory plugin hooks that capture observations automatically across the agent session lifecycle. Use when explaining how memory gets captured without manual saves, when debugging missing observations, or when tuning what gets recorded.
Review the instructions the agent will receive before you install.
The agentmemory plugin registers lifecycle hooks so memory is captured automatically. You do not have to call memory_save for routine work; the hooks observe tool use, prompts, and session boundaries and write observations for you.
For Claude Code, install its plugin:
/plugin marketplace add rohitg00/agentmemory
/plugin install agentmemory
For Devin CLI and Devin Desktop, install the plugin and start a new session:
devin plugins install rohitg00/agentmemory#plugin
Run /hooks inside Devin to confirm the agentmemory hooks are loaded. Plugin hooks run only in local Devin sessions, not in cloud sessions.
Hermes and OpenClaw use their native integrations and lifecycle contracts. Follow the matching integration setup instructions and verify a real turn creates an observation. Installing shared skills or connecting MCP alone does not enable automatic capture. Watch recorded observations in the viewer at http://localhost:3113 when using the default port.
handoff resume it.recall and recap.commit-context and commit-history.AGENTMEMORY_AUTO_COMPRESS) and hook context injection (AGENTMEMORY_INJECT_CONTEXT) are separate options. Native integrations have their own recall/capture settings; inspect the host configuration instead of assuming these flags control every plugin.The exact registered hook events live in REFERENCE.md, generated from plugin/hooks/hooks.json.
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.
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.
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.
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.