Google Antigravity is testing Concierge, a voice activated coding assistant and bot wrangler

RUNTIMEWIRE INVESTIGATION — Scoop

Original reporting by RuntimeWire, based on reverse engineering.

Why it matters

Concierge points to Google building a supervisory layer above coding agents, using conversation history and automatically submitted voice commands to manage work across sessions.

Reporting record

Google's Antigravity 2.12.2 desktop software contains a development-only prototype called Concierge that would let developers give spoken instructions to a dedicated agent responsible for managing work across other agent conversations. RuntimeWire recovered the interface and its microphone controls from the version Google released on September 3rd, 2026.

The welcome screen proposes four jobs for Concierge: reviewing conversations from the previous three days that need the user's attention, addressing code changes described internally as "CLs," generating personalized rules from conversation history, and recommending skills and plugins based on that history.

Those starter prompts describe Google's intended workflows. They do not establish that Concierge successfully completed any of them. The specialized agent relies on an internal executable ending in concierge_main.par, which was not bundled with the inspected public release. Without that component, the prototype's tools, permissions and ability to carry out the proposed tasks could not be tested.

Google's code also makes the interface difficult to mistake for a customer launch. The sidebar labels it "Concierge (Dev only)," and the feature is disabled by default. Enabling the entry requires both an enable-concierge-agent override and a development-mode setting. The evidence establishes that Google distributed the client-side prototype inside a public download, not that ordinary Antigravity accounts can access it.

A spoken command goes straight to the agent

Concierge's voice path differs from Antigravity's documented voice dictation. The existing CLI feature transcribes speech into the prompt box and waits for the user to edit or submit it. Concierge is designed to send each finalized, nonempty transcript automatically to its dedicated agent conversation.

After the user activates the microphone, the client opens a continuous transcription stream. Finalized text is passed to sendUserCascadeMessage using a WHEN_IDLE delivery strategy, meaning the instruction is queued for delivery when the Concierge conversation can accept it. The interface plays a confirmation chime, displays a notification and briefly changes the sidebar status to "Sent!"

The dedicated conversation is stored under the identifier concierge_cascade_id. If no Concierge conversation exists when a transcript is finalized, the client first creates one and then submits the spoken turn.

The microphone starts switched off. Users can toggle it through the interface or with Ctrl+Shift+M. Pressing and holding that shortcut for longer than one second, starting while the microphone is off, creates a push-to-talk interaction that stops recording when the keys are released. The continuous session automatically ends after 30 minutes.

One tooltip calls the feature an "always-on listener," but the implementation does not show the microphone activating by itself. The user must first turn it on, and the ordinary voice-recording control becomes unavailable while Concierge is listening. The inspected client code also does not establish spoken responses or a full speech-to-speech assistant. It shows speech being converted into automatically submitted text instructions.

A supervisor for Google's coding agents

The prototype extends the direction Google has already set for Antigravity. Google publicly supports multiple parallel agent conversations, while Custom Agents give developers specialized instructions and restricted sets of tools, skills and permissions. Its Boost and Teamwork systems distribute larger tasks among multiple agents.

Concierge occupies a different position in that structure. Its proposed job is to watch the user's existing conversations, identify unfinished work and route attention back to the relevant sessions. The prompt about fixing CLs goes further, suggesting the agent could act within the conversations associated with specific changelists. The interface does not identify a code-hosting service or demonstrate working support for pull requests.

The other two prompts make conversation history an input for configuring future agents. One asks Concierge to derive a personalized ruleset from prior interactions. Another asks it to recommend skills and plugins. If implemented, that would turn accumulated chat history into an operating profile for subsequent coding sessions rather than leaving each conversation as an isolated record.

That design raises concrete product questions for any external release. A useful supervisory agent would need enough access to inspect conversations, recognize pending decisions, connect code changes to the correct sessions and understand which actions require user approval. The recovered interface does not establish the scope of that access or which of the four workflows has a functioning backend.

Added sometime after Antigravity 2.5.0

The recovered application package declares version 2.12.2. RuntimeWire compared it with Google's official Linux archive for the same release and found the application packages byte-identical. The embedded main.js also matched the copy recovered from the Windows language server, tying the interface to Google's distributed September 3rd build rather than an independently modified client.

Google's official Antigravity 2.5.0 release, dated July 31st, provided the baseline. Its recovered interface bundle contained no occurrences of either Concierge or concierge. Version 2.12.2 contained 24 capitalized occurrences and 23 lowercase occurrences, along with the development gate, internal executable reference and microphone controls.

The comparison places the addition between July 31st and September 3rd. It cannot establish which intervening build introduced the code, whether Google still considers the experiment active, or whether Google intends to expose it to customers.

The timing is notable because Google's public September 3rd changelog describes Antigravity 2.12.2 as an enterprise model-access update. It lists Gemini 3.8 Flash access through Application Default Credentials, with no mention of Concierge. Public release notes are not an inventory of every internal component bundled into desktop software, and the explicit development gate shows this interface was not presented as part of the release.

The strongest finding remains narrower: Google built a client-side interface for a voice-controlled agent that would review other Antigravity conversations, address code changes and learn from a developer's history. Google then shipped that interface inside Antigravity 2.12.2 with the switch turned off and the agent executable left inside its own environment.