Web console

Open the console for the selected runtime with the host CLI:

localcloud console

Trust the URL printed by the CLI because the gateway may be dynamically remapped from canonical port 24080. Manual-Docker users on canonical ports can open http://localhost:24080.

Dashboard and service status

The dashboard exposes runtime status, the selected project, request counts, and service health. Use /health, /health/{service}, /readiness, and /services for automation; the visual state is an operator aid rather than a production monitoring guarantee.

Data browser

The Data Browser is not read-only. Depending on the selected service and current compatibility it can perform bounded mutations, including:

• creating buckets and folders;
• uploading and deleting Cloud Storage objects;
• creating and deleting Pub/Sub topics;
• publishing local Pub/Sub messages; and
• using service-specific mutation forms exposed by the runtime.

Treat console actions like API calls: use synthetic data, keep the selected project visible, and do not expose a permissive gateway outside loopback.

Read and query views include service-specific datasets, schemas, objects, documents, secret metadata, messages, keys, logs, and metrics. Availability follows enabled services and their compatibility evidence; not every Google Cloud console operation exists locally.

SQL and service explorers

BigQuery and Spanner expose query and schema tooling for documented local workflows. BigQuery and Spanner dependency behavior remains release-sensitive until a source revision and assembled image are qualified together. Validate production SQL semantics separately.

The console also provides request logs and generated environment snippets. Generated values should be copied into the exact shell or process running local clients.

Usage and cost estimates

Any displayed cost value is indicative pricing only — not live Google Cloud rates. It is not a bill, realized saving, or purchasing forecast. Pricing inputs and UI estimates can become stale; confirm the review date shown in the runtime and use current, authorized billing data for decisions.

Security boundary

The console and many administrative paths are accessible even when IAM strict or gcp-live mode is enabled. Keep the runtime loopback-bound. Docker-socket access and transparent networking are separate opt-ins with broader host/network impact.