ParallelSandbox

View saved version →

---
name: parallelsandbox
description: Build, run and test code in ParallelSandbox remote computers, inspect sandbox status and logs, and deliver working previews. Use for requests to operate ParallelSandbox or run a project remotely; ordinary chat and research do not need a box.
---

# ParallelSandbox

Use the connected `parallelsandbox` MCP tools. The box is a remote computer;
you drive it with tools. It does not contain another AI. Use the person's
language for box names, goals, step notes and explanations.

## Connect and inspect

If the connection needs authentication, direct the person to the plugin's
Connect action and complete ParallelSandbox's OAuth sign-in and consent.
Never request or paste an API key or access token into chat or a box.
Verify a connection with the read-only `sandbox_list`; do not start a billable
box just to check that login works.

For status or log requests, use `sandbox_list`, `sandbox_status` or `logs_*`
directly. The list includes other conversations' and teammates' boxes in the
same account. Before resuming an existing box, read its `goal`, `steps` and
`agent` using `sandbox_status`. If another conversation is working or away
and `thisConversation` is false, ask before taking over. Stop only a box
created for this task or one the person explicitly authorized you to stop.

## Run a task

1. Start one box with `sandbox_start`. Give it a descriptive `name` and a
   `goal` explaining the task and what completion means. Default to size 1;
   use a larger size or optional toolchain when the project needs it. Sandbox
   usage consumes the connected account's credits. If it is still starting,
   use `sandbox_status` until ready.
2. Declare the services the project will run. Mark a service `web: true` when
   the person will use its page. Processes listen on `0.0.0.0` at their
   `targetPort` (default `port`). Ports 80 and 9095 are reserved inside the
   box; a service advertised on one of those ports needs a different
   `targetPort`. Proxy browser API requests through the frontend's same
   origin to the API service's internal name and port.
3. Put the source in the box, build it and run it. Use `sandbox_exec` for
   shell commands, supplying a short `note` for each step. Use
   `sandbox_build` for reusable install or build steps. Start a dev server
   with `background: true` and use `sandbox_procs` to inspect, wait for or
   stop that process. Commands run in `/work`; use the appropriate `cwd`.
4. Verify the requested behavior. Run relevant tests, and use headed browser
   tests and `sandbox_shot` when the result needs visual verification.
   `sandbox_scene` runs JavaScript in a page the person has open at one of
   the box's URLs on their own device; it does not drive the box's browser.
   Inspect errors with `logs_errors` or `logs_search` when
   the project has a log service; otherwise read the process's log in the
   box. Use `sandbox_takeover` for a login or other step the person must do
   on the box's screen.
5. Finish the box according to the delivery instructions below. Explain what
   you checked, what succeeded and any unresolved limitation.

## Source and file transfers in ChatGPT

This plugin connects to the remote HTTP endpoint. It cannot read or write
the person's computer through `sandbox_sync` or `sandbox_pull`; those tools
require the separate local stdio adapter.

- For an existing repository, clone its committed source with `sandbox_exec`,
  for example `git clone https://github.com/OWNER/REPO.git /work/project`.
  Follow that repository's instructions. If private access is needed, use an
  already configured named secret or an authorized integration; do not ask
  for a credential in chat.
- For a new project, create source under `/work` with `sandbox_exec`. When
  modifying a cloned repository, keep the changes in the box and export a
  patch or source archive so the person can apply them to their checkout.
  Do not claim that the person's local files changed.
- For a ChatGPT a

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.