autosana CLI, looks at the screen, taps and types through the app, and ends it when it’s done. You can watch every sandbox live in the dashboard and replay it afterwards.
Sandboxes are turned on per company. If you don’t see Sandboxes in the sidebar, contact us to turn them on.
Start one with your coding agent
Open Sandboxes in the sidebar and click Copy prompt, then paste it into Claude Code, Codex, Cursor or any agent that can run terminal commands. The prompt asks the agent to install the CLI, log in, build your app for a simulator or emulator, and start a sandbox with that build. The agent learns the rest fromautosana sandbox --help.
Start one yourself
Install the CLI and log in:.apk, or an iOS Simulator .app or its .zip.
--bundle-id or --app-id. The sandbox installs the app’s active build, or the one you pass with --app-build-id. On iOS it needs a simulator build.
start prints a link to watch the sandbox and shows the app’s first screen. Every command after that works on this sandbox, so none of them need its id.
Run
autosana sandbox --help for every command and option, including picking a device with --device and --os.
How long a sandbox lasts
A sandbox stays up while you use it. It ends 30 minutes after the last command, or when you runautosana sandbox end. Use autosana sandbox extend or Extend on the sandbox’s page to keep it longer. A sandbox lasts at most 12 hours.
Watch and replay
Sandboxes lists your workspace’s live sandboxes first, with how long each has left, followed by the ones that ended recently. Click one to open its page:- While it’s live, the page follows the agent’s commands as they happen.
- After it ends, the page replays every step with its screenshot.
start command also prints a direct link to the sandbox’s page.