**Title (Title)**: [Bug] AGY 2.4.2 Regression: Misbehaving MCP server freezes entire IDE conversation panel
**Body (Body)**: Hi team,
I am migrating this bug report from the GitHub CLI repository (Issue #701) at the request of the maintainer (@manirajc).
Description:
Since upgrading to AGY 2.4.2, there appears to be a regression regarding how the IDE handles unresponsive MCP servers. Specifically, if an MCP server (e.g., markitdown-mcp) misbehaves, hangs, or times out, it causes the entire conversation panel in the Antigravity IDE to freeze. The UI becomes completely unresponsive, forcing a hard restart of the IDE session to recover.
Environment:
- OS: Windows
- Antigravity Version: 2.4.2
- Triggering Component:
markitdown-mcp(but likely affects any unresponsive MCP server)
Steps to Reproduce:
- Configure an MCP server in the IDE.
- Trigger a condition where the MCP server hangs, throws a silent error, or fails to respond gracefully.
- Observe that the entire conversation panel completely freezes instead of timing out or showing an error state.
Expected Behavior:
The IDE should isolate MCP server failures. If a tool call times out or the server crashes, the conversation panel should remain responsive, display an error alert to the user, and allow the conversation to continue (or at least provide an option to restart the specific MCP server).
Additional Context:
This severely impacts the developer workflow, as any unstable external MCP server can take down the entire IDE session. Combined with other recent process management bugs (e.g., Issue #682 regarding orphaned language_server processes), IDE stability in the 2.4.x branch has been challenging.
Please let me know if you need any local logs or diagnostic information to help track this down!
Best regards,
Gerald