Neil bf07b8f60e fix(antigravity): say Antigravity Chat isn't available on Windows instead of silently opening a terminal (#38997) ...

* fix(antigravity): say Antigravity Chat isn't available on Windows instead of silently opening a terminal

Google publishes no Windows agy-acp-server, so a Windows host refused
Antigravity chats with the generic 'agent' reason: launches fell back to a
terminal with no explanation and Settings showed nothing.

A Windows host now reports reason 'windows' (createSupport and published
availability), which launch receipts state as chat_unavailable_on_windows,
the new-tab picker labels 'No chat on Windows yet', and explicit-chat
failures explain. Agents and Accounts settings say so for a Windows host.
The decision is the execution host's OS, so a Windows client chatting on a
macOS or Linux host is unaffected; one predicate
(structuredChatUnavailableOnPlatform) gates it all.

Fixes #30817, STA-11245

* docs: correct chatUnavailableOnThisDesktop comment

2026-11-06 13:59:04 -08:00

..

catalog

fix(antigravity): wait for agy's composer before pasting continuation context (#38939)

2026-11-06 12:54:24 -08:00

choices

Use the shared agent picker for Automations (#37941)

2026-11-04 10:27:59 -08:00

contracts

fix(antigravity): say Antigravity Chat isn't available on Windows instead of silently opening a terminal (#38997)

2026-11-06 13:59:04 -08:00

permissions

…

picker

fix(antigravity): say Antigravity Chat isn't available on Windows instead of silently opening a terminal (#38997)

2026-11-06 13:59:04 -08:00

startup

fix(automations): accept Antigravity model and effort extra arguments (#39161)

2026-11-06 12:55:54 -08:00