deep-agents-memory

Manage Deep Agents memory, persistence, and filesystem access via pluggable backends.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/HyunjunJeon/SDS-AX-Advanced-2026-1 --skill deep-agents-memory-hyunjunjeon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deep-agents-memory
Source: https://github.com/HyunjunJeon/SDS-AX-Advanced-2026-1/tree/main/Day-01/.agents/skills/deep-agents-memory
Command: npx skills add https://github.com/HyunjunJeon/SDS-AX-Advanced-2026-1 --skill deep-agents-memory-hyunjunjeon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deep Agents need memory, persistence, or filesystem access to maintain state across interactions and sessions. This skill provides pluggable backends: StateBackend (ephemeral), StoreBackend (persistent), CompositeBackend for routing, and FilesystemMiddleware for common file operations and path-based routing.

Core Features & Use Cases

  • Ephemeral in-memory state via StateBackend for fast, scoped memory.
  • Persistent memory via StoreBackend that survives threads and sessions.
  • Hybrid storage with CompositeBackend to route different paths to different backends.
  • FilesystemMiddleware for ls, read_file, write_file, edit_file, glob, and grep operations.
  • Safe development and production configurations with clear boundaries and security considerations.

Quick Start

Invoke the deep-agents-memory skill to enable ephemeral and persistent memory backends for your Deep Agent.

Frequently Asked Questions about deep-agents-memory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I persist memory for AI agents across multiple sessions?

Persistent memory for AI agents across sessions is achieved using StoreBackend, which saves state so it survives threads and sessions. This allows agents to recall previous interactions and maintain long-term context without data loss.

What's the best way to route agent memory between ephemeral and persistent storage?

Routing agent memory between ephemeral and persistent storage is handled by a CompositeBackend, which applies routing rules to direct different data paths to StateBackend or StoreBackend. This hybrid approach optimizes both speed and durability.

Can I perform filesystem operations like grep and glob within an agent's memory backend?

Yes, you can perform filesystem operations within an agent's memory backend using FilesystemMiddleware. It supports common file operations including ls, read_file, write_file, edit_file, glob, and grep for path-based routing and management.

How do I prevent cross-thread data leakage when using persistent agent memory?

To prevent cross-thread data leakage with persistent agent memory, you must implement safeguards and proper routing rules for CompositeBackend. Establishing clear boundaries and security considerations ensures safe development and production configurations.

When should I use ephemeral in-memory state versus persistent storage for my agent?

Ephemeral in-memory state via StateBackend is used for fast, scoped memory during active tasks, while persistent storage is needed for data that must survive across threads and sessions. Hybrid routing combines both for optimized performance.