The running Firenook suite: how the project was found, hub locator, hub status, the emulators listing (host and port per service) and the CLI version; with no project, the suites whose locators answer.

Export the running Firestore, Auth and Storage data to a directory outside the project (firenook emulators:export).

Read one Firestore document by path (collection/document[/subcollection/document]); returns its fields as plain JSON or exists:false.

Run a structured query over one collection, or with collectionGroup over every collection with that id (Firestore runQuery): optional where filters, ordering and limit; returns matching documents as plain JSON.

Count the documents of a collection, or with collectionGroup of every collection with that id, that match optional where filters (a COUNT aggregation; no documents are read back).

Write a Firestore document from plain JSON: replaces it, or with merge:true updates only the given top-level fields.

Delete a document (recursive:true also its subcollections) or a collection (its documents; recursive:true everything beneath) through the emulator delete route.

List collection ids at the database root or under a document (listCollectionIds).

List Auth emulator accounts (accounts:batchGet) with uid, email, phone, display name, claims and provider data.

Look up one Auth account by uid, email or phone number (accounts:lookup).

Create an Auth emulator account with a synthetic email/password, phone number or display name (never real credentials).

Delete one Auth emulator account by uid (accounts:delete).

The pending out-of-band codes (email verification, password reset, sign-in links) the Auth emulator holds instead of sending email.

The pending phone verification codes the Auth emulator holds instead of sending SMS.

Mint a Firebase ID token (valid one hour) and refresh token for an existing Auth emulator user, so an agent can call a function or the REST API as that user; claims replace the custom claims for this token only.

Set an Auth emulator user's custom claims: replace them (as the Admin SDK's setCustomUserClaims does) or with mode merge change only the given keys (a null value removes that key).

Remove the named custom claim keys from an Auth emulator user, keeping its other claims.

Disable an Auth emulator account: its sign-ins and token refreshes fail until it is enabled again.

Enable a disabled Auth emulator account again.

Revoke an Auth emulator user's refresh tokens (validSince moves to now), so its existing sessions must sign in again.

List the Auth emulator's tenants (multi-tenancy) with their user counts and sign-in settings.

List Storage objects and folder prefixes under a prefix (one level, like listAll).

The metadata of one Storage object (content type, size, timestamps, custom metadata, download tokens) or exists:false.

Read a Storage object's content: text inline (text, JSON, XML, SVG...), anything else as base64; at most maxBytes are returned and truncated says whether there is more.

Upload (create or replace) a Storage object from text or base64 bytes with a content type and custom metadata, as the Admin SDK would (rules skipped; finalize triggers run).

DESTRUCTIVE: delete one Storage object, or with a path ending in / every object under that folder.

Copy a Storage object (or a folder, a path ending in /) to a new path, in the same or another bucket; refuses to overwrite unless overwrite is true.

Move (rename) a Storage object or a folder (a path ending in /), in the same or another bucket; refuses to overwrite unless overwrite is true.

The functions loaded by the running suite: name, region, generation, trigger kind, event type or schedule, and the HTTPS URL of request/callable functions.

Invoke a loaded function: an HTTPS/callable request with data, or with eventData a background event (Firestore before/after, Storage object, Pub/Sub message, Auth user, schedule, Eventarc custom event, task queue payload) shaped as the official functions shell sends it.

Recent function calls, newest first: trigger kind and cause, outcome (succeeded, failed, timedOut, crashed...), HTTP status, duration and the first line of the error.

One function call in full: its cause, request (method, path, headers, body), response (status, body), event payload, the error with its stack trace, the call's console output and timings.

Run a recorded function call again with the same request or event (after a fix, say) and report the new call: outcome, status, response body and its id for functions_get_call.

Search the suite's log (every emulator and every function's console output) by service, level, function, call, text and time; returns the newest matching lines, oldest first.

Count the log lines matching a filter by level, service, function, codebase, extension instance and kind, to see where errors and warnings come from before reading them.

The Security Rules in force: the Firestore rules of a database and the Storage rules of a bucket (source, whether they are enforced, the file and its problems).

Ask the rules in force (or a draft) whether a request would be allowed: get, list, create, update or delete on a Firestore path or Storage object as a given user or unauthenticated; returns the verdict, the rule line that decided it and each evaluated expression's value. Nothing is written.

Recent requests the Security Rules denied (app clients only; admin and owner requests skip the rules), newest last; with explain, the rule lines that denied each one.

Publish a message to a Pub/Sub emulator topic: string data as given, other JSON as its text (base64-encoded on the wire), plus attributes.

The Pub/Sub emulator's topics with their published counts, subscriptions and the functions they trigger (schedule topics included).

Every Pub/Sub subscription (of every topic, and detached ones) with its delivery type, filter, dead-letter topic and backlog.

Peek at a subscription's backlog in delivery order without pulling, leasing or acking anything: each message's state, attempts, attributes and data.

Queue statistics of the Cloud Tasks emulator (queueStats).

The Cloud Tasks queues (with their pending and running counts) and the tasks waiting in them; with queue, only that queue's tasks, optionally in one state.

Dispatch one waiting Cloud Tasks task now instead of at its schedule time (it is sent on the next tick).

The scheduled functions (onSchedule, pubsub.schedule): expression, time zone, next runs, paused state and the latest runs with their delivery.

Run a scheduled function now: publish one tick to its schedule topic, as Cloud Scheduler would, and report the run.

Publish a custom CloudEvent to an Eventarc channel (default the project's Firebase channel), as getEventarc().channel().publish() does, and report which functions received it and how each call ended.

The Eventarc events the suite received, newest first (custom events, replays and the Firebase services' own), with how many functions matched, received or failed each.

One Eventarc event with its attributes, data and every function delivery (outcome, duration, invocation id for functions_get_call).

Deliver a received Eventarc event again to the functions it matches (a new event, origin replay) and report the new deliveries.

The Firebase Extensions instances the suite runs: reference and version, state (running, loading, failed) with the load error, and their function count.

Reload one Extensions instance (re-read its .env parameters and source, restart its functions) and report its state and functions afterwards.

DESTRUCTIVE: delete all data of the chosen services (every Firestore document, every Auth user and tenant, every Storage object, every Pub/Sub topic, subscription, schema and message, every Cloud Tasks task and its history). Clearing more than one service needs confirmProject set to the project id.