Skip to content

Sandboxes

A sandbox is an isolated environment where an employee runs code, browses the web or uses a computer. Each sandbox is created for one run, cut off from your other systems, and destroyed when the run ends.

Type What the employee can do Example tools Typical use
Code Run Python, JavaScript or shell commands, install packages, read and write files code.run, code.install, files.write Analyze a spreadsheet, build a chart, transform data
Browser Open pages, click, type, fill forms and download files in a headless browser browser.open, browser.click, browser.fill, browser.extract Read sites without an API, fill supplier portals
Computer See a full Linux desktop through screenshots and use the mouse and keyboard computer.screenshot, computer.click, computer.type Work in desktop apps or legacy web apps

Code and Browser sandboxes are on by default. An Owner or Admin turns on Computer in Settings → Capabilities → Sandboxes.

  • Each sandbox runs in its own virtual machine, with its own kernel. It shares nothing with other runs, other employees or other workspaces.
  • A sandbox has no access to your connectors’ credentials. To act in an app, the employee calls a connector tool, outside the sandbox.
  • A sandbox starts from a clean image. Nothing persists between runs unless you save it as a file.
  • Sandboxes run in your workspace’s data region, EU or US.

The employee works in a /workspace folder inside the sandbox.

Direction How
In Files attached to the task, files from a knowledge base and files from connectors (such as a Drive document) are copied into /workspace when the run starts.
Out Files the employee saves to /workspace/output are attached to the run as artifacts. Download them from the run, or let the employee upload them with a connector tool.

Files larger than 500 MB aren’t copied in. See Limits.

By default, a sandbox can reach only package registries (PyPI, npm) and the domains in the egress allowlist. Set the allowlist in Settings → Capabilities → Sandboxes → Network, or per employee on its Tools tab.

Mode What the sandbox can reach
Off Nothing. For code that must only work on the files it’s given.
Allowlist Package registries and the domains you list, such as *.acme.com or data.gov. Default.
Open Any public address, except private ranges and cloud metadata endpoints.

Payments from a sandbox go through x402, from the employee’s wallet, under the usual checks. A sandbox never holds wallet keys.

What happens inside the sandbox doesn’t change anything outside it, so most sandbox tools are Read or Draft. Some actions are classified higher:

Action Impact class
Submit a form on an external site Communicate
Log in to a site with credentials you stored Write internal
Complete a purchase in a browser Spend

The employee’s autonomy level applies to these actions as to any other tool call. At L1, for example, the employee pauses before submitting a form and shows you a screenshot of it.

Every Browser and Computer session is recorded. Open the run in Activity and click the sandbox step to watch the replay, with each click and keystroke marked on the timeline. Code sessions keep the full log of commands and outputs.

Typed passwords and fields marked as secret are masked in recordings. Recordings follow the workspace retention period set in Compliance.

Limit Default Maximum
Session duration 15 minutes 60 minutes
Idle time before shutdown 3 minutes 10 minutes
CPU 2 vCPU 8 vCPU
Memory 4 GB 16 GB
Disk 10 GB 50 GB

When a session reaches its limit, Orqane saves the files in /workspace/output, stops the sandbox and lets the employee decide whether to start a new session. Sandbox time is billed in credits. See Billing.