Skip to main content
On Gravix Layer, one sandbox ≈ one job. Create as many as you need, track each runtime_id, and kill when finished. That is the Gravix equivalent of running many Claude sessions side by side.

Prerequisites

All examples use the platform template claude.

Fan out three jobs

Each task gets its own sandbox. Results print as they finish.
To open an interactive shell on a sandbox you are not killing immediately, omit runtime kill / sandbox.kill() and run:

Pause and resume a long session

Useful when a job should keep its /workspace (and Claude --resume state) overnight without burning idle compute.

Cron: nightly briefing

Drop this next to a .env that exports the variables from Prerequisites. Cron creates a fresh sandbox each run.
For PR review in GitHub Actions, clone the PR head with sandbox.git (see Edit a repository) and run claude -p "Review this PR…".

Ops checklist

  • Cap concurrent sandboxes (service quotas)
  • Tag with metadata (task, pr_number, owner)
  • Always kill or set timeout
  • Log runtime_id, Claude session_id, and exit_code

Next