How agentmemory wires into host coding agents via the connect command. Use when installing agentmemory into a specific agent, when asked which agents are sup...
记忆
Agentmemory Hooks
试用The agentmemory plugin hooks that capture observations automatically across the agent session lifecycle. Use when explaining how memory gets captured without...
它能做什么
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.
技能文档
The Claude Code 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.
Quick start
Install the plugin and the hooks register themselves:
/plugin marketplace add rohitg00/agentmemory
/plugin install agentmemory
Watch observations land live at http://localhost:3113.
What the hooks do
- Session start and end frame each unit of work and let
handoffresume it. - Tool-use hooks capture what changed and why, the raw material for
recallandrecap. - Prompt-submit captures intent. Pre-compact preserves context before the host trims it.
- A post-commit hook links commits to sessions, which powers
commit-contextandcommit-history.
Important
- Capture is on by default and is zero-LLM. Turning observations into LLM summaries (
AGENTMEMORY_AUTO_COMPRESS) and injecting them back into context (AGENTMEMORY_INJECT_CONTEXT) are separate opt-ins because they spend tokens. - If observations are missing, confirm the plugin is enabled and the server is running. See ../_shared/TROUBLESHOOTING.md.
See also
- agentmemory-config for the capture and injection flags.
- The handoff, recap, and session-history skills consume what these hooks record.
Reference
The exact registered hook events live in REFERENCE.md, generated from plugin/hooks/hooks.json.
相关技能
The agentmemory HTTP REST API surface, the primary protocol for talking to the memory server. Use when calling agentmemory over HTTP, when MCP is unavailable...
Audit and maintain OpenClaw-style long-term memory. Use for MEMORY.md cleanup, daily-note digestion, duplicate detection, stale-memory review, and promoting...
Unlimited organized memory for your AI agent. Store, search, and organize projects, contacts, decisions, and knowledge across categories. Never lose context...
Map of every agentmemory MCP tool, what each does, and its parameters. Use when choosing which memory tool to call, when a tool name or argument is unclear,...
Use when preserving, searching, reviewing, or exporting user-owned agent memory across OpenClaw, Codex, Claude, OpenCode, Hermes, Qoder, Obsidian, and Git. Inputs are local memory/chat stores and handoff summaries; outputs are Obsidian sources, memory indexes, context/profile packs, skill inventorie