Subagent Persistent Memory - Claude Code
Auto-memory that persists across multiple subagent invocations.
Persistent memory lets a subagent carry state forward between invocations. A researcher agent can remember what it's already looked into; a reviewer can remember your house style.
What it does
Enable persistent memory in the subagent frontmatter and Claude writes summaries to a scoped memory file after each run. On the next invocation, the agent loads those notes before it begins. It's auto-memory, but scoped to the agent identity rather than the project.
When to use it
- Agents that do the same job repeatedly and benefit from recall.
- Multi-session work where you want continuity without copy-pasting context.
- Reviewer or auditor agents that should learn your preferences over time.
- Fan-out patterns where each worker builds on prior runs.
Gotchas
- Memory grows over time. Prune stale entries or it starts to slow down invocations.
- Persistent memory isn't magic - the agent still needs relevant instructions each call.
- Scope matters. Project-scoped memory shouldn't leak personal preferences; user-scoped shouldn't leak project data.
Official docs: https://code.claude.com/docs/en/sub-agents.md#enable-persistent-memory
Technical content at the intersection of AI and development. Building with AI agents, Claude Code, and modern dev tools - then showing you exactly how it works.
Get the weekly deep dive
Tutorials on Claude Code, AI agents, and dev tools - delivered free every week.
Was this helpful?
Related Guides
Related Tools
Claude Code
Anthropic's agentic coding CLI. Runs in your terminal, edits files autonomously, spawns sub-agents, and maintains memory...
View ToolCodeburn
Interactive TUI dashboard that shows exactly where your Claude Code and Cursor tokens are going, in real time.
View ToolClaude Opus 4.7
Anthropic's flagship reasoning model. Best-in-class for coding, long-context analysis, and agentic workflows. 1M token c...
View ToolZed
High-performance code editor built in Rust with native AI integration. Sub-millisecond input latency. Built-in assistant...
View ToolRelated Videos

Nimbalyst: The Open-Source Visual Workspace for Building with Codex and Claude Code
Nimbalyst Demo: A Visual Workspace for Codex + Claude Code with Kanban, Plans, and AI Commits Try it: https://nimbalyst.com/ Star Repo Here: https://github.com/Nimbalyst/nimbalyst This video demos N...

Composio: Connect OpenClaw & Claude Code to 1,000+ Apps via CLI
Composio: Connect AI Agents to 1,000+ Apps via CLI (Gmail, Google Docs/Sheets, Hacker News Workflows) Check out Composio here: http://dashboard.composio.dev/?utm_source=Youtube&utm_channel=0426&utm_...

Claude Code Channels in 8 Minutes
Anthropic has released Channels for Claude Code, enabling external events (CI alerts, production errors, PR comments, Discord/Telegram messages, webhooks, cron jobs, logs, and monitoring signals) to b...
Related Posts

Claude Opus 4.8 Is an Agent Honesty Release
Claude Opus 4.8 looks like a benchmark bump, but the developer story is better honesty, dynamic workflows, and effort co...

Continual Learning in Claude Code: Memory That Compounds
Skills turn Claude Code sessions into persistent memory. Successes and failures get captured, progressively disclosed, a...

Anthropic Sonnet 4.5 in Claude Code
Anthropic's Claude Sonnet 4.5 isn't just another model increment. The company claims they've observed it maintaining foc...

AI Code Attribution Needs Defect Forensics, Not Vibes
The rsync Claude debate shows why teams need reproducible defect forensics before AI attribution becomes a public blame...

Security Agents Need Repro Harnesses, Not More Scan Prompts
Anthropic's open-source vulnerability harness shows where AI security work is going: reproducible exploit loops, separat...

AI Agent Containment Needs a Capability Ledger
Anthropic's Claude containment writeup points to the next security layer for coding agents: deterministic capability led...
