Is Basecamp a sandbox?
No. The sandbox provides the isolated computer. Basecamp prepares the environment that runs inside it: runtime, packages, tools, SDKs, and other locked inputs.
Where does Basecamp run?
Wherever the sandbox lifecycle gives you a setup step: inside a managed sandbox before the agent starts, while building a reusable image or snapshot, or on a connected machine before importing an offline bundle.
Does Basecamp replace Cargo, pnpm, uv, or Go?
No. Native ecosystem files and commands stay authoritative. Basecamp prepares the environment around them and then gets out of the way.
Does Basecamp build or run my application?
No. Use basecamp sync to prepare the environment, then invoke the normal project command such as cargo build, pnpm test, or uv run.
Which languages are supported?
Rust / Cargo is the complete v0.5 implementation. Node, Python, Go, JVM, and other adapters are part of the polyglot environment model and are being added without changing the core lifecycle.
What does “AI-native environment” mean?
AI workloads often need browsers, MCP servers, native/GPU SDKs, model assets, tokenizers, datasets, and utility binaries in addition to language packages. Basecamp treats these as environment inputs instead of setup work the agent has to rediscover every run.
Can it work without network access?
Yes. Prepare and materialize the environment while connected, export it with basecamp bundle pack, then restore it inside an isolated sandbox with bundle unpack.
What should I commit?
Commit basecamp.lock next to your native package lockfiles. Keep machine-local .basecamp/ activation state out of the repository.