What problem does it solve? Deep Agents need a way to persist files and memory beyond a single conversation thread, but choosing and wiring the right backend (ephemeral, persistent, or hybrid) is error-prone and easy to misconfigure. ## Core Features & Use Cases - Backend Selection Guidance: Explains when to use StateBackend (ephemeral, thread-scoped), StoreBackend (persistent across threads), FilesystemBackend (real disk access), and CompositeBackend (path-based routing). - FilesystemMiddleware Tools: Documents the built-in file tools (ls, read_file, write_file, edit_file, glob, grep) and what agents can and cannot configure. - Common Pitfall Fixes: Shows correct patterns for store requirements, thread-scoping issues, route prefix matching, production PostgresStore usage, and virtual_mode security. - Use Case: You want user preferences saved in one thread to be readable in another. Route /memories/ to StoreBackend via CompositeBackend so files persist across thread IDs. ## Quick Start Ask the agent to configure a Deep Agent with CompositeBackend so that files under /memories/ persist across threads while everything else stays ephemeral.