Skip to main content
Push a script into a disposable sandbox, run it once, and see its full result — no sandbox to create or clean up yourself. bonya job run handles all of that: by default it creates a sandbox just for this run and deletes it when the run ends. Every command below uses the deployment’s default template; if you haven’t installed the CLI or logged in yet, start with the Quickstart.
1

Write the script locally

2

Run it as a job

--script uploads and runs the file in one call; job run blocks until it finishes and prints the result. There’s no sandbox to create first — one is provisioned for this run and torn down automatically when it’s done.
The script’s own stdout appears first, then the run’s summary. SANDBOX is the disposable sandbox this run created — by the time this printed, it was already deleted.
3

Look up the run later

Every run gets an id you can hand to job get to see it again, including its full stored spec and timeline — useful if you didn’t capture the output the first time:
Nothing to clean up — the run’s own sandbox already tore itself down. Pass --keep to job run if you want the sandbox to survive the run instead.

​
Next steps

Jobs

Job schedules, existing-sandbox targeting, and the full spec.

Transfer files

The fs read/write/upload/download surface, for when you’re working against a sandbox you already have.