An agent environment has two halves: an execution boundary and a dependency boundary.
Glossary
Agent environment
The set of runtimes, tools, files, and network endpoints an AI coding agent can reach while it works on a task. It covers both where the agent executes code and what that code is allowed to call.
Code sandboxes such as E2B, Modal, or Docker sandboxes provide the execution boundary.
LocalCloud provides a Google Cloud dependency boundary so agent-written cloud calls resolve to localhost.
What Agent environment means here
The set of runtimes, tools, files, and network endpoints an AI coding agent can reach while it works on a task. It covers both where the agent executes code and what that code is allowed to call.
- An agent environment has two halves: an execution boundary and a dependency boundary.
- Code sandboxes such as E2B, Modal, or Docker sandboxes provide the execution boundary.
- LocalCloud provides a Google Cloud dependency boundary so agent-written cloud calls resolve to localhost.
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
- Local cloud for AI agents — How the two boundaries fit together.
- 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.