superserve sessions commands manage active and past agent sessions.
Each session represents an isolated conversation with an agent, complete with persistent state in the /workspace filesystem.
List Sessions
View all sessions:Example Output
Filter by Agent
Filter by Status
active- Session is currently runningrunning- Alias for activeidle- Session exists but no recent activitycompleted- Session finished successfullyended- Session was manually endedfailed- Session encountered an errorerror- Alias for failed
JSON Output
Get Session Details
View detailed information about a session:Short Session IDs
You can use a short prefix of the session ID:Example Output
JSON Output
Resume Session
Continue a previous session:Example
Persistent State
When you resume a session:- Conversation history - The agent remembers previous messages
- Filesystem state - Files in
/workspacepersist from the previous session - Environment - Secrets and configuration remain available
- Multi-turn debugging sessions
- Long-running data analysis tasks
- Resuming after network interruptions
End Session
Manually end an active session:Example Output
Why End Sessions?
Ending sessions:- Frees resources - Stops the sandbox container
- Clears state - Resets the
/workspacefilesystem - Improves security - Ensures sensitive data doesn’t persist
Command Reference
superserve sessions list
List all sessions.
Filter sessions by agent name or ID
Filter sessions by status (e.g.,
active, idle, ended)Output as JSON
superserve sessions get
Get details of a specific session.
Session ID or short prefix (e.g.,
ses_5a3f7b9c or 5a3f7b9c)Output as JSON
superserve sessions resume
Resume a previous session.
Session ID or short prefix (e.g.,
ses_5a3f7b9c or 5a3f7b9c)superserve sessions end
End an active session.
Session ID or short prefix (e.g.,
ses_5a3f7b9c or 5a3f7b9c)Session Lifecycle
Status Meanings
| Status | Description |
|---|---|
ACTIVE | Session is currently processing a message |
IDLE | Session exists but no recent activity |
RUNNING | Alias for ACTIVE |
ENDED | Session was manually ended |
COMPLETED | Session finished successfully |
FAILED | Agent encountered an error |
ERROR | Alias for FAILED |
PENDING | Session is being created |
Session IDs
Session IDs are prefixed withses_ and contain 32 hexadecimal characters:
Short IDs
The CLI displays shortened IDs insessions list for readability:
Examples
List Recent Sessions
Resume Last Session for Agent
End All Idle Sessions
Count Messages Across All Sessions
Session Titles
Sessions are titled based on the first message:Troubleshooting
”Session not found”
Verify the session ID:”No sessions found”
You haven’t started any sessions yet. Run an agent:“Session has expired”
Sessions expire after 24 hours of inactivity and cannot be resumed. Start a new session:Best Practices
- Resume for long tasks - Use
sessions resumefor multi-step debugging or data analysis - End when done - Manually end sessions to free resources
- Filter by agent - Use
--agentto find sessions for specific agents - Check status - Use
sessions getto see how many messages are in a session - Use short IDs - The first 8-12 characters are usually unique enough