What problem does it solve? Deep Agents need file storage and memory, but choosing between ephemeral thread-scoped state, persistent cross-session storage, and real disk access is confusing and error-prone. This Skill explains how to select and configure the right backend so agent files persist exactly where and when you need them. ## Core Features & Use Cases - Backend Selection Guidance: Compares StateBackend (ephemeral), StoreBackend (persistent), FilesystemBackend (local disk), and CompositeBackend (hybrid routing) with a decision table. - Hybrid Memory Routing: Shows how to route paths like /memories/ to persistent storage while keeping working files ephemeral, using CompositeBackend with longest-prefix matching. - Custom Tool Memory Access: Demonstrates reading and writing long-term user preferences directly through the LangGraph store in custom tools. - Common Pitfall Fixes: Documents fixes for missing store instances, thread-scoped file loss, route prefix mismatches, and insecure FilesystemBackend usage. - Use Case: Build a support agent that remembers user preferences across conversations by routing /memories/ writes to a PostgresStore while keeping scratch files thread-local. ## Quick Start Ask the agent to configure a Deep Agent with a CompositeBackend that persists files under /memories/ across threads using a store.