Environments

Sandbox compute leases attached to sessions, with an audit timeline.

The Environments screen lists the sandbox compute leases attached to your sessions. Each lease is a sandbox — an isolated environment where an agent’s tools run. For the concept, see Sandboxes.

A paused sandbox preserves its filesystem and memory and resumes on the next tool call, so an agent can pick up exactly where it left off.

Filtering the leases

Narrow the table by session, agent, provider, or state.

Leases table

Column	Meaning
Agent	The agent the lease belongs to.
Sandbox	Sandbox ID, with a link to its session.
Provider	The sandbox backend.
State	ready, paused, closed, or errored.
Last activity	Most recent tool activity.
Allocated	When the lease was created.

Environments — sandbox compute attached to agent sessions (shown before any session has started).

Lease detail

Click a row to open the detail sheet. It shows the lease metadata and an audit timeline of lifecycle events — allocate, pause, resume, release, and error — each with trace and span IDs for correlating with your observability data.

Related

Sandboxes

What sandboxes are and how they run tools.

Stats

Fleet-wide sandbox KPIs and audit feed.