List all running SAGA sessions
!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-flowSearch for places (restaurants, cafes, etc.) via Google Places API proxy on localhost.
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Start voice calls via the OpenClaw voice-call plugin.
Notion API for creating and managing pages, databases, and blocks.
Gemini CLI for one-shot Q&A, summaries, and generation.
Category:developer