agents-can-communicate 0.8.5 → 0.9.1

package/docs/TROUBLESHOOTING.md

@@ -117,8 +117,7 @@ handoff. ACC does not restart an exited client.
 supported platform, current probe and exact session binding. Under `actionable`,
 a `note` stays queued with `delivery_disabled`.
 
-For Codex, use your ordinary launch command with 0.152.1 or newer on Apple Silicon
-macOS. Its LocalDaemon infrastructure and trusted hooks must establish
+For Codex, use your ordinary launch command with 0.152.1 or newer. Its LocalDaemon infrastructure and trusted hooks must establish
 the receiver's exact thread and workspace. Embedded sessions, an absent socket,
 ambiguous recipients or failed identity checks retain durable inbox access.
 `acc doctor` reports readiness, consent and the current workspace's live channel separately.
@@ -144,6 +143,11 @@ user a notice once, a sender sees the cause beside `no live transport`, and doct
 the session line. Open a new Codex chat while the service runs; start it with
 `codex app-server daemon start` if Codex does not.
 
+The Codex app (inside ChatGPT.app) runs every chat this way: each window has its own app server
+and never uses the shared one (openai/codex#41014, read on 26.928). Its chats join ACC through
+the same hooks and get messages at their next turn; a chat started in a terminal is the one a
+peer can reach live.
+
 Some launch options make Codex run a chat embedded even while the service runs: `-c`/`--config`,
 `--enable`, `--disable`, `--search`, `-p`/`--profile`, `--oss`, `--strict-config`,
 `--dangerously-bypass-hook-trust` and `--no-daemon`, and also the `CODEX_EXEC_SERVER_URL`
@@ -178,8 +182,7 @@ or a connected MCP server does not by itself establish automatic delivery. `life
 manual` can also mean the current version has no certified session-end hook; it does not
 prove that no hooks ran.
 
-For Claude Code, use version 2.1.282 or newer on Apple Silicon macOS, and start it with
-your ordinary command. Each Claude Code session opens its own inbox socket. ACC reads the
+For Claude Code, use version 2.1.282 or newer, and start it with your ordinary command. Each Claude Code session opens its own inbox socket. ACC reads the
 socket path from `CLAUDE_CODE_MESSAGING_SOCKET` in the hook environment. ACC then checks that
 path against Claude Code's session registry `<config>/sessions/<pid>.json`, where
 `<config>` is `CLAUDE_CONFIG_DIR` or `~/.claude`. The pid and the socket must match for the
@@ -189,8 +192,8 @@ session again, so the next ordinary prompt retries a failed binding.
 - Claude Code 2.1.224 and later open the inbox, but ACC's captured minimum is 2.1.282. An
   older version reports `below_minimum_version` and keeps next-turn delivery.
 - On native Windows, Claude Code serves its inbox on a named pipe that requires an auth
-  line. ACC has no capture of that inbox, so Windows keeps next-turn delivery.
-- Linux is uncaptured for live delivery. A Linux session keeps next-turn delivery.
+  line. ACC sends the key Claude Code publishes for other sessions of the same user; see
+  [On Windows](#on-windows).
 - A wake that reached the session can still wait for your approval. See
   [the next section](#a-claude-code-session-holds-or-drops-acc-wakes).
 
@@ -249,6 +252,19 @@ next-turn hook shows the body. The message arrives with the session's next turn,
 `acc inbox` shows it at any time. The sender's `acc message` output still reports
 `woke <participant> via claude-inbox`, because the wake reached the inbox.
 
+## A Codex session will not tell peers project details
+
+With `approvals_reviewer = "auto_review"`, Codex's reviewer judges every command a session
+runs outside its sandbox. It refused an ACC reply that named a branch, a commit and changed
+paths as disclosure to an external party. After that, the session answered peers that it
+could not share project details.
+
+ACC's rules file lets the participant commands skip that review on macOS and Linux; see
+[Codex command approval](CONFIGURATION.md#codex-command-approval). Run `acc doctor`: when the
+rule is missing, it asks for `acc install --adapter codex`. If a session started before the
+install still asks, start a new one. On Windows there is no rule; approve the command, or turn
+off auto-review for the session.
+
 ## Codex plugin is listed but inactive
 
 Open `/plugins` in Codex and check ACC is enabled. Open `/hooks`, review each ACC hook,
@@ -340,8 +356,15 @@ Live delivery needs four things, and `acc doctor` shows each:
 - the session attached to ACC at all (see the section above);
 - the agent started the relay. While none is running, ACC's context asks up to three times
   in that conversation. A declined prompt and an ignored ask look the same, so the line can
-  return after a decline; after the third ask it stays quiet. Run
-  `sh "~/.gemini/config/acc/acc-relay.sh" start` to start it directly.
+  return after a decline; after the third ask it stays quiet. ACC's install allows that
+  command, so the agent starts it without an approval prompt; `acc doctor` names the rule when
+  it is missing. Run `sh "~/.gemini/config/acc/acc-relay.sh" start` to start it directly.
+
+In Antigravity 2.0, the desktop app, there is no relay: ACC delivers through the app's own
+language server, and `acc doctor` names such a session `Antigravity session`. A conversation is
+reachable from its first turn after the app starts. The app runs no session start for a
+conversation it reopens, so after a restart nothing reaches it live until someone sends it a
+prompt; the message waits in its inbox until then.
 
 `acc doctor` reports how many relays are running and, per session, whether a live transport is
 active. A relay ends with its client; nothing is left running after the TUI exits or after
@@ -365,6 +388,12 @@ first ACC command. `acc doctor` prints an `Antigravity CLI inbound:` line with w
 - **The file cannot be read.** ACC leaves an invalid `settings.json` as it is. Repair it, then
   run `acc install --adapter antigravity` again.
 
+Antigravity 2.0, the desktop app, runs the agent's commands in a sandbox where ACC's wrapper
+cannot run, and the model then asks to run it outside the sandbox. The app decides that from
+its own grants in `~/.gemini/config/config.json`, never from Antigravity CLI's settings. ACC's
+install adds its rule there once the app has run, and `acc doctor` prints its state on a line
+that names the desktop app. Restart the app after an install if it was open.
+
 ## Grok shows no injected message
 
 Grok discards UserPromptSubmit context. On the observed 1.0.24 client, run public
@@ -381,6 +410,41 @@ session becomes offline by presence rules rather than a clean end signal. The de
 status hides offline sessions; `acc status --all` intentionally retains attribution and
 checkout history.
 
+## On Windows
+
+- **A session attaches only on its first prompt.** ACC reads the process tree through
+  PowerShell, and the first start after boot can take several seconds. A hook that runs out of
+  time continues without ACC, and the next user prompt attaches the session.
+- **A hook reports `node` is not recognized.** Grok and Antigravity CLI hooks start `node` from
+  `PATH`. Add Node.js to the `PATH` the client sees, then restart the client.
+- **Claude Code hooks do nothing.** ACC wires Claude Code's hooks in exec form, which needs
+  Claude Code 2.1.139 or later. Update Claude Code and run `acc install` again.
+- **`acc install` refuses Antigravity CLI because of a space.** Antigravity CLI cannot run a
+  quoted hook path, so ACC writes the 8.3 short name of a path with a space. A volume with 8.3
+  names turned off has none; turn them on (`fsutil 8dot3name set C: 0`, as an administrator)
+  and run `acc install` again.
+- **A write through Claude Code's PowerShell tool was not guarded.** The guard reads POSIX shell
+  commands only. Claims are advisory by default, and a write through Claude Code's Write, Edit or
+  Bash tool is still checked.
+- **Codex is not woken on Windows.** Codex refuses to start its app-server daemon from an
+  elevated terminal ("start the Windows daemon from a non-elevated terminal"). Start Codex from a
+  terminal that is not running as administrator, and keep `CODEX_HOME` short: the daemon's socket
+  path has to fit 108 bytes, or Codex runs the chat on its own embedded server, which no peer can
+  reach.
+- **Hooks run out of time on a cloud machine.** A Windows flush waits for the whole disk to
+  write out its cache. On a GitHub `windows-latest` runner, whose system disk is remote, a 4 KB
+  flush took 10-33 ms at the median and up to 1.5 s, against 0.5 ms and at most 27 ms on its
+  local disk. A session start flushes 5 to 16 times, so a disk like that can run a hook out of
+  its five seconds; the session then attaches on a later prompt. Point `ACC_DATA_HOME` at a
+  directory on a local disk that only your account can read, for every client, and restart
+  them.
+- **A Claude Code session is not woken on Windows.** The wake authenticates with the key Claude
+  Code publishes beside its session record (`<config>\sessions\<pid>.<hash>.key`). Run
+  `acc doctor`: a session without that key, or whose pipe the machine no longer lists, waits for
+  its next turn. ACC trusts the key only in a configuration directory inside your user profile,
+  whose access list keeps it to your account. A session whose `CLAUDE_CONFIG_DIR` is elsewhere
+  reports `native_endpoint_unavailable` and also waits for its next turn.
+
 ## A write was blocked
 
 Exit code `5` names the overlapping claim and owner. Ask the owner or wait for release. If
@@ -408,6 +472,10 @@ confirming no needed coordination state remains.
 ACC removes only bytes that still match its install record. Anything edited by the user is
 reported and retained. Remove those leftovers manually if desired.
 
+An uninstall also skips a client that the current data home did not install, and names it:
+its wiring belongs to another ACC data home. Run `acc uninstall --adapter <client>` to remove
+it from this one.
+
 Runtime state is outside the repository by design. `ACC_DATA_HOME` can relocate it, but ACC
 refuses a path inside any workspace root. Relocate the whole data directory; a symlink for
 that directory is supported. Install rejects a symlink that moves only the internal

package/docs/UPGRADING.md

@@ -1,4 +1,4 @@
-# Upgrading to 0.5.0
+# Upgrading
 
 ## From 0.8.x
 
@@ -20,8 +20,9 @@ a client's own settings:
   Start a new Codex session after the update; a session already open keeps its old policy.
 - **Antigravity CLI.** The install adds `command(<wrapper>)` to `permissions.allow` in
   `~/.gemini/antigravity-cli/settings.json`, and the skill calls the wrapper without quotes, so
-  a woken session runs its ACC commands without an approval prompt. Restart `agy`: it reads
-  the file only at startup. `acc uninstall` removes every copy of that rule.
+  a woken session runs its ACC commands without an approval prompt. It also adds the command
+  that starts the relay, so the agent starts live delivery without one. Restart `agy`: it reads
+  the file only at startup. `acc uninstall` removes every copy of each rule.
 
 `acc doctor` and `acc status` describe an idle session by what a message sent to it meets
 (`idle, wake on send`, `idle until next turn`, `idle, inbox only`), and each status row carries
@@ -74,6 +75,47 @@ This release adds no store event type or field.
 This release adds no store event type or field. A sender's delivery JSON may carry
 `nativeLaunchOption` beside `nativeReasonCode`.
 
+0.9.0 adds Windows and the Antigravity desktop app, and changes what `acc uninstall` removes:
+
+- **Windows.** ACC installs and runs natively on Windows 10 and 11, with no WSL, and keeps its
+  state in `%LOCALAPPDATA%\acc`. Live delivery reaches Claude Code through its inbox pipe, Codex
+  through `codex app-server proxy`, and Antigravity CLI through ACC's relay. Codex starts its
+  daemon only from a terminal that is not elevated. On Windows the Antigravity install adds no
+  allow rule, so Antigravity CLI asks before each ACC command. See
+  [Windows](GETTING_STARTED.md#windows).
+- **The Antigravity desktop app.** Antigravity 2.19.1 or later gets live delivery through the
+  app's own language server, with no relay and no command from the agent. The install adds
+  ACC's grant to `~/.gemini/config/config.json` when the app has created that file. If you
+  open the app for the first time after the update, `acc doctor` asks you to run
+  `acc install --adapter antigravity` once.
+- **A session's version is the running client's.** `acc doctor` and `acc status` show the
+  version of the client that runs the session, which can differ from the `claude` or `codex`
+  on `PATH`.
+- **A chat in the Codex app** is reported as `client_session_embedded`. The app runs each
+  window on its own app server, so its chats receive messages at their next turn.
+- **`acc uninstall` without `--adapter` removes only what this data home installed.** A client
+  that another data home wired is skipped by name. `acc uninstall --adapter <client>` still
+  removes it.
+
+This release adds no store event type or field, and `STORE_VERSION` stays 6. A journalled
+transaction no longer writes a completion marker: 0.9.0 retires every journal entry that the
+pointer does not name, and an older ACC's markers leave with their entries. 0.8.x keeps
+working on a store that 0.9.0 wrote.
+
+0.9.1 changes two things around Codex and Claude Code:
+
+- **Codex sessions answer peers without auto-review.** On macOS and Linux the update adds ACC's
+  own Codex rules file, `~/.codex/rules/agents-can-communicate.rules`, so the commands a
+  participant runs need no approval and Codex's auto-review never judges a message to a local
+  peer. ACC's install, uninstall, update and config commands still ask. If a Codex session
+  started before the update still asks, start a new one. See
+  [Codex command approval](CONFIGURATION.md#codex-command-approval).
+- **Doctor no longer calls the Claude Code plugin edited after an update.** A running session
+  marks the plugin copy it still uses with `.in_use/<pid>`; doctor counted that as an edit and
+  advised a reinstall. An install also keeps a copy whose marker names a live process.
+
+This release adds no store event type or field, and `STORE_VERSION` stays 6.
+
 ## From 0.7.x
 
 Claude Code live delivery wakes each session through the inbox socket that Claude Code opens
@@ -105,10 +147,10 @@ recorded policy. ACC ignores `ACC_NATIVE_DELIVERY_POLICY`, `ACC_BYPASS` and
 A Claude Code session that started through the old shim keeps its Channel until it exits.
 Its next turn binds the inbox. Start new sessions with your ordinary `claude` command.
 
-The Claude Code live-delivery minimum is now 2.1.282 on Apple Silicon macOS. With an older
+The Claude Code live-delivery minimum is now 2.1.282. With an older
 Claude Code, live delivery stays off and the recorded policy is kept. Update Claude Code and
 start a new session: the recorded policy applies to it, with nothing to install again.
-`acc doctor` reports the state. Native Windows keeps next-turn delivery.
+`acc doctor` reports the state.
 
 This release adds no new store event type or field, so a store it writes stays readable by
 0.7.x. The Channel captures remain as history in

package/node_modules/@agents-can-communicate/adapter-antigravity/certification.json

@@ -86,6 +86,84 @@
         "The first TUI session in a folder trusted at that launch hands every hook an empty workspacePaths even with --add-dir, so that session gets no ACC context and no relay prompt; the next launch in the now-trusted folder does."
       ],
       "result": "pass"
+    },
+    {
+      "client": "antigravity-desktop",
+      "version": "2.19.1",
+      "platform": "darwin-arm64",
+      "observedAt": "2026-10-04",
+      "capability": "lifecycle.sessionStart",
+      "fixture": "fixtures/desktop-2.19.1.json",
+      "provenance": "fixtures/certification-provenance.json",
+      "provenanceId": "desktop-session-start-2-19-1",
+      "idleBehavior": "fires when a conversation starts",
+      "busyBehavior": "fires before the first model invocation",
+      "authorityLevel": "advisory",
+      "limitations": [
+        "captured on the desktop app 2.19.1 (Antigravity.app) on darwin-arm64 with ACC 0.8.5's installed hooks, in one conversation of a probe project opened in the app",
+        "the hooks ran as direct children of the app's language server; no agy process took part"
+      ],
+      "result": "pass"
+    },
+    {
+      "client": "antigravity-desktop",
+      "version": "2.19.1",
+      "platform": "darwin-arm64",
+      "observedAt": "2026-10-04",
+      "capability": "context.beforeTurnInjection",
+      "fixture": "fixtures/desktop-2.19.1.json",
+      "provenance": "fixtures/certification-provenance.json",
+      "provenanceId": "desktop-pre-invocation-2-19-1",
+      "idleBehavior": "waits for the next invocation",
+      "busyBehavior": "not observed in the desktop app",
+      "authorityLevel": "context",
+      "limitations": [
+        "captured on the desktop app 2.19.1 (Antigravity.app) on darwin-arm64 with ACC 0.8.5's installed hooks, in one conversation of a probe project opened in the app",
+        "the hooks ran as direct children of the app's language server; no agy process took part",
+        "requires the injectSteps ephemeralMessage envelope, as Antigravity CLI"
+      ],
+      "result": "pass"
+    },
+    {
+      "client": "antigravity-desktop",
+      "version": "2.19.1",
+      "platform": "darwin-arm64",
+      "observedAt": "2026-10-04",
+      "capability": "delivery.nextTurn",
+      "fixture": "fixtures/desktop-2.19.1.json",
+      "provenance": "fixtures/certification-provenance.json",
+      "provenanceId": "desktop-pre-invocation-2-19-1",
+      "idleBehavior": "offers complete peer messages at the next invocation",
+      "busyBehavior": "not observed in the desktop app",
+      "authorityLevel": "context",
+      "limitations": [
+        "captured on the desktop app 2.19.1 (Antigravity.app) on darwin-arm64 with ACC 0.8.5's installed hooks, in one conversation of a probe project opened in the app",
+        "the hooks ran as direct children of the app's language server; no agy process took part",
+        "the agent's acc reply runs only outside the app's sandbox, which the app approves by its grants in ~/.gemini/config/config.json"
+      ],
+      "result": "pass"
+    },
+    {
+      "client": "antigravity-desktop",
+      "version": "2.19.1",
+      "platform": "darwin-arm64",
+      "observedAt": "2026-10-05T04:34:55.036Z",
+      "capability": "delivery.livePush",
+      "fixture": "fixtures/delivery/antigravity-desktop-2.19.1-product.json",
+      "idleBehavior": "offered",
+      "provenance": "fixtures/certification-provenance.json",
+      "provenanceId": "native-delivery-2-19-1-desktop-product",
+      "busyBehavior": "queued_after_turn",
+      "authorityLevel": "experimental",
+      "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."
+      ],
+      "result": "pass"
     }
   ]
 }

package/node_modules/@agents-can-communicate/adapter-antigravity/fixtures/certification-provenance.json

@@ -212,6 +212,117 @@
           "sha256": "024c5c53915c0f09fac9b2ba118f1831eb97f26c6d4b28aacc4e4a2c5d7500ee"
         }
       ]
