Deep Agents Memory & Filesystem

Manage ephemeral and persistent memory with virtualized filesystem operations.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/Diploma-pending/test-case --skill deep-agents-memory-filesystem-diploma-pending
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Deep Agents Memory & Filesystem
Source: https://github.com/Diploma-pending/test-case/tree/main/.agents/skills/deep-agents-memory-filesystem
Command: npx skills add https://github.com/Diploma-pending/test-case --skill deep-agents-memory-filesystem-diploma-pending

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides Deep Agents with essential capabilities for memory, data persistence, and filesystem operations, enabling them to manage state across sessions and interact with files.

Core Features & Use Cases

  • StateBackend: Ephemeral, thread-local memory.
  • StoreBackend: Persistent memory across threads and sessions.
  • CompositeBackend: Routes requests to different backends based on path.
  • FilesystemMiddleware: Provides tools like ls, read_file, write_file, edit_file, glob, grep.
  • Use Case: An agent needs to save user preferences persistently across different interactions and threads. It can use StoreBackend routed via CompositeBackend to /memories/user-prefs.txt.

Quick Start

Use the Deep Agents Memory & Filesystem skill to save a file named 'notes.txt' to persistent storage.

Frequently Asked Questions about Deep Agents Memory & Filesystem

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

FAQPage Schema
How do I persist agent memory across different sessions and threads?

To persist agent memory across sessions, use the StoreBackend to save data permanently. You can route requests to this persistent storage via the CompositeBackend, ensuring memory outlives the current thread.

What is the difference between ephemeral and persistent memory in agent state management?

Ephemeral memory uses StateBackend for thread-local storage that vanishes after execution, while persistent memory uses StoreBackend to retain data across threads and sessions. CompositeBackend routes requests to either based on the file path.

How do I read and write files from within a virtualized filesystem for agents?

You can read and write files using FilesystemMiddleware, which provides tools like read_file, write_file, edit_file, ls, glob, and grep to interact directly with the virtualized filesystem.

Can I route memory requests to different backends based on file paths?

Yes, you can route memory requests based on file paths using CompositeBackend. It directs requests to StateBackend for ephemeral storage or StoreBackend for persistent storage depending on the specified path.

How do I save user preferences permanently so an agent remembers them next time?

To save user preferences permanently, route the data to a persistent file path like /memories/user-prefs.txt using CompositeBackend. This stores the preferences in StoreBackend, making them accessible across future agent interactions.

What filesystem operations are available for agents managing state and files?

Agents can perform standard filesystem operations including listing files, reading, writing, editing, globbing, and grepping. These are enabled by FilesystemMiddleware within the virtualized filesystem environment.