A sandbox with real cloud credentials can still create real cloud resources and real charges.
Glossary
Agent sandbox vs cloud emulator
Two different controls that are often confused. An agent sandbox isolates where generated code runs. A cloud emulator replaces what that code talks to. Using one does not give you the other.
An emulator without a sandbox still lets generated shell commands touch the host.
Most agent setups that handle cloud code want both controls in place.
What Agent sandbox vs cloud emulator means here
Two different controls that are often confused. An agent sandbox isolates where generated code runs. A cloud emulator replaces what that code talks to. Using one does not give you the other.
- A sandbox with real cloud credentials can still create real cloud resources and real charges.
- An emulator without a sandbox still lets generated shell commands touch the host.
- Most agent setups that handle cloud code want both controls in place.
How to use the term safely
In LocalCloud content, this term should not imply production replacement, legal permission, hidden credentials, or complete cloud parity. It describes a bounded local-development workflow that still needs license review and release validation against real Google Cloud.
Use the sandbox deliberately
- Permitted workflows use local endpoint values and should stop rather than fall back to real Google Cloud or real credentials. The Public Preview License permits individuals and organizations, including for-profit companies, to use LocalCloud for non-production internal development, testing, CI, evaluation, and pilots.
- LocalCloud emulates bounded local development workflows. Validate application behavior against real Google Cloud before production deployment.
- Before production deployment, unset LocalCloud emulator environment variables and validate behavior against real Google Cloud.
Keep the agent on the supported path
- LocalCloud vs hosted agent sandboxes — Where each boundary applies.
- Agent routes — Agent sandbox entry points.
- Compatibility — Service support boundaries.
- Compatibility matrix — Check current support boundaries before relying on a local-only test.
- Service catalog — Review every LocalCloud service, endpoint, and limitation.
- SDK examples — Use standard Google Cloud SDKs pointed at localhost.
- Seed data — Load deterministic fixtures for repeatable agent and CI runs.