Availability
There is no built-in exe.dev adapter today. Connect it through a customer-installed custom capacity provider.
Integration shape
The setup, credentials, governed actions, and evidence should be obvious.
Agent loop
ExecWarden can host the loop, or an external client can own it. Customer-managed exe.dev capacity supplies optional compute for either architecture.
Tools
Files, commands, and processes belong to the execution environment; GitHub, MCP tools, and internal APIs can be exposed through ExecWarden.
Credentials
Use scoped MCP credentials for tools supplied by ExecWarden.
Governed actions
ExecWarden can govern mediated GitHub, package, imported MCP, and approval-gated actions.
ExecWarden evidence
The activity and approval records apply to calls made through ExecWarden.
Start
Implement and register the custom capacity provider, then connect the resulting execution environment to ExecWarden MCP with a scoped Agent identity.
Where the boundary is
How this boundary works in practice.
The execution environment governs files, shell, network, and local secrets. ExecWarden governs the credentials and capabilities it supplies.
Execution
Run the agent where it fits.
An external execution environment can handle files, commands, and processes for the task.
MCP
Call GitHub, MCP tools, or internal APIs through ExecWarden.
The agent can use a scoped MCP credential for GitHub, package-backed tools, or imported MCP capabilities.
Evidence
Keep governed actions visible.
Calls through ExecWarden can leave activity records, approval records, and provider results even when execution happens elsewhere.
Examples
Example tasks and outcomes.
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.