From 198d559c1ef7db1feb274372ae5ea0725f110d39 Mon Sep 17 00:00:00 2001 From: Docs Bot Date: Wed, 27 May 2026 16:54:35 +0000 Subject: [PATCH 1/4] Add Fleet Computer use documentation page --- src/docs.json | 3 +- src/langsmith/fleet/computer-use.mdx | 148 +++++++++++++++++++++++++++ 2 files changed, 150 insertions(+), 1 deletion(-) create mode 100644 src/langsmith/fleet/computer-use.mdx diff --git a/src/docs.json b/src/docs.json index 22a82ac05f..6c8903fe52 100644 --- a/src/docs.json +++ b/src/docs.json @@ -1018,7 +1018,8 @@ "pages": [ "langsmith/fleet/workspace-admin", "langsmith/fleet/agent-identity", - "langsmith/fleet/manage-agent-settings" + "langsmith/fleet/manage-agent-settings", + "langsmith/fleet/computer-use" ] }, { diff --git a/src/langsmith/fleet/computer-use.mdx b/src/langsmith/fleet/computer-use.mdx new file mode 100644 index 0000000000..48d615ce48 --- /dev/null +++ b/src/langsmith/fleet/computer-use.mdx @@ -0,0 +1,148 @@ +--- +title: Computer use +description: Give your Fleet agent access to a persistent Linux computer to run code, manage files, and make authenticated requests. +--- + +Computer use gives your Fleet agent access to an isolated Linux computer. The agent can write and execute code, manage files, install packages, and make authenticated outbound HTTP requests—all without exposing secrets to the language model directly. + + +Computer use is available on the Plus and Enterprise plans. + + +## Computer modes + +Fleet offers two computer modes. Select the mode that best matches how your agent works. + +### Shared computer + +All conversation threads share a single computer. The agent's filesystem, installed packages, and running processes persist across threads. + +Use this mode when you want state (files, installed dependencies, environment setup) to accumulate over time across multiple conversations. + +### Computer per thread + +Each conversation thread gets its own isolated computer. The computer is created fresh when a new thread starts and is archived when it goes idle. + +Use this mode when threads should be independent of one another, or when you want a clean environment for each conversation. + +## Configure computer use + + + + In [Fleet](https://smith.langchain.com/agents), select the agent you want to configure and click the **Edit** icon. + + + In the graph view, find the **Computer** node. Select either **Shared computer** or **Computer per thread**. + + + Click **Save changes**. + + + +## Access profiles + +Access profiles let the computer make authenticated requests to external services without exposing credentials to the agent. When the computer makes an outbound HTTP request to a matching host, a proxy intercepts the request and injects the configured credentials before forwarding it. The agent never sees the token or secret. + +Each access profile specifies: + +- **Hosts**: The target hostnames to match (for example, `github.com` or `*.slack.com`). +- **Credentials**: Either a workspace secret (for static API keys) or an OAuth connection (for user-delegated access). +- **Network scope** (optional): Whether to allow all outbound traffic, restrict it to an allowlist, or block a denylist of hosts. + +### Add an access profile + + + + Go to the [Fleet Integrations tab](https://smith.langchain.com/agents/tools) and navigate to the **Computer** section. Click **+ Add** and follow the prompts to configure the host patterns and credentials. + + + In the agent editor, click the **Computer** node. Click **+ Add** next to **Access profiles** and select the profile you created. + + + Click **Save changes**. + + + + +Access profiles are always referred to as "Access profiles" — not proxy profiles or sandbox policies. + + +## Computer lifecycle + +You can configure how long a computer stays active and how long stopped computers are retained. These settings are per-agent. + +### Idle timeout + +The idle timeout is a soft time-to-live (TTL). When the computer has not received any commands for the configured duration, it stops and the disk is archived. The agent can resume the same computer later without losing its data. + +Default: **15 minutes** + +Available presets: 2 min, 5 min, 15 min (default), 30 min, or a custom value. + +### Stopped computer cleanup + +The stopped computer cleanup period is a hard TTL. After a computer has been stopped for the configured duration, it is permanently deleted along with all disk data. + +Default: **14 days** + +Available presets: 1 day, 7 days, 14 days (default), 30 days, or a custom value. + + +The stopped computer cleanup setting applies to **Computer per thread** mode only. Computers in **Shared computer** mode are not automatically deleted. + + +### Configure lifecycle settings + + + + In [Fleet](https://smith.langchain.com/agents), select the agent and click the **Edit** icon. + + + In the **Computer** node, click the settings icon to open the **Computer lifecycle** panel. + + + Select a preset or enter a custom value for **Idle timeout** and, if using Computer per thread mode, **Stopped computer cleanup**. + + + Click **Save changes**. + + + +## Advanced: base snapshot + +A snapshot is the disk image used to boot the computer. By default, all Fleet agents use the workspace default snapshot, which is based on Ubuntu 22.04 and comes pre-installed with common utilities (Python 3, pip, git, curl, and build tools). + +You can create custom snapshots to pre-install packages, configure the environment, or use a larger disk. + +### Custom snapshot options + +| Option | Description | +|---|---| +| **Docker image** | The Docker image used to build the snapshot (for example, `ubuntu:24.04`). Defaults to `ubuntu:24.04`. | +| **Filesystem capacity** | Disk size in GiB (1–100 GiB). | +| **Private registry** | Optional link to a private container registry credential, for private Docker images. | + + +For agents using **Shared computer** mode, the snapshot cannot be changed after the agent is published. The computer retains its original snapshot for its lifetime. + + +### Create a custom snapshot + +Custom snapshots are created by workspace admins from the [Fleet Integrations tab](https://smith.langchain.com/agents/tools) under the **Computer** section. + +### Select a snapshot for an agent + + + + In [Fleet](https://smith.langchain.com/agents), select the agent and click the **Edit** icon. + + + In the **Computer** node, click the settings icon to open the **Computer lifecycle** panel. + + + In the **Snapshot** dropdown, select the snapshot you want the computer to boot from. + + + Click **Save changes**. + + From 178f3c7960b7805d890a60e5e4fecde613e6d3ab Mon Sep 17 00:00:00 2001 From: Florence Morris <1629446+fjmorris@users.noreply.github.com> Date: Thu, 28 May 2026 11:47:58 -0400 Subject: [PATCH 2/4] Incorporated feedback from Brace. --- src/langsmith/fleet/computer-use.mdx | 38 ++++++++-------------------- 1 file changed, 10 insertions(+), 28 deletions(-) diff --git a/src/langsmith/fleet/computer-use.mdx b/src/langsmith/fleet/computer-use.mdx index 48d615ce48..573eaa488f 100644 --- a/src/langsmith/fleet/computer-use.mdx +++ b/src/langsmith/fleet/computer-use.mdx @@ -1,9 +1,9 @@ --- title: Computer use -description: Give your Fleet agent access to a persistent Linux computer to run code, manage files, and make authenticated requests. +description: Give your Fleet agent access to a persistent virtual computer to run code, manage files, and make authenticated requests. --- -Computer use gives your Fleet agent access to an isolated Linux computer. The agent can write and execute code, manage files, install packages, and make authenticated outbound HTTP requests—all without exposing secrets to the language model directly. +Computer use gives your Fleet agent access to an isolated virtual computer. The agent can write and execute code, manage files, install packages, and make authenticated outbound HTTP requests, all without exposing secrets to the language model directly. Computer use is available on the Plus and Enterprise plans. @@ -23,7 +23,7 @@ Use this mode when you want state (files, installed dependencies, environment se Each conversation thread gets its own isolated computer. The computer is created fresh when a new thread starts and is archived when it goes idle. -Use this mode when threads should be independent of one another, or when you want a clean environment for each conversation. +Use this mode when threads should be independent of one another, or when you want a clean environment for each conversation. Often used when your agent may perform many write-heavy parallel tasks (for example, a software engineering agent). ## Configure computer use @@ -39,6 +39,10 @@ Use this mode when threads should be independent of one another, or when you wan + +The computer mode is set when the agent is created and cannot be changed afterward. + + ## Access profiles Access profiles let the computer make authenticated requests to external services without exposing credentials to the agent. When the computer makes an outbound HTTP request to a matching host, a proxy intercepts the request and injects the configured credentials before forwarding it. The agent never sees the token or secret. @@ -63,10 +67,6 @@ Each access profile specifies: - -Access profiles are always referred to as "Access profiles" — not proxy profiles or sandbox policies. - - ## Computer lifecycle You can configure how long a computer stays active and how long stopped computers are retained. These settings are per-agent. @@ -77,16 +77,12 @@ The idle timeout is a soft time-to-live (TTL). When the computer has not receive Default: **15 minutes** -Available presets: 2 min, 5 min, 15 min (default), 30 min, or a custom value. - ### Stopped computer cleanup The stopped computer cleanup period is a hard TTL. After a computer has been stopped for the configured duration, it is permanently deleted along with all disk data. Default: **14 days** -Available presets: 1 day, 7 days, 14 days (default), 30 days, or a custom value. - The stopped computer cleanup setting applies to **Computer per thread** mode only. Computers in **Shared computer** mode are not automatically deleted. @@ -98,7 +94,7 @@ The stopped computer cleanup setting applies to **Computer per thread** mode onl In [Fleet](https://smith.langchain.com/agents), select the agent and click the **Edit** icon. - In the **Computer** node, click the settings icon to open the **Computer lifecycle** panel. + Click the settings icon in the agent editor to open the settings popover, then select the **Computer lifecycle** panel. Select a preset or enter a custom value for **Idle timeout** and, if using Computer per thread mode, **Stopped computer cleanup**. @@ -110,26 +106,12 @@ The stopped computer cleanup setting applies to **Computer per thread** mode onl ## Advanced: base snapshot -A snapshot is the disk image used to boot the computer. By default, all Fleet agents use the workspace default snapshot, which is based on Ubuntu 22.04 and comes pre-installed with common utilities (Python 3, pip, git, curl, and build tools). - -You can create custom snapshots to pre-install packages, configure the environment, or use a larger disk. - -### Custom snapshot options - -| Option | Description | -|---|---| -| **Docker image** | The Docker image used to build the snapshot (for example, `ubuntu:24.04`). Defaults to `ubuntu:24.04`. | -| **Filesystem capacity** | Disk size in GiB (1–100 GiB). | -| **Private registry** | Optional link to a private container registry credential, for private Docker images. | +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](/langsmith/sandbox-snapshots). For agents using **Shared computer** mode, the snapshot cannot be changed after the agent is published. The computer retains its original snapshot for its lifetime. -### Create a custom snapshot - -Custom snapshots are created by workspace admins from the [Fleet Integrations tab](https://smith.langchain.com/agents/tools) under the **Computer** section. - ### Select a snapshot for an agent @@ -137,7 +119,7 @@ Custom snapshots are created by workspace admins from the [Fleet Integrations ta In [Fleet](https://smith.langchain.com/agents), select the agent and click the **Edit** icon. - In the **Computer** node, click the settings icon to open the **Computer lifecycle** panel. + Click the settings icon in the agent editor to open the settings popover, then select the **Computer lifecycle** panel. In the **Snapshot** dropdown, select the snapshot you want the computer to boot from. From cae8b70b9d707f804ecbc4615cbb69911cb75630 Mon Sep 17 00:00:00 2001 From: Florence Morris <1629446+fjmorris@users.noreply.github.com> Date: Thu, 28 May 2026 13:49:18 -0400 Subject: [PATCH 3/4] Modified computer-use.mdx to match actual Fleet UI. --- src/langsmith/fleet/computer-use.mdx | 99 +++++++++++++--------------- 1 file changed, 44 insertions(+), 55 deletions(-) diff --git a/src/langsmith/fleet/computer-use.mdx b/src/langsmith/fleet/computer-use.mdx index 573eaa488f..089042c8d5 100644 --- a/src/langsmith/fleet/computer-use.mdx +++ b/src/langsmith/fleet/computer-use.mdx @@ -1,63 +1,70 @@ --- title: Computer use -description: Give your Fleet agent access to a persistent virtual computer to run code, manage files, and make authenticated requests. +description: 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 make authenticated outbound HTTP requests, all without exposing secrets to the language model directly. +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 use is available on the [Plus and Enterprise plans](https://langchain.com/pricing). ## Computer modes -Fleet offers two computer modes. Select the mode that best matches how your agent works. - ### Shared computer -All conversation threads share a single computer. The agent's filesystem, installed packages, and running processes persist across threads. +All conversation threads share a single computer. The filesystem, installed packages, and running processes persist across threads. Shared computers are not deleted automatically. -Use this mode when you want state (files, installed dependencies, environment setup) to accumulate over time across multiple conversations. +Choose this mode when you want files, dependencies, or environment setup to accumulate across conversations. ### Computer per thread -Each conversation thread gets its own isolated computer. The computer is created fresh when a new thread starts and is archived when it goes idle. +Each conversation thread gets its own isolated computer. The computer starts fresh when a thread starts, and is archived when it goes idle. -Use this mode when threads should be independent of one another, or when you want a clean environment for each conversation. Often used when your agent may perform many write-heavy parallel tasks (for example, a software engineering agent). +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. + + - - In [Fleet](https://smith.langchain.com/agents), select the agent you want to configure and click the **Edit** icon. + + In the [Fleet](https://smith.langchain.com/agents) left navigation, under **My Agents**, click and select either **Create with AI** or **Blank agent**. Enter a name for your agent. - - In the graph view, find the **Computer** node. Select either **Shared computer** or **Computer per thread**. + + Under **Should your agent use a computer?**, select **Yes**, then choose **Shared computer** or **Computer per thread**. - - Click **Save changes**. + + Expand **Advanced** to choose a **Snapshot** for new computers. + + + Click **Create Agent**. - -The computer mode is set when the agent is created and cannot be changed afterward. - + +To create an agent with no computer access, select **No** (the default) under **Should your agent use a computer?**. + ## Access profiles -Access profiles let the computer make authenticated requests to external services without exposing credentials to the agent. When the computer makes an outbound HTTP request to a matching host, a proxy intercepts the request and injects the configured credentials before forwarding it. The agent never sees the token or secret. +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: -Each access profile 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}`). -- **Hosts**: The target hostnames to match (for example, `github.com` or `*.slack.com`). -- **Credentials**: Either a workspace secret (for static API keys) or an OAuth connection (for user-delegated access). -- **Network scope** (optional): Whether to allow all outbound traffic, restrict it to an allowlist, or block a denylist of hosts. +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 - Go to the [Fleet Integrations tab](https://smith.langchain.com/agents/tools) and navigate to the **Computer** section. Click **+ Add** and follow the prompts to configure the host patterns and credentials. + Go to the [Fleet Integrations tab](https://smith.langchain.com/agents/tools) and navigate to the **Computer** section. Click **+ Create profile** and follow the prompts to configure the host patterns and credentials. In the agent editor, click the **Computer** node. Click **+ Add** next to **Access profiles** and select the profile you created. @@ -69,60 +76,42 @@ Each access profile specifies: ## Computer lifecycle -You can configure how long a computer stays active and how long stopped computers are retained. These settings are per-agent. +The idle timeout and stopped computer cleanup control how long a computer stays active and how long it is kept after it stops. Both are configured per agent. ### Idle timeout -The idle timeout is a soft time-to-live (TTL). When the computer has not received any commands for the configured duration, it stops and the disk is archived. The agent can resume the same computer later without losing its data. +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 -The stopped computer cleanup period is a hard TTL. After a computer has been stopped for the configured duration, it is permanently deleted along with all disk data. +After a computer has been stopped for this duration, it is permanently deleted along with all disk data. Default: **14 days** -The stopped computer cleanup setting applies to **Computer per thread** mode only. Computers in **Shared computer** mode are not automatically deleted. +**Stopped computer cleanup** applies only to **Computer per thread** mode. Shared computers are not deleted automatically. -### Configure lifecycle settings - - - - In [Fleet](https://smith.langchain.com/agents), select the agent and click the **Edit** icon. - - - Click the settings icon in the agent editor to open the settings popover, then select the **Computer lifecycle** panel. - - - Select a preset or enter a custom value for **Idle timeout** and, if using Computer per thread mode, **Stopped computer cleanup**. - - - Click **Save changes**. - - - -## Advanced: base snapshot +## 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](/langsmith/sandbox-snapshots). -For agents using **Shared computer** mode, the snapshot cannot be changed after the agent is published. The computer retains its original snapshot for its lifetime. +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. -### Select a snapshot for an agent +## 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. - - In [Fleet](https://smith.langchain.com/agents), select the agent and click the **Edit** icon. - - - Click the settings icon in the agent editor to open the settings popover, then select the **Computer lifecycle** panel. + + In [Fleet](https://smith.langchain.com/agents), open the agent and click the settings icon in the agent editor. - - In the **Snapshot** dropdown, select the snapshot you want the computer to boot from. + + Scroll to the **Computer lifecycle** section. Set the **Snapshot**, **Idle timeout**, and, for **Computer per thread** mode, **Stopped computer cleanup**. Click **Save changes**. From 363f8bf71b838110a4ed3bc0c90184093de706a7 Mon Sep 17 00:00:00 2001 From: Florence Morris <1629446+fjmorris@users.noreply.github.com> Date: Thu, 28 May 2026 15:58:15 -0400 Subject: [PATCH 4/4] Incorporated feedback from Lauren. --- src/langsmith/fleet/computer-use.mdx | 38 ++++++++-------------------- 1 file changed, 10 insertions(+), 28 deletions(-) diff --git a/src/langsmith/fleet/computer-use.mdx b/src/langsmith/fleet/computer-use.mdx index 089042c8d5..a196df1d64 100644 --- a/src/langsmith/fleet/computer-use.mdx +++ b/src/langsmith/fleet/computer-use.mdx @@ -11,17 +11,12 @@ Computer use is available on the [Plus and Enterprise plans](https://langchain.c ## Computer modes -### Shared computer +Choose how the virtual computer is shared across an agent's conversation threads. -All conversation threads share a single computer. The filesystem, installed packages, and running processes persist across threads. Shared computers are not deleted automatically. - -Choose this mode when you want files, dependencies, or environment setup to accumulate across conversations. - -### Computer per thread - -Each conversation thread gets its own isolated computer. The computer starts fresh when a thread starts, 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. +| 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 @@ -34,7 +29,7 @@ The computer mode is set when the agent is created and cannot be changed afterwa In the [Fleet](https://smith.langchain.com/agents) left navigation, under **My Agents**, click and select either **Create with AI** or **Blank agent**. Enter a name for your agent. - Under **Should your agent use a computer?**, select **Yes**, then choose **Shared computer** or **Computer per thread**. + 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. Expand **Advanced** to choose a **Snapshot** for new computers. @@ -44,10 +39,6 @@ The computer mode is set when the agent is created and cannot be changed afterwa - -To create an agent with no computer access, select **No** (the default) under **Should your agent use a computer?**. - - ## 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. @@ -76,19 +67,10 @@ A profile also has a **Network scope** that controls outbound traffic for the ag ## Computer lifecycle -The idle timeout and stopped computer cleanup control how long a computer stays active and how long it is kept after it stops. Both are configured per agent. - -### 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. +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](#configure-lifecycle-and-snapshot). -Default: **14 days** +- **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. @@ -96,7 +78,7 @@ Default: **14 days** ## 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](/langsmith/sandbox-snapshots). +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](/langsmith/sandbox-snapshots). [Change the snapshot for an agent](#configure-lifecycle-and-snapshot) 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.