Internal automation

LocalCloud automation for internal projects

The Public Preview License permits organization and team CI for non-production development and testing. Keep Docker, localhost endpoints, no Google Cloud credentials, and a visible readiness check.

Read docs Check compatibility SDK examples

Agent prompt CTAs

Configure internal CI

Have an agent add a permitted non-production LocalCloud CI workflow.

Read https://local.cloud/docs/licensing/ before changing this automation. Keep the workflow within the Public Preview License's non-production boundary. Propose the smallest change that starts LocalCloud, waits for readiness, exports emulator env vars, runs integration tests locally, and avoids real GCP secrets.

Troubleshoot routing

Diagnose why SDKs or Terraform are still reaching real GCP.

Troubleshoot my LocalCloud setup. Read https://local.cloud/ai/agents.md, check whether Docker and the localcloud container are healthy, verify emulator environment variables are set in this shell/test runner, and identify any SDK or Terraform configuration that could still call real Google Cloud.

Configure this repo

Have an agent wire an existing project to LocalCloud safely.

Set up this repository to use LocalCloud for local GCP development. First read https://local.cloud/ai/agents.md, then inspect this repo, identify the GCP services and SDK language, configure emulator environment variables, and run the narrowest integration test against localhost. Do not use real GCP credentials or production endpoints.

Fact

Agents must keep automation inside the Public Preview License boundary.

Fact

Automation jobs must print active emulator endpoints before tests.

Fact

Real GCP validation is a separate release gate.

Reviewable diff

Keep the first automation change small

Start container, wait for health, export env, run existing integration tests. Avoid unrelated retries, deployment logic, or credential setup in the first agentic CI change.

Failure mode

Fail closed on routing mistakes

If env vars are missing or LocalCloud is unhealthy, fail the job rather than silently using production defaults.

Copy-ready setup

Commands and prompts

Use these snippets as starting points, then keep the checks scoped to localhost until you intentionally validate against real Google Cloud.

Public preview automation instruction

Read the LocalCloud Public Preview License and keep this workflow non-production. Prepare the smallest automation change that starts LocalCloud, waits for http://localhost:24080/health, exports emulator env vars, runs existing integration tests, and does not add real GCP secrets.

Reusable health gate

for i in $(seq 1 60); do
  if curl -fsS http://localhost:24080/health; then exit 0; fi
  sleep 2
done
exit 1

Limitations

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.

Next routes

Keep the agent on the supported path

GitHub Actions workflow — Concrete YAML starting point.
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.