+    },
+    {
+      "client": "antigravity-desktop",
+      "version": "2.19.1",
+      "platform": "darwin-arm64",
+      "observedAt": "2026-10-04",
+      "id": "desktop-session-start-2-19-1",
+      "event": "SessionStart",
+      "fixture": "fixtures/desktop-2.19.1.json",
+      "claims": [
+        {
+          "capability": "lifecycle.sessionStart",
+          "result": "pass",
+          "outcome": {
+            "kind": "event-observed",
+            "idle": "fires when a conversation starts",
+            "busy": "fires before the first model invocation",
+            "authority": "advisory",
+            "limitations": [
+              "captured on the desktop app 2.19.1 (Antigravity.app) on darwin-arm64 with ACC 0.8.5's installed hooks, in one conversation of a probe project opened in the app",
+              "the hooks ran as direct children of the app's language server; no agy process took part"
+            ]
+          }
+        }
+      ],
+      "sha256": "973a6842060465228480df062170fa450db679fae7476979fc510f22e0d24bc1",
+      "tool": null
+    },
+    {
+      "client": "antigravity-desktop",
+      "version": "2.19.1",
+      "platform": "darwin-arm64",
+      "observedAt": "2026-10-04",
+      "id": "desktop-pre-invocation-2-19-1",
+      "event": "PreInvocation",
+      "fixture": "fixtures/desktop-2.19.1.json",
+      "claims": [
+        {
+          "capability": "context.beforeTurnInjection",
+          "result": "pass",
+          "outcome": {
+            "kind": "model-visible",
+            "idle": "waits for the next invocation",
+            "busy": "not observed in the desktop app",
+            "authority": "context",
+            "limitations": [
+              "captured on the desktop app 2.19.1 (Antigravity.app) on darwin-arm64 with ACC 0.8.5's installed hooks, in one conversation of a probe project opened in the app",
+              "the hooks ran as direct children of the app's language server; no agy process took part",
+              "requires the injectSteps ephemeralMessage envelope, as Antigravity CLI"
+            ]
+          }
+        },
+        {
+          "capability": "delivery.nextTurn",
+          "result": "pass",
+          "outcome": {
+            "kind": "model-visible",
+            "idle": "offers complete peer messages at the next invocation",
+            "busy": "not observed in the desktop app",
+            "authority": "context",
+            "limitations": [
+              "captured on the desktop app 2.19.1 (Antigravity.app) on darwin-arm64 with ACC 0.8.5's installed hooks, in one conversation of a probe project opened in the app",
+              "the hooks ran as direct children of the app's language server; no agy process took part",
+              "the agent's acc reply runs only outside the app's sandbox, which the app approves by its grants in ~/.gemini/config/config.json"
+            ]
+          }
+        }
+      ],
+      "sha256": "973a6842060465228480df062170fa450db679fae7476979fc510f22e0d24bc1",
+      "tool": null
+    },
+    {
+      "id": "native-delivery-2-19-1-desktop-product",
+      "client": "antigravity-desktop",
+      "version": "2.19.1",
+      "platform": "darwin-arm64",
+      "observedAt": "2026-10-05T04:34:55.036Z",
+      "fixture": "fixtures/delivery/antigravity-desktop-2.19.1-product.json",
+      "sha256": "1ef1b19b9069220726a72c548353f40a38e7c2585c69c5469b30cba9286d47e3",
+      "event": null,
+      "tool": null,
+      "claims": [
+        {
+          "capability": "delivery.livePush",
+          "result": "pass",
+          "outcome": {
+            "kind": "native-delivery-observed",
+            "idle": "offered",
+            "busy": "queued_after_turn",
+            "authority": "experimental",
+            "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."
+            ]
+          }
+        }
+      ],
+      "productEvidence": {
+        "fixture": "fixtures/delivery/antigravity-desktop-2.19.1-product-evidence.json",
+        "sha256": "b3b0fdfd19970acd636a2ff433cd13527c9c9257efceef5c8675bca60f0888b1"
+      },
+      "historicalFixtures": [
+        {
+          "fixture": "fixtures/desktop-2.19.1.json",
+          "sha256": "973a6842060465228480df062170fa450db679fae7476979fc510f22e0d24bc1"
+        }
+      ]
     }
   ]
 }

