Depot
Log in
Managed agents

Run Devin in Depot sandboxes

Run Devin Outpost sessions in Depot sandboxes through Devin's web interface. Depot starts and manages the runner for you. View run status, timing, and failure details in your Depot dashboard.

How it works

Devin is Cognition's AI software engineering agent for writing, running, and testing code.

An Outpost is a queue of Devin sessions waiting for compute. You connect an Outpost to Depot and select it when starting a session in Devin.

Depot checks the queue, claims a session, and starts the Devin runner in a sandbox. You continue the conversation in Devin while the runner executes tools in the sandbox. You don't need to install or start a worker yourself.

How Devin runs on DepotStart a session in Devin with your connected Outpost selected. Devin queues the session in the Outpost. Depot checks the queue, claims a session, and starts a Devin runner in a sandbox. The runner connects to Devin's gateway with a session credential, receives tool calls, executes commands and file operations, and sends results back to Devin. You continue the conversation in Devin.DevinDepotSandbox managementStarts sandboxesDevin web interfaceYour task & OutpostStarts sessionOutpost & gatewaySession queueClaims sessionStarts runnerDepot sandboxDevin runnerCommands & filesTool callsResults

Get started

Prerequisites

Before you start, you need:

  • A Depot account with the Owner role in your Depot organization.
  • A Devin account with Outposts enabled.
  • A Devin administrator who can manage enterprise settings and service users.

Connect Devin to Depot

  1. Open Settings > Connections > Agent providers in Depot and select Devin.
  2. Click Connect with Devin.
  3. Sign in to Devin if prompted.
  4. Confirm the Outpost name and keep Linux as the platform.
  5. Click Connect in Devin.

Devin creates an Outpost and a service user for Depot. When setup completes, Depot shows Connected to Devin and the Outpost ID. You don't need to copy the Outpost ID or service user token.

Depot keeps the service user token outside the sandbox. The runner receives a credential for the session Depot claims.

Choose a sandbox size

The default sandbox size is 4x16 (4 CPUs, 16 GB memory). To change the sandbox size, open Settings > Managed Runs and click Run settings for the connection. In the Sandbox table, select a Size in the Default row and click Save. See sandbox sizes for available sizes, billing, and when changes take effect. To run on ARM64 instead of x86-64, select arm64 under Sandbox architecture in the same section. See sandbox architecture for what changes. To start runs without Depot Cache credentials, turn off Depot Cache in the same section and click Save. See turn off Depot Cache for runs.

Start a Devin session

  1. Start a new session in Devin.
  2. Under Configuration > Virtual environment, select the Outpost you connected.
  3. Send a task, such as “Create a hello.txt file containing Hello from Depot.”

Depot claims the session and starts its sandbox. Devin's response appears in the same conversation.

Add Depot's MCP server in Devin

Devin reads MCP servers only from your Devin organization's settings, so Depot can't add its server for you. To give Devin the tools from your organization's MCP servers, add Depot's server in Devin once:

  1. In Devin, open Customize > MCPs and add a server.
  2. Name it depot and choose HTTP as the type.
  3. Enter http://127.0.0.1:47917/ as the URL.
  4. Set Execution location to Session machine.
  5. Save the server.

Depot runs this server inside each sandbox and signs every request with the run's identity, so the server needs no token. Devin sessions on your Outpost then list the depot server and its tools. Sessions that run outside Depot can't reach it.

Verify your run in Depot

Open Managed Runs in your Depot dashboard and choose Devin in the provider filter to see your runs, newest first. You can also filter by status.

Managed Runs list filtered to Devin, with status filters and a list of runs

Select a run to see its status, duration, and steps. Each step also shows its duration and its log, and the setup script step shows the script's output. If the run failed, a banner shows the reason.

The Agent panel shows the sandbox ID. The Outputs panel lists the files the run saved, which you can download. See Save files from a run.

Use Open in Devin to return to the conversation when the link is available.

Devin run page showing its status, duration, steps, Outputs and Agent panels, and the Open in Devin button

From the run page, organization owners can stop a run that's still working. See Stop a run.

What's next

Give Devin a repository task, such as fixing a bug, adding tests, or updating a dependency, and select your connected Outpost. You can close your laptop while Devin works on Depot, then return to the conversation to review progress and give follow-up instructions.

Continue working by sending another message in the same Devin conversation. If the session needs a new sandbox, Depot restores the latest available workspace snapshot. See Session continuity for details and limitations.