Hi team, I’d like to report a bug in version 2.2.1.
Before updating to 2.2.1, every time I used the /browser command, the system would properly delegate the task to a Subagent. It would prompt me to enable remote debugging on my local Chrome, and this workflow worked perfectly on Windows.
However, after the 2.2.1 update, the routing logic for the /browser command seems broken. Sometimes, instead of invoking the Subagent, the system tries to run a built-in Browsing xxx inline UI directly in the chat. The problem is that this built-in tool seems to only support Linux. As a result, it gets stuck at No browser pages open and throws an error stating it can only run in a Linux environment.
It looks like the command is erroneously dispatching to an unsupported Linux-only headless mode instead of the reliable local Chrome MCP Subagent path.
Could you please fix this routing logic in the next update, or perhaps provide a setting to force /browser to default to the Subagent mode? Thanks!
error executing cascade step: CORTEX_STEP_TYPE_OPEN_BROWSER_URL: failed to open URL in Antigravity Browser. DO NOT try alternative ways of opening the page. If this tool has failed multiple times, end the task, and state that the open_browser_url tool failed with the following error: local chrome mode is only supported on Linux