Computer use
Inspect an application in the sandbox's browser and share its desktop with an agent.
Desktop commands require a Session image with desktop support enabled for your
environment. Updating the CLI alone does not add desktop tools to an existing
sandbox. A Session without them reports desktop_not_installed.
Choose where the browser runs
| Command | Browser location | Use it for |
|---|---|---|
cube open 3000 --session feature/payments | Your computer | Previewing a forwarded app in your normal browser |
cube browser feature/payments http://localhost:3000 | The sandbox | Interacting with the app using remote Chromium |
cube desktop feature/payments | Viewer on your computer, desktop in the sandbox | Watching or controlling the remote desktop |
The remote browser shares the sandbox's files. localhost in its URL refers
to the sandbox, so it can reach the development server running there.
Open the remote browser
Start your application inside the sandbox, then run locally:
cube browser feature/payments http://localhost:3000Adria opens Chromium inside the sandbox and shows the desktop through a local viewer URL. To view the desktop without choosing a browser URL:
cube desktop feature/paymentsThese commands require an existing Session and can resume a paused one. They
return your terminal prompt while a local helper keeps the viewer connected.
Use --no-open to print the viewer URL without opening it automatically.
Observe and interact
Run these commands locally, with the Session explicitly selected:
cube computer screenshot feature/payments --output screen.png
cube computer click feature/payments --x 420 --y 280
cube computer type feature/payments 'Hello from Adria'
cube computer key feature/payments Return
cube computer scroll feature/payments --direction down --amount 3Screenshots are 1920 × 1080 PNGs saved to the requested path. Click coordinates
use screenshot pixels with the origin at the top left. type pastes text into
the focused application; key sends a key or chord such as CTRL+L. Scroll
amounts are wheel ticks.
Screenshot and input commands require a ready Session. Use its UUID outside a repository or when a branch name is ambiguous. Independent headless Playwright processes do not automatically appear in this shared desktop.
Share control with an agent
The viewer starts in watch mode. Select Take control to use the desktop yourself. While you hold control, Adria computer input commands from agents are blocked; screenshots remain available. Select Return control to let the agent send input again.
Close and reconnect
Closing the viewer leaves the remote desktop and browser running while the VM
runs. After a lost connection, rerun cube desktop <session> to reconnect.
Pausing preserves the browser profile on disk, but not tabs or process memory.
After resume, restart your app and open the browser again.