client.sandboxes gives you ephemeral, network-jailed code-execution environments (gVisor microVMs) with noxus-sdk pre-installed. Use them to run untrusted or one-off code — data processing, generating a file, running an SDK script against the platform.
Lifecycle
persistent=False sandboxes are cheap and cleaned up when idle; pass
persistent=True only if you need it to survive between calls. Sandbox fields:
id, status, created_at, last_activity, label.Prefer the context manager — it always tears down
Run commands
Read & write files
Recipe: run an SDK script inside the sandbox
The sandbox can call the Noxus API itself (it hasnoxus_sdk baked in). Inject a scoped key and backend URL as env vars, then run the script:
The sandbox network jails RFC1918 but NATs out, so the backend must be
reachable at a public URL from inside the sandbox for the SDK-in-sandbox
pattern to work.
Async twins exist throughout:
client.sandboxes.acreate / alist / aget /
adelete; sb.akill / sb.arefresh; sb.commands.arun; and
sb.files.awrite / aread / aread_bytes.