Platform
Workspace overview
Start a new workspace with its first trace, then use /app as the daily launch point for approvals, blocked evals, alerts, trace errors, connected agents, and fleet health.
On this page
Start here
The overview shows needed attention and system health. New workspaces get a path to their first trace; active ones see approvals, evals, alerts, trace errors, agents, and fleet state.
Before you begin
- A signed-in workspace member at /app
- Owner or admin access to the workspace-key page and a trace client
Put it into practice
-
Complete first-run ingest
Open /app/agents/workspace-key, create the primary key, store its one-time secret, and use it in the dashboard curl example. The current Create key link opens agent credentials, which requires a service agent.
-
Confirm the live picture
Return to /app, verify the trace appears, and open it for event-level evidence.
-
Work the attention queue
Open pending approvals, blocked evals, active alerts, and recent trace errors from the overview, then resolve them in their dedicated screens.
The workspace records its first trace, shows current summaries, and links each attention item to its action screen.
01 First run
detailsThree steps to your first trace
When the workspace has neither a machine key nor a trace, the dashboard shows key, trace, and eval steps; a marketplace-provisioned workspace instead shows a one-line note that its traces arrive from hires and no API key is needed. Owners and admins should create the primary key at /app/agents/workspace-key, then use it in the displayed POST /api/v1/traces curl. The dashboard's current Create key link opens /app/agents/credentials, which requires an existing service agent and does not create the workspace primary key.
02 Attention
detailsLive queue
The home brings together up to four of: pending approvals, blocked evals, open alerts, recent trace errors, and machine-access gaps (a missing workspace key or agents without credentials), so an operator can triage before opening /app/approvals, /app/evals/runs, /app/alerts, /app/traces, or /app/agents for the full evidence and supported action.
Troubleshooting
- The first-run panel remains
- Confirm a key and trace exist. Without a service agent, use /app/agents/workspace-key instead of the current credentials CTA; then check the curl response.
- Counts look unfamiliar
- Verify the active workspace and follow the linked detailed screen. The overview is a summary, not a replacement for trace, eval, approval, or fleet records.
- An attention item cannot be resolved here
- The home is a triage surface. Open the corresponding approval, eval review, alert, or trace page to perform the supported action.