From saga-core
Lists running SAGA sessions in a table with story ID, elapsed start time, session name, plus commands to stream logs or kill sessions.
npx claudepluginhub roeia1/saga --plugin coreThis skill is limited to using the following tools:
!`npx @saga-ai/dashboard sessions list`
Starts SAGA dashboard server in background via npx/Bash and opens it in browser to visualize epics, stories, and execution progress.
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
!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