Run Droids on an Environment

Start a cloud session#

1. 1
   Create a new session in the Factory App.
2. 2
   Open the computer or Run on picker and choose a Ready Environment. If an organization default is available to you, it may already be selected.
3. 3
   Review the repository summary and any branch options shown for your session.
4. 4
   Enter your task and send it.

Factory creates a Computer from the Environment's successful snapshot, provisions runtime credentials, connects Droid, and starts the session. Provisioning progress is shown while it prepares. An Environment with no successful build is not a launch target yet.

If the picker does not offer Environments, check availability and compute policy. New environment in the picker opens Environment settings.

Run multiple Droids in parallel#

Start another new session, select the same Environment, and give it a separate task. Each launch creates its own instance, so agents do not share working-tree changes. You can run different tasks against the same prepared baseline without repeating setup.

Parallel launches still depend on organization compute limits, provider capacity, repository access, and model usage allowances. A reusable snapshot is not a promise of unlimited concurrent compute.

Push branches or save durable outputs before relying on another instance to see them. An instance's changes are not written back into the Environment snapshot. Instance lifetime depends on the workflow that created it; do not treat a fresh Environment launch as your only permanent copy of work.

Create a persistent Droid Computer#

For a computer you want to reuse across sessions:

1. 1
   Open Settings → Droid Computers and click Create.
2. 2
   Name the computer and review its owner and provider options. When Environments are enabled for your organization, select a Ready Environment in the wizard's Environment selector.
3. 3
   Complete the remaining repository and setup options, then create the computer.

The Environment selector appears in the regular computer creation wizard when your organization has Environments enabled; it is not offered in the bulk scratch-computer wizard for delegation worker pools. See Create a Droid Computer for the complete flow.

The new computer starts from that snapshot but keeps its own subsequent state. Later Environment rebuilds do not modify it. This flow can remain available even when your organization restricts direct Environment session launches.

Configure delegation compute#

A manager or owner configures shared execution in Settings → Delegations:

1. 1
   Open the delegation configuration wizard and choose an active service-account identity.
2. 2
   In Compute, choose Dynamic.
3. 3
   Choose Use existing environment, or New environment to create one without leaving the wizard.
4. 4
   Select an organization Environment and finish the configuration. Wait until its build is Ready before delegating work.

Each configuration uses one Environment. To change it, remove the current selection before choosing another. Personal Environments are not eligible for this shared configuration.

The service account needs repository access and receives organization and service-account runtime secrets. Connecting Slack, Linear, Jira, or Microsoft Teams does not replace source-control setup. Follow the provider-specific Delegations guides for integration setup and triggering tasks.

Configure automation compute#

In an automation creation flow that offers Run on, choose a Ready Environment instead of an existing Computer. When your organization permits Environment launches, the picker offers Environments accessible to the selected run identity, whether you run as yourself or an eligible service account.

For scheduled automations, Create with session opens a setup session on a new instance. Slack and webhook automations use Create and do not open a setup session. Each Environment-backed run starts on a fresh instance; it does not reuse a setup computer or the previous run's working directory.

Use Create with Template to start from an automation prompt or trigger preset. See Automations for schedules, triggers, run identities, and how each automation uses its computer.

Configure Mission compute#

When the Mission worker-machine chooser offers Environments, select a Ready Environment for workers that need the same repositories and tools. Workers use separate instances; building or failed Environments cannot provide a new baseline. You can also configure an Environment in Settings → Mission defaults where available.

Use Missions for planning, worker concurrency, and execution controls. Environment setup does not replace a Mission's own availability or usage requirements.

Inspect the organization fleet#

Managers and owners can open Settings → Fleet, then Environment Instances. The overview groups instances by Environment; choose an Environment to inspect its computers. Search, filters, sorting, and refresh help find instances by owner, source, and recent activity.

The Fleet view also separates persistent Droid Computers and Remote Control computers. Use it for inventory, not to edit an Environment's build configuration.