Computer use

Run code, manage files, and call authenticated APIs from a persistent virtual computer attached to your Fleet agent.

Computer use gives your Fleet agent access to an isolated virtual computer. The agent can write and execute code, manage files, install packages, and call authenticated external APIs without exposing credentials to the language model.

Computer use is available on the Plus and Enterprise plans.

Computer modes

Choose how the virtual computer is shared across an agent’s conversation threads.

Mode	Description
Shared computer	All threads share a single computer. The filesystem, installed packages, and running processes persist across threads. Choose this mode when you want files, dependencies, or environment setup to accumulate across conversations. Shared computers are not deleted automatically.
Computer per thread	Each thread gets its own isolated computer that starts fresh and is archived when it goes idle. Choose this mode for software-engineering agents and other workloads that run many parallel, write-heavy tasks, or for any case where threads should not see each other’s state.

Configure computer use

The computer mode is set when the agent is created and cannot be changed afterward. To switch modes, create a new agent.

1. Open the Create agent dialog

   In the Fleet left navigation, under My Agents, click and select either Create with AI or Blank agent. Enter a name for your agent.

2. Enable computer use

   Under Should your agent use a computer?, select Yes, then choose Shared computer or Computer per thread. If you select No (the default), the agent is created with no computer access.

3. Set the base snapshot (optional)

   Expand Advanced to choose a Snapshot for new computers.

4. Create the agent

   Click Create Agent.

Access profiles

Use access profiles to let your agent call authenticated external APIs without putting credentials in the prompt or exposing them to the language model. Outbound HTTP requests to matching hosts are routed through a proxy that injects the configured headers before forwarding.

A profile contains one or more Custom rules. Each rule specifies:

• Match Hosts: The target hostnames the rule applies to. Use * as a wildcard (for example, *.example.com matches api.example.com).
• Source Type and Provider: The credential source. Choose Connection for user-delegated OAuth, or Workspace Secret for static API keys.
• Inject Headers: The HTTP headers the proxy adds to matched requests. Use template values such as {access_token} to reference the credential (for example, Authorization: Bearer {access_token}).

A profile also has a Network scope that controls outbound traffic for the agent’s computer. The default is None (all traffic allowed).

Add an access profile

1. Create the access profile

   Go to the Fleet Integrations tab and navigate to the Computer section. Click + Create profile and follow the prompts to configure the host patterns and credentials.

2. Attach the profile to an agent

   In the agent editor, click the Computer node. Click + Add next to Access profiles and select the profile you created.

3. Save changes

   Click Save changes.

Computer lifecycle

Each agent has two lifecycle settings that control how long a computer stays active and how long it is kept after it stops. Configure both in the settings popover.

• Idle timeout: When the computer has not received any commands for this duration, it pauses and the disk is archived. The agent can resume the same computer later without losing data. Default: 15 minutes.
• Stopped computer cleanup: After a computer has been stopped for this duration, it is permanently deleted along with all disk data. Default: 14 days.

Stopped computer cleanup applies only to Computer per thread mode. Shared computers are not deleted automatically.

Base snapshot

A snapshot is the disk image used to boot the computer. By default, all Fleet agents use the workspace default snapshot. To build, capture, or configure custom snapshots, see Sandbox snapshots. Change the snapshot for an agent in the settings popover.

Snapshot changes apply only to new computers for the agent. The single shared computer in Shared computer mode keeps its original snapshot for its lifetime.

Configure lifecycle and snapshot

The snapshot, idle timeout, and stopped computer cleanup for an agent are all set in the Computer lifecycle section of the settings popover.

1. Open the settings popover

   In Fleet, open the agent and click the settings icon in the agent editor.

2. Set the lifecycle fields

   Scroll to the Computer lifecycle section. Set the Snapshot, Idle timeout, and, for Computer per thread mode, Stopped computer cleanup.

3. Save changes

   Click Save changes.

---

Connect these docs to Claude, VSCode, and more via MCP for real-time answers.

Edit this page on GitHub or file an issue.