Skip to content
LogoLogo

Devin Outposts

createos sandbox setup devin runs an orchestrator on your Mac or Linux machine. Each Devin session gets a sandbox running devin-remote; the orchestrator claims queued sessions and connects their remote tools.

Setup

Install a CLI version with sandbox setup devin, authenticate with createos login, and create a Linux outpost in Devin under Settings → Environment → Outposts. Save the outpost token shown at creation in your local environment.

export DEVIN_API_TOKEN='<outpost-token>'
createos sandbox setup devin --outpost my-outpost --doctor
createos sandbox setup devin --outpost my-outpost

Leave the orchestrator running and select that outpost under Configuration → Virtual environment when starting a Devin session. The Devin API token stays on the orchestrator host; each sandbox receives only its session's connect token.

Configuration

FlagDefaultEnvironment override
--outpostRequired name or ID—
--shapes-4vcpu-8gbCREATEOS_DEVIN_SHAPE
--rootfsdevbox:1; use a Debian/Ubuntu-based image or templateCREATEOS_DEVIN_ROOTFS
--max-sessions2; keep within your account's sandbox quota—
--delete-paused-after168h (seven days); 0 disables this cleanupCREATEOS_DEVIN_DELETE_PAUSED_AFTER
--api-urlhttps://api.devin.aiDEVIN_API_URL
--doctorCheck prerequisites without serving—

The default shape must be available to your plan. Paused sandboxes still count against the account concurrency cap.

Session lifecycle

Suspending a session pauses its sandbox, preserving disk and memory. Resuming reconnects the session with a new connect token. Termination deletes the sandbox. The orchestrator uses createos.devin/outpost and createos.devin/session labels to rediscover its sandboxes after a restart.

Paused-session cleanup defaults to seven days while the orchestrator is running. Paused sandboxes continue to incur memory and storage charges; stopping the orchestrator is not a substitute for inspecting and cleaning up remaining sandboxes.

See CLI commands, labels, and pause/resume.