{
  "client": "antigravity-desktop",
  "version": "2.19.1",
  "platform": "darwin-arm64",
  "observedAt": "2026-10-05T04:34:55.036Z",
  "capability": "native_delivery",
  "result": "pass",
  "fixture": "antigravity-desktop-2.19.1-product",
  "launchMode": "ordinary-command-with-installed-hooks",
  "protocolContract": "antigravity-desktop-agentapi-v1",
  "idle": "offered",
  "busy": "queued_after_turn",
  "reply": "routed",
  "duplicate": "same_message_id",
  "fallback": "queued",
  "limitations": [
    "Observed on darwin-arm64 with Antigravity 2.19.1, the desktop app (Antigravity.app), model Gemini 3.8 Flash, in one conversation of a probe project opened in the app, through a private candidate built from this branch and installed into an isolated ACC data home that the app was launched with.",
    "No relay and no command for the agent to run: ACC found the app's language server as the hook's parent, read its endpoint from the server's command line at each bind and offer, and pushed through the server's own agentapi; the endpoint record carries the server's pid, start time and port, never the token.",
    "An idle conversation woke with no user input. A message accepted while the model streamed a long answer was presented after that answer completed, uninterrupted. The desktop UI shows each push as a collapsed ACC peer message entry.",
    "The agent's acc commands fail inside the app's sandbox and run once the model retries outside it; with the wrapper's grant already in ~/.gemini/config/config.json, that retry ran without an approval prompt.",
    "With the app quit, a message stayed queued as recipient_offline. After the app restarted - a new language server, token and port - the conversation's first user turn bound it again, and the next push woke it.",
    "The app runs no SessionStart for a conversation it reopens, so after a restart live delivery returns at the conversation's next turn, not before."
  ],
  "packageSha256": "c03096251a9efd251ecd42c6bf489e8783a9515c83d85242645a3a31fcdc0c42"
}