list-sessions
List all running SAGA sessions
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
List all running SAGA sessions
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Start autonomous story implementation
Releases a new version of SAGA (plugin + dashboard). Bumps version numbers, updates CHANGELOG.md, publishes dashboard to npm, and creates GitHub release. Use when the user says 'release', 'publish', 'new version', or 'version bump'.
Collaboratively plan a goal, then create stories (standalone or epic-based)
Create a new epic definition with vision and architecture
Generate stories from an epic
Initialize .saga/ directory structure for SAGA epic/story workflow
| name | list-sessions |
| description | List all running SAGA sessions |
| user-invocable | true |
| disable-model-invocation | true |
| allowed-tools | ["Bash"] |
!npx @saga-ai/dashboard sessions list
The command above outputs a JSON array of session objects:
[
{
"name": "saga-story-my-story-id-1704067200000",
"status": "running",
"outputFile": "/tmp/saga-sessions/saga-story-my-story-id-1704067200000.out"
}
]
If the array is empty, report:
No SAGA sessions are currently running.
If sessions exist, parse each session name to extract:
Present in a table format:
## Running Sessions
| Story | Started | Session Name |
|-------|---------|--------------|
| login-flow | 2h 30m ago | saga-story-login-flow-1704067200000 |
To stream logs: `saga sessions logs <session-name>`
To kill session: `saga sessions kill <session-name>`
The session name format is: saga-story-<storyId>-<timestamp>
To extract components:
saga-story- prefix-) are the timestamp (Unix milliseconds)storyIdExample: saga-story-auth-login-flow-1704067200000
saga-story- → auth-login-flow-1704067200000- → timestamp 1704067200000auth-login-flow