Core Modules
Bootstrapping
Startup bootstrapping — System Prompt assembly, mode selection, dynamic context injection
HITL
Auto-Run modes and tool approval mechanism, ensuring human confirmation before sensitive operations
Middleware
DeepAgents middleware pipeline — auto-summarization, filesystem, task management, prompt caching
Models
Model configuration & management — custom API Keys, Zeus preset models, 200+ model profiles
Context
Agent context assembly, Token management & optimization strategies
Tools
Four-layer tool system — Built-in Tools, MCP Tools, OAuth Tools, Connector Tools
Skills
Dynamic instruction packages — code review, data analysis, writing assistant, and other extensible skills
System Prompt
System prompt — CORE, SOUL, TOOLS, WORKFLOW, MEMORY, dynamic injection
Artifacts
Structured tool return format — HTML, code, charts, and other rich content rendering
Workspace
Each user has an independent cloud workspace managed byCloudDriveBackend, backed by Supabase Storage for persistence and Redis for caching.
| Path | Description |
|---|---|
users/{user_id}/workspace/ | Agent’s working directory for output files |
users/{user_id}/workspace/projects/ | Project files |
users/{user_id}/workspace/sandbox-output/ | Sandbox execution results |
users/{user_id}/workspace/uploads/ | User-uploaded files |
users/{user_id}/memory/ | Long-term memory files |
File System Detailed Design
Learn about the complete design of CloudDriveBackend, Checkpoint, and other storage architecture
Sessions
Each conversation creates an independent Session for state isolation:- Session ID: Format is
session_{hex12}, provided by the frontend or auto-generated - Thread ID: Same as Session ID, used for Checkpointer state isolation
- Context Cache: Stores tool list, system prompt, and interrupt configuration per session_id, reused during HITL recovery
Checkpointer
State persistence is implemented via LangGraph’s Checkpointer mechanism:| Environment | Implementation | Description |
|---|---|---|
| Production | PostgresSaver | PostgreSQL persistence, supports cross-process recovery |
| Development/Fallback | MemorySaver | In-memory storage, lost on process restart |
Checkpoint Storage
Learn about PostgresSaver detailed configuration and HITL recovery flow
Modes
Zeus supports three interaction modes, each constraining the Agent’s tool set and behavioral boundaries:Mode Comparison
| Feature | Agent | Ask | Plan |
|---|---|---|---|
| File read | Yes | Yes | Yes |
| File write | Yes | No | No |
| Sandbox execution | Yes | No | No |
| Memory read | Yes | No | Yes |
| Memory write | Yes | No | No |
| HITL approval | Yes | No | No |
| Tool calls | All | Read-only subset | Read-only subset |
| Typical scenarios | Coding, deployment, automation | Code explanation, Q&A | Architecture design, plan comparison |
invoke() entry point, implemented through disable flags and tool filtering. Ask mode disables sandbox, memory writes, and HITL; Plan mode disables sandbox and HITL but retains memory read access for context.