Lightweight hosted runtime
No machine attached
Bounded JavaScript, bounded public HTTP where enabled, and granted capability calls. No general shell, filesystem, git, or browser.
Plan and transform dataFetch public URLsInvoke granted tools
Agent loop versus execution
A hosted agent does not automatically get a machine.
When you choose an ExecWarden-hosted loop, ExecWarden keeps the transcript and run state. The execution choice decides whether the task gets only lightweight hosted tools or a customer-configured machine.
Connected execution environment
Customer-configured machine
A VM, Docker environment, or local machine provides the files, shell, processes, git, browser, tests, containers, and network access configured for the task.
Edit and test codeRun local processesReach private systems
Same governed capability layerGitHub, MCP tools, package-backed APIs, approvals, revocation, and activity records still follow the grants on the caller.
Connect it deliberately
Connect compute without blurring the trust boundary.
A connected environment is a place to execute, not a blanket of ExecWarden policy. Decide what the machine exposes locally, attach it to the run that needs it, and keep external credentials behind mediated capabilities where possible.
Customer configuration
Choose what the machine makes available.
The customer configures the VM, Docker host, or local machine, including its files, network reachability, installed software, and local secrets.
Run attachment
Attach execution capacity to the work that needs it.
A hosted session can bind to a sandbox volume on configured capacity. External clients use their existing environment and connect to governed tools through MCP.
Credential boundary
Keep external authority behind mediated tools.
A GitHub or SaaS credential held by ExecWarden follows grants and approvals. A separate token placed on the machine can be used outside that path.
Examples
Tasks that fit each execution shape.
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.