Cloud sandboxes for coding agents.

Give your agent a fast, reproducible, and persistent place to run code. RWX sandboxes share their config, their caching, and their CLI with your CI/CD pipelines, so your inner dev loop and outer dev loop run on the same platform.

Read the docsTalk to an engineer

Run your inner dev loop and
outer dev loop on the same rails.

Coding agents spend most of their time in a tight inner loop. Edit, run a targeted test, repeat. Once the change looks right, the commit and push to hand off to the outer loop: the full CI/CD pipeline. RWX gives the agent one platform for both.

Inner loop
  • Make a change
  • Run a targeted testrwx sandbox exec
  • Loop until the change succeeds
Outer loop
  • Verify the entire buildrwx run --wait
  • Loop until CI/CD passes
  • Commit and push
❯

The same primitives CI/CD runs on, available to your agent.

RWX sandboxes leverage the same runtime as our CI/CD platform. Same run definitions, the same content-based caching, and the same compute. Exposed as a persistent environment your agent can call into.

Your run definition is your sandbox.

Share a definition across your dev sandboxes and your build. No bespoke container images. No snapshots to curate. Edit one file, both loops update.

tasks:
  - key: code
    call: git/clone 2.0.7

  - key: sandbox
    use: code
    run: rwx-sandbox

Ready in seconds, not minutes.

Other platforms make you build bloated container images or curate snapshots out of band. RWX sandboxes always have your latest dev dependencies installed and snapshotted automatically. Each task produces a content-addressed filesystem layer and new sandboxes spin up with the layers that match your config.

clone2s
rubyCached
gemsCached
nodeCached
node-modulesCached
sandboxRunning

Persistent environments. Automatic sync.

Your sandbox stays warm between commands. Background processes and services continue to run. Your local changes sync up before each command and results sync back after so your agent always sees the latest state on both sides.

❯

Credentials your agent can't see.

The same secrets you use in CI/CD can be injected into the sandbox at runtime, scoped per task. Commands inside the sandbox see the real values; the agent's prompt never does.

❯_Read more about RWX Vaults

Agent context
STRIPE_SECRET_KEY••••••••••••••••
Sandbox runtime
STRIPE_SECRET_KEYsk_test_T2bx…q8AC

Start a sandbox in three steps.

Execute commands against the same environment you already use for your build.

❯_Read the getting started guide

Install RWX

Add the CLI and install the RWX skill.

❯ brew install rwx-research/rwx/rwx
❯ rwx skill install

Define your sandbox

Describe your development environment in .rwx/sandbox.yml.

❯ rwx sandbox init

Launch your sandbox

Run any command against your freshly provisioned environment.

❯ rwx sandbox exec -- echo "hello world"

Unblock your agents.

Start buildingTalk to an engineer