I need to rant about the core design philosophy of Antigravity 2.0, because this weekend’s updates have made it painfully clear who Google is actually building for.
Google decided to hard-remove terminal visibility for background tasks. When the agent executes a command, we no longer see the raw stdout or stderr. We just get a sanitized, summarized status bubble.
When I am debugging complex GLSL shaders, checking my raw hardware logs, or fixing FastAPI routing for my IoT air-quality monitor, I absolutely need to see the raw error traces. I am trying to build a premium, polished React dashboard (using strict oval UI constraints, not generic boxes), and the agent is silently failing in the background because I can’t read the actual Webpack errors to correct it.
Google is treating us like consumers who want a “magic box,” not engineers who need control over the metal.
This is exactly why DeepSeek V4 and local Opencode setups are winning the developer mindshare. The Chinese open-source ecosystems assume you are an engineer who needs full, transparent access to your infrastructure. They scale their models to be ruthlessly efficient, and they don’t hide the logs.
When my goal is to build an engineering portfolio capable of landing a 5 LPA CTC role, I need tools that teach me, not tools that hide the errors from me.
Are we just accepting that Big Tech is dumbing down developer tools, or is everyone else moving to transparent open-source IDEs? Let me know below.