agentmemory-hooks
/agentmemory-hooks
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.
- Author
- rohitg00 ↗
- Repository
- agentmemory ↗
- Licence
- Apache-2.0
- Last repository change
- 25.10.2026
Assessment and security
- Files in this package
- 3
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
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.
Original author description
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.
How it works
- Quick start
- What the hooks do
- Important
- See also
- Reference
SKILL.md preview
--- name: agentmemory-hooks description: 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. user-invocable: false --- 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. ## Quick start For Claude Code, install its plugin: ```bash /plugin marketplace add rohitg00/agentmemory /plugin install agentmemory ``` For Devin CLI and Devin Desktop, install the plugin and start a new session: ```bash 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. Pi and OMP install native recall and capture with `agentmemory connect pi --with-mcp` or `agentmemory connect omp --with-mcp`. Reload Pi or restart OMP, then inspect `/agentmemory-status`. DSH requires `agentmemory connect dsh --with-hooks` and a restart. Cursor lifecycle hooks come from its enabled plugin, separately from `connect cursor`'s MCP setup. 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. A pending capture queue is not proof that the daemon stored the event. ## What the hooks do - Session start and end frame each unit of work and let `handoff` resume it. - Tool-use hooks capture what changed and why, the raw material for `recall` and `recap`. - Prompt-submit captures intent. Pre-compact preserves context before the host trims it. - A post-commit hook links commits to sessions, which powers `commit-context` and `commit-history`. ## Important - The plugin hooks capture by default without an LLM. Per-observation LLM compression (`AGENTMEMORY_AUTO_COMPRESS`) and hook context injection (`AGENTMEMORY_INJECT_CONTEXT`) are separate options. Session summaries can use a configured LLM provider independently of automatic observation compression. Native integrations have their own recall/capture settings; inspect the host configuration instead of assuming these flags control every plugin. - If observations are missing, confirm the plugin is enabled and the server is running. See [TROUBLESHOOTING.md](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`.
Files in this package (3)
- REFERENCE.md 1 KB
- SKILL.md 3 KB
- TROUBLESHOOTING.md 4 KB
Versions
The database has no other skills named agentmemory-hooks.
Database snapshot: 13.11.2026 · package version 8cb75d1bd3cc (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90agentmemory-mcp-tools
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, or when answering what agentmemory can do via MCP. - 100agentmemory-config
Set up and diagnose local agentmemory, including MCP, environment variables, ports, and feature flags. Use when getting started, checking a connection, enabling a feature, configuring auth, or explaining why a feature is off by default. - 100observations
List recent captured session observations (the summarized voyage logs). Use when the user wants to see what Captain Memo has logged from past sessions. - 100auto-capture-claude-code
Claude Code adapter for the auto-capture skill. Extends auto-capture with automatic session-end hooks that capture transcripts to Open Brain without manual intervention. Use this when you want every meaningful Claude Code session to be preserved automatically — not just the ones… - 100hooks
Guide to Claude Code hooks — lifecycle events, handler types, decision control, and common patterns. Use when creating, debugging, or planning hooks for guardrails, context injection, quality gates, notifications, or automation. - 100langfuse-trace-ingestion-medic
Investigate missing, partial or incorrectly nested Langfuse observations by reconciling a captured OTLP batch with Observations API v2 readbacks. Use when traces disappear after a serverless exit, exported spans are absent, or parent context differs. Trigger with "Langfuse spans…