Superset Orchestration

Coordinate terminal agents with Superset's workspace, agent, and terminal commands. Treat this as a coordinator-driven protocol: Superset provides session transport, while the coordinator owns task dependencies and completion state.

Establish the control surface

1. Run superset auth whoami --json.
2. Run superset terminals --help and require list, read, send, and close.
3. If those commands are absent, run superset update and recheck. Do not invent or substitute unsupported orchestration commands.
4. When developing inside the Superset monorepo, use bun run --cwd packages/cli dev -- in place of superset to exercise the source CLI against the API configured in the root .env. To reuse production CLI authentication while testing unreleased source commands, run them from packages/cli with SUPERSET_API_URL=https://api.superset.sh bunx cli-framework dev.
5. Resolve the workspace, host, and terminal-capable agent before dispatching:

superset hosts list --json
superset agents list --local --json
superset workspaces list --local --json

When coordinating from inside the target workspace, pass --workspace "$SUPERSET_WORKSPACE_ID" explicitly to agent and terminal commands. Only workspaces get defaults its workspace ID from that environment variable. Pass --host <id> consistently for a remote host. If the target host is offline, use hosts wake <id> and confirm it is online before dispatching. Do not use --agent superset: it creates a chat session, and terminal read/send cannot control it.