> ## Documentation Index
> Fetch the complete documentation index at: https://docs.asteroid.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Environments

> The three sandboxes a workflow runs in — Browser, Linux and Windows — and what it can do in each.

Every workflow runs inside an isolated sandbox. The **environment** decides what that sandbox is, and how the workflow acts on the target system.

A workflow has one environment. You set it in [Workflow settings](/concepts/workflow-settings), and it applies to every node.

| Environment | Best for                   | How the workflow acts                    |
| ----------- | -------------------------- | ---------------------------------------- |
| **Browser** | Web apps and websites      | Page structure, scripts, and screenshots |
| **Linux**   | Linux desktop applications | Screenshots, mouse and keyboard          |
| **Windows** | Windows-only software      | Screenshots, mouse and keyboard          |

The environment also decides which capabilities an Agent node can use. See [What a node can do](/concepts/node-capabilities).

| Environment      | `browser_use` | `computer_use` |
| ---------------- | ------------- | -------------- |
| Browser          | On by default | Off by default |
| Linux or Windows | Always off    | Always on      |

***

## Browser

The Browser environment runs the workflow in a headless Chromium sandbox.

Choose it when the work happens on the web:

* filling forms and moving through web apps
* pulling structured content out of pages
* running deterministic browser automation
* mixing scripted steps with model-driven interaction

A node in this environment has three ways to act, and one workflow can mix all three:

* **Page structure** — click, type and select by reading the DOM. This is the default.
* **Scripts** — deterministic JavaScript for precise, repeatable steps.
* **Computer use** — screenshot and coordinate actions, for pages the DOM cannot handle.

Browser downloads land in `downloads/`. See [Workflow filesystem](/concepts/filesystem).

***

## Linux

The Linux environment gives the workflow a full Linux desktop session in an isolated sandbox.

Choose it when the work goes past the browser:

* driving native desktop applications
* running terminal-driven work
* handling local files through desktop tools
* mixing browser and desktop steps in one execution

The workflow works through **computer use**. The model reads screenshots and issues mouse and keyboard actions to control the desktop.

***

## Windows

The Windows environment gives the workflow a Windows desktop session in an isolated sandbox.

Choose it when the work depends on Windows-only software:

* enterprise desktop tools
* vendor clients that ship for Windows only
* internal apps that need a Windows runtime

The workflow works through **computer use**, the same way it does on Linux.

<Info>
  Windows workflows start after a demo with our team. Ask us at [support@asteroid.ai](mailto:support@asteroid.ai).
</Info>

***

## What every environment shares

The sandbox layout is identical in all three. Each execution mounts `/home/agent` with the same four directories — `shared/`, `workspace/`, `downloads/` and `uploads/`. File handling and tool behaviour do not change with the environment. See [Workflow filesystem](/concepts/filesystem).

Credentials, cookies and proxy settings come from the attached [agent profile](/concepts/profiles), whatever the environment.

<Tip>
  Computer use is slower and costs more than browser use. Pick Browser when the task can be done on the web.
</Tip>

<CardGroup cols={2}>
  <Card title="What a node can do" icon="wand-sparkles" href="/concepts/node-capabilities">Capabilities and the tools they unlock</Card>
  <Card title="Workflow settings" icon="settings" href="/concepts/workflow-settings">Where you choose the environment</Card>
</CardGroup>