The voice path is the part worth reading twice. RuntimeWire's recovered code pairs a continuous voice provider with automatic message submission and window-level keyboard controls [10], alongside a shared transcription hook that exposes a final-transcript callback and caps a continuous session at 30 minutes [12]. The microphone toggle and listening indicator sit in a sidebar entry present only in development builds [11]. Chain those and the sequence has no human step in it: audio streams, the recognizer decides the utterance ended, the callback hands over the text, the session submits it.
The break point is the recognizer's finality decision. Finalize early and a half-sentence gets sent. In an ordinary chat that costs one bad turn, but the addressee described here is a dedicated agent responsible for managing work across other agent conversations [1], so the cost depends entirely on what that agent may read and write, and that is the one thing the teardown could not reach [6].
It could not reach it because a binary is missing. The specialized agent depends on an internal executable ending in concierge_main.par, which was not bundled with the inspected public release [5], leaving its tools, permissions and ability to perform the proposed tasks untested [6]. RuntimeWire says its work was read-only extraction, byte comparison, JavaScript control-flow inspection and protocol-schema decoding, that it did not call authenticated agent endpoints or internal Google services, and that it claims no successful Concierge backend run [15]; it describes the finding as partially reproduced [16]. On its own account, the welcome-screen prompts describe Google's intended workflows rather than completed ones [4], and the evidence establishes that Google distributed a client-side prototype inside a public download, not that ordinary Antigravity accounts can reach it [9].
The rest of the bundle reads like an internal build with the internals shaved off. The public-build feature provider omits implementations for Best of N, thought steering and ABFS providers [13], and a Labs sharing description marked internal-only requires an x20 export destination [14]. Electron bundles are a poor place to keep secrets.
One pair of numbers in the reporting record does not line up. The uploaded ASAR for package version 2.12.2 is listed at 4,526,397 bytes [17], while the highest evidence offset cited inside main.js ends at 8,578,737 [18], about 1.9 times the archive size [19]. Both can be true of different artifacts, since offsets into an extracted main.js are not offsets into a packed file, but the record as published does not say which was measured, so the recovered lines cannot be tied back to the hash.
RuntimeWire reads Concierge as Google building a supervisory layer above coding agents, driven by conversation history and automatically submitted voice commands [22]. For that reading to transfer, the client would have to show that concierge_main.par runs, that it gets read access to conversation history across sessions, and that it carries write authority over work in other sessions. It shows none of the three. Google had not responded to RuntimeWire's request for comment by publication [20].
