deep-agents-memory

To persist agent memory across multiple sessions, configure a StoreBackend for durable, cross-thread storage. This maintains long-term memory and files so later sessions can retrieve and reuse them.

The best way to separate temporary scratch files from permanent agent memory is to use a CompositeBackend for hybrid path routing. It directs different filesystem paths to ephemeral or persistent backends based on path prefixes.

Yes, you can use standard file operations like read and write with a custom memory backend by configuring FilesystemMiddleware. This enables ls, read_file, write_file, edit_file, glob, and grep tools to operate with the correct persistence behavior.

You need ephemeral thread-scoped state for deep agents when you want temporary working files to exist only for the lifetime of a single thread. StateBackend handles this by keeping fast, thread-scoped working memory without persistence.

Yes, composite routing supports different path prefixes for ephemeral and persistent storage. CompositeBackend allows you to route paths like /memories/ to persistent storage while keeping other paths ephemeral for the current thread.