Skip to main content
The Locus Sandbox Router is a Recipe that gives your agent a cloud sandbox for running code without choosing a supplier. Describe the work and what matters most, and Locus picks the provider.

How it works

Locus picks E2B, Tensorlake, Boat, or Modal, creates the sandbox, and explains the choice. You pay for runtime in prepaid windows. Creating a sandbox charges its first window, and extending or resuming it charges another. To delete a sandbox, release it under Resources.
Try Locus Sandbox Router

Choose a workload and a priority

Tell your agent what kind of work the sandbox is for and what to optimize:
  • Workload: code execution, coding agent, data processing, or background service.
  • Priority: balanced, cost, latency, or reliability.

Good to know

  • Included in each window: commands, files, background jobs, and preview URLs.
  • No refunds for unused time. Unused time in a window is not refunded.
  • Persistent sandboxes pause. A persistent sandbox, the default for coding agents, pauses when its window ends and keeps its files, packages, and git state for seven days at no charge.
  • Other sandboxes are deleted when their window ends.
  • Find them under Resources. Your sandboxes appear under Resources, where you can release one to delete it.

Next steps

Recipes

See the other Recipes.

Resources

Renew or release your sandboxes.