The storage architecture design for Zeus Agent, consisting of two core components: Checkpoint (state persistence) and Backend (file storage).
Architecture Overview
Core Components
| Component | Purpose | Storage Location | Documentation |
|---|---|---|---|
| Checkpointer | Agent state persistence, HITL interrupt recovery | PostgreSQL | Checkpoint.md |
| Backend | File system operations, user cloud drive | Supabase Storage | Backend.md |
| Memory | Long-term memory (custom implementation) | Supabase Storage | Backend.md |
Quick Comparison
| Aspect | Checkpointer | Backend | Memory |
|---|---|---|---|
| Stored Content | Agent execution state | Files/artifacts | User knowledge/preferences |
| Granularity | Per execution step | File operations | Concept-level |
| Lifecycle | Session-level | User-level | Permanent |
| Accessed By | LangGraph internals | Agent tools | Custom logic |
| Current Implementation | DrizzleCheckpointSaver | StateBackend | InMemoryStore |
| Target Implementation | PostgresSaver | CloudDriveBackend | Supabase Storage |
Migration Priority
- High Priority: Checkpoint - Affects HITL feature stability
- Medium Priority: Backend - Affects artifact persistence and user experience
- Low Priority: Redis Cache - Performance optimization, can be added later
Environment Variables
The following environment variables need to be configured:DATABASE_URL- PostgreSQL connection URL (for Checkpointer)SUPABASE_URL- Supabase Storage URL (for Backend)SUPABASE_SERVICE_KEY- Supabase Service Key (for Backend)REDIS_URL- Redis connection URL (optional, for caching)