deep-agents-memory

Implement configurable memory backends for ephemeral and persistent agent data.

7|1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Harmeet10000/skills --skill deep-agents-memory-harmeet10000
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deep-agents-memory
Source: https://github.com/Harmeet10000/skills/tree/main/skills/ai-ml/deep-agents-memory
Command: npx skills add https://github.com/Harmeet10000/skills --skill deep-agents-memory-harmeet10000

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deep Agents rely on pluggable backends to manage memory, persistence, and filesystem access across sessions and threads. This Skill provides a structured way to route data through ephemeral, persistent, and hybrid backends with clear safety constraints.

Core Features & Use Cases

  • StateBackend: ephemeral per-thread memory that resets when the thread ends.
  • StoreBackend: persistent storage across threads and sessions.
  • CompositeBackend: route specific paths to the appropriate backend for hybrid storage.
  • FilesystemMiddleware: file operations integrated with backends to support memory-backed workflows.
  • Use Case: maintain user preferences across sessions while keeping temporary data isolated per task.

Quick Start

Store a temporary note to /memories/style.txt and verify it persists as configured.

Frequently Asked Questions about deep-agents-memory

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

FAQPage Schema
How do I add persistent memory for deep agents across sessions?

You achieve persistent memory for deep agents by implementing a StoreBackend, which provides cross-session storage to retain data like user preferences even after threads end. This ensures long-term data persistence without losing state.

What is the best way to isolate ephemeral state per agent thread?

The best way to isolate ephemeral state is using a StateBackend, which provides temporary per-thread memory that automatically resets when the thread ends. This keeps task-specific data cleanly separated.

Can I route specific paths to different storage backends for hybrid workflows?

Yes, you can route specific paths to different storage backends using a CompositeBackend. This enables hybrid storage routing, directing ephemeral data to StateBackend and persistent data to StoreBackend simultaneously.

How does FilesystemMiddleware work with agent memory backends?

FilesystemMiddleware integrates file operations directly with configured memory backends to support memory-backed workflows. It allows agents to perform file operations while maintaining the safety boundaries and persistence rules of the underlying storage.

When do I need hybrid storage routing for my agent's memory and persistence?

You need hybrid storage routing when maintaining user preferences across sessions while keeping temporary data isolated per task. CompositeBackend routes specific paths to appropriate ephemeral or persistent backends for this mixed requirement.