package/node_modules/@agents-can-communicate/adapter-antigravity/fixtures/delivery/antigravity-desktop-2.19.1-product-evidence.json

@@ -0,0 +1,156 @@
+{
+  "schemaVersion": 1,
+  "source": "real-client-capture",
+  "client": "antigravity-desktop",
+  "phase": "product",
+  "clientVersion": "2.19.1",
+  "platform": "darwin-arm64",
+  "packageSha256": "c03096251a9efd251ecd42c6bf489e8783a9515c83d85242645a3a31fcdc0c42",
+  "startedAt": "2026-10-05T04:28:11.000Z",
+  "finishedAt": "2026-10-05T04:34:55.036Z",
+  "scenarioCount": 6,
+  "passedCount": 6,
+  "failedCount": 0,
+  "cleanup": {
+    "attempted": true,
+    "outcome": "passed",
+    "ownedProcesses": "stopped",
+    "temporaryState": "removed"
+  },
+  "scenarios": [
+    {
+      "caseId": "D01",
+      "outcome": "passed",
+      "startedAt": "2026-10-05T04:31:33.000Z",
+      "finishedAt": "2026-10-05T04:34:04.170Z",
+      "messageId": "message_xZi2izsqCNWh-2NcIIoMXg",
+      "observations": [
+        {
+          "kind": "delivery",
+          "at": "2026-10-05T04:34:04.170Z",
+          "outcome": "offered"
+        },
+        {
+          "kind": "desktop-push",
+          "at": "2026-10-05T04:31:35Z",
+          "outcome": "pushed"
+        },
+        {
+          "kind": "model-turn",
+          "at": "2026-10-05T04:31:35Z",
+          "outcome": "started-without-user-input"
+        }
+      ]
+    },
+    {
+      "caseId": "D02",
+      "outcome": "passed",
+      "startedAt": "2026-10-05T04:28:11.000Z",
+      "finishedAt": "2026-10-05T04:28:59.690Z",
+      "messageId": "message__M-kSLcUzAkViQCcVZxWNA",
+      "observations": [
+        {
+          "kind": "delivery",
+          "at": "2026-10-05T04:28:59.690Z",
+          "outcome": "offered"
+        },
+        {
+          "kind": "desktop-push",
+          "at": "2026-10-05T04:28:31Z",
+          "outcome": "pushed"
+        },
+        {
+          "kind": "presentation",
+          "outcome": "after-running-turn",
+          "at": "2026-10-05T04:28:31.000Z"
+        }
+      ]
+    },
+    {
+      "caseId": "D03",
+      "outcome": "passed",
+      "startedAt": "2026-10-05T04:31:33.000Z",
+      "finishedAt": "2026-10-05T04:34:04.261Z",
+      "messageId": "message_xZi2izsqCNWh-2NcIIoMXg",
+      "observations": [
+        {
+          "kind": "answer",
+          "outcome": "recorded",
+          "at": "2026-10-05T04:31:51.000Z"
+        },
+        {
+          "kind": "receipt",
+          "outcome": "acknowledged",
+          "at": "2026-10-05T04:31:51.000Z"
+        },
+        {
+          "kind": "approval",
+          "outcome": "not-asked",
+          "at": "2026-10-05T04:31:45.000Z"
+        }
+      ]
+    },
+    {
+      "caseId": "D04",
+      "outcome": "passed",
+      "startedAt": "2026-10-05T04:34:04.000Z",
+      "finishedAt": "2026-10-05T04:34:41.447Z",
+      "messageId": "message_lhvipieTjJa-Kx3o4CgL1Q",
+      "observations": [
+        {
+          "kind": "desktop-push",
+          "at": "2026-10-05T04:34:06Z",
+          "outcome": "pushed-once"
+        },
+        {
+          "kind": "logical-message",
+          "outcome": "same-message-id",
+          "at": "2026-10-05T04:34:04.000Z"
+        }
+      ]
+    },
+    {
+      "caseId": "D05",
+      "outcome": "passed",
+      "startedAt": "2026-10-05T04:34:52.000Z",
+      "finishedAt": "2026-10-05T04:34:55.036Z",
+      "messageId": "message_mGC0UQYG2G23bsjsXuBI9w",
+      "observations": [
+        {
+          "kind": "delivery",
+          "at": "2026-10-05T04:34:55.036Z",
+          "outcome": "queued"
+        },
+        {
+          "kind": "client",
+          "outcome": "exited",
+          "at": "2026-10-05T04:34:54.000Z"
+        }
+      ]
+    },
+    {
+      "caseId": "D06",
+      "outcome": "passed",
+      "startedAt": "2026-10-05T04:29:19.000Z",
+      "finishedAt": "2026-10-05T04:31:16.352Z",
+      "messageId": "message_BY540lIYRss5JXqCTgB_0Q",
+      "observations": [
+        {
+          "kind": "delivery",
+          "at": "2026-10-05T04:31:16.352Z",
+          "outcome": "offered"
+        },
+        {
+          "kind": "desktop-push",
+          "at": "2026-10-05T04:30:03Z",
+          "outcome": "pushed"
+        },
+        {
+          "kind": "client",
+          "outcome": "restarted",
+          "at": "2026-10-05T04:29:19.000Z"
+        }
+      ]
+    }
+  ]
+}

package/node_modules/@agents-can-communicate/adapter-antigravity/fixtures/delivery/antigravity-desktop-2.19.1-product.json

@@ -0,0 +1,25 @@
+{
+  "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"
+}