hippocampus-subagent-memory
Isolate and coordinate sub-agent memory in OpenClaw with Hippocampus using scoped IDs, bounded merge-back, and explicit cross-agent imports.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/cezexpl/hippocampus-subagent-memoryHippocampus Subagent Memory
Use this skill when OpenClaw spawns sub-agents that need their own memory without contaminating the parent agent context.
Use It For
- creating isolated sub-agent memory namespaces
- preventing accidental memory leakage across siblings
- returning only bounded summaries or artifacts to the parent
- coordinating explicit import from child to parent
Preferred Flow
- Spawn a child with a scoped
HIPOKAMP_SUBAGENT_ID. - Let the child write only into its own namespace.
- Return a bounded result package at the end of the task.
- Import back to parent only what is explicitly approved.
Guidance
- Default to isolation.
- Do not flatten full child memory into the parent.
- Prefer summary, artifacts, and references over transcript copy.
- Tag child memory with session and parent linkage metadata.
- Root-agent bootstrap should happen once in the portal; child agents should inherit scope automatically and should not require separate portal signup.
Related
hippocampus-memory-corefor core memory operationshippocampus-openclaw-onboardingfor base config@hippocampus/openclaw-context-enginefor automated spawn/end lifecycle hooks
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-cezexpl-hippocampus-subagent-memory": {
"enabled": true,
"auto_update": true
}
}
}Related Skills
hippocampus-memory-core
Deterministic external memory for OpenClaw and coding agents using S3-Hipokamp. Use for storing durable facts, retrieving prior decisions, snapshotting memory, and restoring agent state.
hippocampus-openclaw-onboarding
Bootstrap OpenClaw with Hippocampus memory under a branded, repeatable setup: workspace, agent ID, API key or bootstrap token, and MCP wiring.