QUESTIONS

A few things
worth knowing.

Clear answers about preparation, compatibility, source ownership and the optional next chapter.

Do I need multiple sandboxes?

No. One project and one fixed sandbox are enough. Basecamp prepares the environment before your task; switching or managing multiple destinations is optional.

Does Basecamp install tools inside my task sandbox?

The prepare-first path materializes declared resources upstream, then delivers them for activation. A setup-only integration that still installs dependencies in the target is a different route and must be identified as such.

What happens to my source code?

It stays separate. Source files, native manifests, locks and project inputs are not absorbed into a reusable environment cache.

Is every listed language or sandbox supported?

No. The landscape illustrates the environment model and provider surfaces. The published Rust / Docker fixture proves its recorded configuration. Other combinations need their own adapter and validation.

Can my application still use the network?

Yes, under your policy. Avoiding dependency-registry downloads is not the same as prohibiting business APIs, databases or other legitimate network access.

Does the website launch a sandbox?

No. The product walkthrough and optional Next workbench are local illustrations. The recording is a separate historical execution with reproducible files.

Does Basecamp replace Cargo, npm or my build system?

No. Keep native project tools and lockfiles. Basecamp prepares their environment; the sandbox executes your commands and your application or agent produces the result.