deep-agents-memory

To persist Deep Agent memory across sessions, you need a backend that stores long-term state. This skill provides a StoreBackend specifically designed to maintain memory and filesystem access continuity between independent agent runs and threads.

The best way to manage mixed agent state is using a CompositeBackend for hybrid routing. It combines StateBackend for ephemeral per-thread memory with StoreBackend for cross-session persistence within a single configuration.

You give an agent filesystem access by integrating FilesystemMiddleware. It exposes file operations like ls, read_file, write_file, edit_file, glob, and grep, enabling on-demand file manipulation during agent execution.

Yes, you can restrict agent filesystem access to a specific root directory. The backend configuration enforces root-dir restrictions and routing rules, ensuring agents only operate within allowed path boundaries.

Yes, the memory backend supports optional human-in-the-loop controls. Alongside enforcing backend configuration and routing rules, it allows you to integrate manual oversight into the agent's state and file operations.

Your agent loses memory because it lacks cross-session persistence and is using ephemeral per-thread state. You need to configure a StoreBackend or CompositeBackend to route memory data to a persistent storage layer.