Remote Control becomes unresponsive after queuing a message, while the desktop app remains functional

Google Antigravity
1

The issue occurs in Antigravity Remote Control in a browser (at least when accessing from mobile).

Steps to reproduce:

  1. Start an Antigravity session on the desktop application.
  2. Connect to that session through Remote Control from a browser.
  3. While an agent is running, send a message that enters the queue.
  4. Try to type another message or approve/reject a pending command from Remote Control.

Actual result:
After a message is queued, the Remote Control UI stops accepting input:

  • The chat text box does not accept typing.
  • Approve/reject command controls do not respond.
  • The session becomes impossible to control from Remote Control.

\* observed even after page refresh observed in chrome mobile and brave mobile.

Important comparison:
The Antigravity desktop application on the host machine remains fully functional at the same time. I can type in the chat and approve or reject the same pending commands there.

This appears to be a Remote Control web UI/state synchronization issue, not an agent-session freeze.

Expected result:
Queuing a message must not disable the chat input or command-approval controls in Remote Control.

versions:
antigravity v 2.12.2 (GUI, not CLI, not IDE)
Microsoft Windows 10 (version 10.0.19045.6466)

2

Hi @dcaldr ,

Thank you for reaching out and sharing these details with us.

Could you please try updating your Antigravity desktop application to v2.13 (or later) and re-pairing your Remote Control session? This should resolve the issue and allow the prompt queue to work smoothly as intended.

Please let us know how it goes—we’re very happy to help if you need anything else.

3

Tried it for few days and seems perfectly resolved
in one conversation (that started prior update to v 2.13+) sometimes bacame unresponsive (need to refresh page) however it seemed one off