Project inputs stay small
The CLI fingerprints environment-relevant project inputs locally. The normal Rust resolver path works from their SHA-256 identities rather than treating your repository as a remote build workspace.
Sources are explicit and verified
Direct binary sources are locked by SHA-256. Package layers are tied to the native ecosystem lock digest, and Basecamp validates input identities before reproducing an existing environment lock.
Activation is project-scoped
Shared immutable layers live in the Basecamp store while generated activation state stays in the project. For Cargo, Basecamp uses project-scoped source configuration so unrelated host settings do not silently change the synchronized environment.
The sandbox still owns isolation
Basecamp prepares the runtime and resources. The sandbox provider remains responsible for process isolation, filesystem boundaries, network policy, resource limits, and session lifecycle.
Offline is explicit
Bundles carry the exact environment lock and already materialized layers into an environment where network access is intentionally unavailable.