Skip to main content
This example shows how to run multiple CoreWeave sandboxes in parallel using a session. A session applies shared defaults across the sandboxes and cleans them up automatically when the block exits. Use this pattern to coordinate work across several sandboxes without managing each lifecycle individually.

Choose authentication

These examples run on serverless capacity unless a section specifies CKS. Choose the credential for the account that owns your sandboxes. See Choose and get credentials to obtain a key or token. Run the installation commands in an active Python virtual environment. Save the Python code from your credential tab as sandbox_auth.py beside the Python scripts you run from this page. It stores the authentication choice, not your credential. The examples import AUTH from that file and pass it explicitly to each new sandbox or session.
Use your Forge API key through the SDK’s W&B authentication strategy:
sandbox_auth.py
For CKS placement, choose the CoreWeave token, enable a runner, and set placement_mode="cks" on sandbox creation or in SandboxDefaults. Creating a session with auth=AUTH also authenticates the sandboxes it owns. Keep the same credential when reconnecting, listing, or cleaning up sandboxes.

Run sandboxes in a session

Sessions manage multiple sandboxes with shared defaults and automatic cleanup:
For sandbox pools, adoption patterns, and lifecycle management, see the Sessions guide.
Last modified on October 23, 2026