Every run, traced.
Studio is the visual console for your agent. Every invocation opens as a trace — a waterfall of steps with timing, the model calls it made, structured logs and the cost it spent — and the same console browses the agent's database, RAG, storage, queues, secrets, config and contract, clears human approvals in an inbox, and fires test runs from the Playground. The same console UI runs against your local stackbone dev emulator (its Studio API on localhost:4242) and, unchanged, against the cloud.
Studio comes up with stackbone dev
- 11 screens
- same console local & cloud
- per-run cost
trigger webhook · duration 4.18 s · cost $0.0413 · trace 7f3a…
illustrative trace
A run opens as a waterfall of steps. Click a step to inspect what it did — its timing, its status and its payload.
invoke
healthy- Duration
- 4.18 s
- Start
- 2026-06-04T09:41:02.118Z
{
"input": { "query": "refund over 500 EUR?" },
"trigger": "webhook"
}A trace is a waterfall of these step types, indented by parent.
Cost shown as the run's estimated USD; duration as ms under a second, then seconds.
Studio is the console docked at the bottom of the app shell, scoped to the active agent. It has three discrete states — no drag handle.
Panel expands; the shell stays visible in the top ~30%. Screens get the full width.
Closing returns to collapsed — the bar is always part of the shell, never hidden.
Refresh starts collapsed; no auto-expand.
ctrl ` toggles collapsed ↔ mid · scoped to the active agent.
A dock state only changes the panel's height — not which screen you're on. The DB Explorer is shown at max simply because a wider, table-heavy screen is what benefits from the extra height.
The same console hosts everything that touches the agent — grouped by what you reach for.
The HITL Inbox dot is amber to mark a state — approvals awaiting a human — not a live count.
The Playground sends a real invocation — the browser sets X-Stackbone-Playground: 1 — and it bills like any other run. It is excluded only from public Trust-Layer metrics.
{ "query": "refund over 500 EUR?" }opens as a trace, same as any run.
- Reinvoke in Playground
- View run logs
- Open in Tempo
the console you debug in is the console you ship.
One Studio UI. It runs locally under stackbone dev and docks into the cloud shell — same trace, same explorers, same inbox, same Playground.
- The trace
- The explorers
- The HITL inbox
- The Playground
See every run while you build.