Everything Pub/Sub gives you
- 01
Publisher, Subscriber, Schema APIs
Topics, subscriptions, Pull, StreamingPull, acks, snapshots, Seek and schema revisions over gRPC, with paging.
- 02
Five subscription kinds
Pull, push (wrapped or unwrapped, with an OIDC token), BigQuery, Cloud Storage and Bigtable; their rows and files are kept.
- 03
Schemas that validate
Avro and Protocol Buffers in JSON or binary; a publish no revision accepts gets INVALID_ARGUMENT.
- 04
Filters and ordering
Attribute filters with hasPrefix, NOT, AND, OR; ordering keys wait while one of their messages is out.
- 05
Retries and dead letters
Nack or a passed deadline redelivers with the retry backoff; past max attempts the message moves to the dead-letter topic.
- 06
Exactly-once delivery
Expired ack ids fail with EXACTLY_ONCE_ACKID_FAILURE; StreamingPull confirms acks, as ack_with_response reads.
- 07
JavaScript and AI transforms
UDFs run in QuickJS with Pub/Sub's signature; AI inference transforms are answered by the AI models simulator.
- 08
Import topics
Cloud Storage, MSK, Confluent and Kinesis sources read Stuntman storage, Kafka and Kinesis; any source takes pubsub_ingest.
- 09
Snapshots and Seek
Seek to a snapshot or a time replays what is retained, with retain-acked and topic retention honoured.
The screens
Each number is a control or a reading on the real screen. Everything you can click there, your agent can do with a tool.
A topic, and each subscription's view of its messages

Every publish is validated; subscribers get the googclient_schema* attributes.
An import topic reading a Kafka topic as Amazon MSK, with its state.
A JavaScript UDF runs on every message before the schema check.
Messages with the same key are delivered in order, one out at a time.
Pending, outstanding, acked, expired or dead after 5 attempts, per subscription.
- Schema
Every publish is validated; subscribers get the googclient_schema* attributes.
- Ingestion
An import topic reading a Kafka topic as Amazon MSK, with its state.
- Transform
A JavaScript UDF runs on every message before the schema check.
- Ordering key
Messages with the same key are delivered in order, one out at a time.
- State per subscription
Pending, outstanding, acked, expired or dead after 5 attempts, per subscription.
Provoke on publish, and the subscriptions

Publish answers UNAVAILABLE; the client libraries retry it.
Exactly-once acks fail with TRANSIENT_FAILURE_UNORDERED_ACK_ID until times runs out.
After 5 delivery attempts the message moves to shipments-dlq.
Messages whose attributes do not match never reach this subscription.
Subscriptions that write rows and files Stuntman keeps for you to read.
- Unavailable
Publish answers UNAVAILABLE; the client libraries retry it.
- Ack transient
Exactly-once acks fail with TRANSIENT_FAILURE_UNORDERED_ACK_ID until times runs out.
- Dead-letter topic
After 5 delivery attempts the message moves to shipments-dlq.
- Filter
Messages whose attributes do not match never reach this subscription.
- BigQuery, Storage, Bigtable
Subscriptions that write rows and files Stuntman keeps for you to read.
Break it on purpose
The failures you need to test, exactly when you ask: from the screen or by a tool call, each one shown on the timeline with who caused it.
UnavailablePublish answers UNAVAILABLE; clients retry
set_pubsub {provoke: unavailable, times: 2}Deadline exceededPublish answers DEADLINE_EXCEEDED
set_pubsub {provoke: deadline_exceeded}Resource exhaustedPublish answers RESOURCE_EXHAUSTED
set_pubsub {provoke: resource_exhausted}Topic not foundPublish answers NOT_FOUND, for one topic or all
set_pubsub {provoke: not_found, topic}Slow publishEach publish waits delay_ms (3 s by default)
set_pubsub {provoke: slow_publish}Duplicate deliveryA message comes again after its first ack
set_pubsub {provoke: duplicate}Transient ack failureExactly-once acks and modacks fail and are retried
set_pubsub {provoke: ack_transient}Push endpoint failsNon-2xx answers retry with backoff, then dead-letter
create_pubsub_subscription {push_endpoint}Row that does not fitBigQuery row refused, retried, then dead-lettered
set_pubsub_bigquery_tableAI transform fails429 or 5xx from the model fails the publish
force_ai_failureSubscription expiresAn idle subscription past its ttl is deleted
create_pubsub_subscription {expiration_ttl} + advance_clock
Why not the real sandbox
Cloud behaviour, locally
Schemas, snapshots, dead letters, filters, exactly-once and push auth behave as in the cloud, not only the basics.
See every subscription's state
One message shows acked here, outstanding there, dead in a third subscription, with delivery attempts.
Sinks without a cloud
BigQuery rows, Cloud Storage files and Bigtable rows are kept locally, so the test reads what would land.
Failures the clients retry
UNAVAILABLE, transient ack failures and duplicates on cue test the retry paths before production does.
Your AI agent drives it
Claude Code, Codex or any MCP client connects to /mcp (or calls /api over plain HTTP), sets the stand-in up, breaks it on cue and reads what your app did.
Make sure our shipment publisher survives two UNAVAILABLE errors in a row.
MCP tools
list_pubsub_topicsTopics, subscriptions, counts per state, snapshots, schemaslist_pubsub_messagesMessages with their state in each subscriptionpubsub_publishPublish as another service wouldcreate_pubsub_subscriptionPull, push, BigQuery, Cloud Storage or Bigtableset_pubsub_schemaCreate a schema or a revision; attach it to a topicset_pubsub_topicIngestion source and JavaScript UDF of a topicpubsub_ingestFeed records into an import topicwait_for_pubsub_messageWait for the app to publish a matching messagelist_pubsub_bigquery_rowsRows BigQuery subscriptions wroteset_pubsubDefault project and a provocation on Publish
The same over HTTP
- GET
/api/pubsub/topics - GET
/api/pubsub/messages - POST
/api/pubsub/topics/{topic}/publish - PUT
/api/pubsub/subscriptions/{subscription} - GET
/api/pubsub/topics/{topic}/wait - PUT
/api/pubsub/config
- Plaintext gRPC without auth, as the official emulator; one port serves every environment.
- Kinesis import topics read Stuntman's Kinesis; Event Hubs ones only get what pubsub_ingest feeds.