Google Antigravity hits remote-SSH wall

This is the real fault line in agentic IDEs: autonomy looks clean on a laptop, but the minute the code lives on a legacy SSH box, the editor’s hidden assumptions become the bottleneck. Antigravity feels like a strong control plane, but not yet a turnkey answer for "agent on my PC, execution on an old server."

• –Google’s own docs frame Antigravity as local-first, which means the remote-host-as-primary-workspace model is not the default path.
• –CentOS 7-era machines are exactly where server payloads, browser hooks, and modern agent plumbing tend to be the least forgiving.
• –The pragmatic pattern is to keep the agent, UI, and verification loop local, then use plain SSH only for execution and file movement.
• –If deeper remote orchestration is required, a bastion VM, container, or newer jump host is usually a cleaner target than retrofitting every old box.
• –The broader lesson is that "agentic coding over SSH" is really an infrastructure design problem, not just a product choice.