Quick Start
1
Simple Usage
Attach a session to the agent so its state survives a restart.
2
With Configuration
Reopen the same session ID later to pick up exactly where you left off.
How It Works
Guides
Overview
Persistence concepts
Database Setup
Configure database backends
Session Resume
Resume interrupted sessions
Best Practices
Choose a backend before you scale
Choose a backend before you scale
SQLite is perfect for a single process; move to PostgreSQL or Redis once several instances need to share the same sessions.
Treat session_id as the resume key
Treat session_id as the resume key
The same
session_id reconnects to the same history. Generate it per user or per task, and store it where you can look it up later.Checkpoint long-running work
Checkpoint long-running work
Set
checkpoint_interval so a crash mid-task resumes from the last checkpoint instead of the beginning.
