Building and deploying
What happens after you create an agent — build progress, live logs, health states, and the failure diagnostics surfaced in the console.
When you create an agent (or apply a skill edit), the platform builds a container image for it and deploys it into your workspace. You don't run anything yourself — the console shows the whole process live.
Build progress
Right after create, the screen switches to a progress view that polls the build and streams its logs:
| Phase | Meaning |
|---|---|
| Building | The agent image is being generated and built. |
| Deployed / Starting up | The image was deployed; the agent is starting. |
| Running | The agent is up and healthy — terminal success state. |
| Degraded | The agent deployed but is not fully healthy. |
| Failed | The build or deployment failed — terminal failure state. |
The log panel pins to the newest line as the build streams. If a build runs unusually long, the view notes it is still deploying — you can leave and check back from the agent's detail page, which refreshes live while the agent is settling.
From the terminal states you can jump to the agent, create another, or (on failure) go back and adjust the configuration before retrying.
Health states
Every agent shows a status chip on the Agents list and its detail page: running, deployed, degraded, or failed (plus in-progress states while building). Health is read live from the running deployment, not from a stored snapshot, so the chip reflects what is actually happening right now.
Failure diagnostics
When an agent is degraded or failed, the detail page shows an actionable callout — not just a status chip:
- Runtime failures include per-container diagnostics: image pull errors, crash loops with the last exit reason, and unschedulable pods.
- Build-stage failures have no running containers to inspect, so the callout falls back to the stored build error explaining which step failed.
The same diagnostics appear as marked lines in the create screen's log stream, so a failure is visible without leaving the create flow.
Diagnose
The Diagnose button on the agent detail page gathers the agent's evidence in one click — live health, the build error, recent audit events, and a log tail — and returns a diagnosis with a probable cause, suggested remediation, and citations. Every citation resolves to the same data shown in the Activity and Logs tabs, so nothing is claimed that you can't verify yourself. Diagnose is prominent when a failure callout is showing, and still available when health is green — behavior problems like policy denials or wrong outputs exist without any infrastructure failure.
Observing a running agent
The agent detail page has tabs for day-to-day operation:
- Overview — chat with the agent directly and browse its sessions.
- Activity — the agent's runtime audit event stream, grouped by run, with an in-place event drawer. Retained even after an agent is deleted.
- Logs — a bounded raw tail of the agent container for the cases events can't explain (stack traces, print debugging). Choose the tail size, refresh on demand, search with match highlighting, and read the previous instance to see the output of a container that crashed and restarted.
- Usage — the agent's model and token usage.
- Settings — egress, skill editing, environment variables, and deletion. See Secrets and environment.
Rebuilds and restarts
Two different update paths, with very different costs:
- Skill or egress changes rebuild the agent image and redeploy it — this takes a few minutes and goes through the same progress view as the first build.
- Environment value changes patch the agent's secret and restart it — no rebuild, effective in seconds.