RetrySight Docs cloud
Cloud dashboard
RetrySight Cloud staging console — Collectors, Live, Tasks, Cost, Traces, Account settings, and which IDs to copy.
The Cloud console is the React dashboard at cloud-staging.retrysight.com. GraphQL (JWT + account_id) and Live WebSocket subscriptions (taskUpdated, agentHeartbeat) talk to the same origin under /api/v1.
Pages
| Route | Nav | What it does |
|---|---|---|
/signup, /login | — | Public auth. Signup creates the account, OWNER, and rk_live_* key. |
/welcome | after signup | Account ID and collector installer. Account ID ≠ agent ID. |
/ | Dashboard | Weekly KPIs, charts, collector health chip |
/live | Live | Heartbeats and tasks; split terminal + session waterfall |
/tasks | Tasks | Filter by tool, user, collector, retries, git repo/branch |
/tasks/:id | Task detail | Timeline, tokens, git project context, replay, Task ID |
/agents | Collectors | Fleet table. Open a hostname for identity, heartbeat, tools, tracing setup |
/traces | Traces | Span search — see Traces |
/cost | Cost | Spend by model/user |
/retries | Retries | Retry analysis |
/reports | Reports | Wizard; CSV / JSON / PDF |
/evaluations, /experiments, /playground | Evals | Definitions, A/B experiments, ad-hoc runs |
/patterns | Patterns | Topic clustering |
/settings/account | Account | Org metadata, agent API key copy/rotate, installer (owners/admins) |
Insights chat is a drawer (⌘J / Ctrl+J), not a route.
The header Collectors chip reflects heartbeats. Stale means no heartbeat within the manager stale-after window — not “this IDE produced no chats.”
IDs
| Label | Meaning | Where |
|---|---|---|
| Account ID | Organization UUID | Welcome / Account |
Agent API key (rk_live_*) | Ingest + OTel auth | Account |
| Agent ID | Collector UUID | Collectors details; ~/.agent-retry/agent-id |
| Task ID | Session UUID | Task detail — required to bind OTLP spans |
Never paste the API key into Agent ID or Account ID fields.
Filtering
Tasks, Traces, and several reports share Collector (agent UUID as the value, hostname as the label), tool, user, date, min retries, and git repo/branch when git query is on. Solo accounts hide the user picker when there is only one developer.
Git metadata on tasks is on by default in Cloud (TIER_4_CLOUD). Chat-only Cursor prompts that never touch a workspace often show — for repo/branch until an edit lands.