Agent runtime

Start persistent agent work from ExecWarden.

ExecWarden can host the agent loop and keep its transcript, approvals, and mediated tool calls together. Use lightweight gateway-backed work without a machine, or connect execution capacity for a machine-backed interactive session.

Identity and mediated activity

Keep the caller, its grants, and tool-call results inspectable.

Each named Agent identity keeps its authority and mediated tool-call records together. The activity log does not claim visibility into commands or credentials used directly inside a connected execution environment.

Maintenance Agent identity with a scoped GitHub grant
The named caller carries its own grant scope, mode, and lifecycle.
Recent mediated GitHub activity showing successful, failed, and approval-paused calls
The identity view keeps several outcomes visible without presenting local machine work as gateway activity.

What you can do

Keep the run visible without assuming it has a machine.

Start with bounded JavaScript, bounded public HTTP where enabled, and granted capabilities. Add a customer-configured VM, Docker environment, or local machine only for tasks that need shell, files, git, browser, tests, or private-network access.

Persistent sessions

Keep task state attached to the run.

Hosted run state keeps the transcript, tool calls, approvals, and status together across lightweight and machine-backed paths.

Tool boundary

Give the session only the capabilities it needs.

Attach GitHub, package-backed APIs, and imported MCP tools through scoped Agent authority. Configure execution capacity separately when the task needs a machine.

Compute when needed

Connect a machine for machine-shaped work.

A customer-configured VM, Docker environment, or local machine supplies the shell, files, git, browser, processes, and network access configured for the task.

Examples

Hosted tasks with and without connected compute.

1Research public information and call granted APIs without attaching a machine.
2Attach customer compute for a repo investigation, tests, and branch output.
3Move a trusted task toward a workflow after the manual run is useful.

Get started during beta

Start with one bounded task and one boundary to review.

Use the app during beta, or open the docs and choose the first agent task you want to govern.

Start an agentReview trust boundaries