fabro/docs/integrations/exe-dev.mdx
Bryan Helmkamp 44731e0926 Rename arc setup to arc install for clarity
The one-time environment setup command (LLMs, certs, GitHub) is now
`arc install`, freeing up naming space for a future `arc init` command
for per-project initialization.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-10 12:56:53 -04:00

54 lines
1.7 KiB
Text

---
title: "exe.dev"
description: "Run Arc workflows in fast ephemeral VMs from exe.dev"
---
<Warning>
The exe.dev sandbox provider is **under development**. It requires building Arc with the `exedev` feature flag enabled. The API and configuration may change.
</Warning>
[exe.dev](https://exe.dev) provides fast ephemeral cloud VMs for Arc workflows. Each run gets a fresh VM with full machine-level isolation, connected via SSH.
## How it works
- Each run creates a new VM via the exe.dev management plane over SSH
- Arc clones the current git repository into the VM automatically (using GitHub App credentials for private repos)
- Agent tool calls (shell commands, file edits, grep, glob) execute over SSH inside the VM
- Git checkpointing commits agent changes to a remote branch between stages
- Cancelling a run cleanly tears down the VM
- VMs are destroyed automatically when the run finishes
## Configuration
```bash
arc run workflow.dot --sandbox exe
```
```toml title="run.toml"
[sandbox]
provider = "exe"
[sandbox.exe]
image = "my-custom-image:latest"
```
| Field | Description |
|---|---|
| `image` | Custom container image for the VM. Optional — uses the exe.dev default when omitted. |
## SSH access
Connect to a running exe.dev sandbox via SSH for live debugging:
```bash
arc run workflow.dot --sandbox exe --ssh
```
This prints the SSH connection command so you can connect to the VM while the workflow runs.
## Prerequisites
- SSH keys configured for exe.dev (added via the [exe.dev dashboard](https://exe.dev))
- A [GitHub App](/integrations/github) configured via `arc install` (for private repository cloning)
See [Environments](/execution/environments#exe) for additional details on how the exe.dev sandbox operates.