Runtime details
- Endpoints
- gRPC :24082
- Minimum tier
- community
- Persistence
- volatile
- Documented workflows
- 3
3 documented workflows
Run Pub/Sub workflows locally
Topic, subscription, publish, pull, and acknowledgement workflows.
Documented workflows
- topics.create/get/list/delete
- subscriptions.create/get/list/delete
- publish/pull/ack/modifyAckDeadline
Service boundaries
- Schemas, snapshots, seek, dead-letter policy, filters, and other advanced subscription fields are not implemented on the configured endpoint.
- gcloud and console paths remain partial for advanced Pub/Sub workflows.
- schemas, snapshots, seek, dead-letter policy: Not supported locally. The configured Pub/Sub gRPC endpoint fails unsupported schemas, snapshots, seek, and advanced subscription fields explicitly with UNIMPLEMENTED.
- Topics, subscriptions, and messages do not survive emulator/container restart
- Reseed or recreate state after restart.
FAQ
Common questions
How do I run Pub/Sub locally?
Install the LocalCloud host CLI, start the runtime, and load the generated environment values into your application process. Pub/Sub is then reachable at the endpoints the CLI reports, and standard Google Cloud clients resolve to localhost instead of googleapis.com.
Which environment variable points the SDK at the local Pub/Sub?
LocalCloud exports PUBSUB_EMULATOR_HOST=localhost:24082. Read the value from the generated environment rather than assuming a fixed port, because occupied ports are remapped at startup.
What Pub/Sub workflows are documented locally?
3 Pub/Sub workflows are documented with operation-level status: topics.create/get/list/delete, subscriptions.create/get/list/delete, publish/pull/ack/modifyAckDeadline. The compatibility matrix lists the status of every operation.
Does the local Pub/Sub behave exactly like Google Cloud?
No. LocalCloud implements documented local workflows with published boundaries, and compatibility is narrower than managed Google Cloud. Validate behavior against real Pub/Sub before production deployment.
Can an AI coding agent use the local Pub/Sub?
Yes. Because no cloud credentials or billing project are required by default, agent-written Pub/Sub code can run against localhost without creating real cloud resources or charges.