61–70 of 224 posts
Google really can’t help themselves but to have some internal re-org kill off a public thing people are actively using. It’s honestly impressive how consistent they are.
The usual playbook is they rename it a few times first, then they kill it.
I stopped using Google products due to their propensity for killing them off. I continue to be proven correct in my assertion that they do not care about their customers.
100%. I really wish that I could treat them as a valid option, but they continuously reaffirm the position that it is dangerous to rely on them for anything commercial.
Mechanics that I found in the binary with a few agents, more information than I could glean from the GitHub page or the docs: - A Chrome DevTools Protocol / Playwright client. - macOS Seatbelt sandbox (--sandbox flag) with some special Node / v8 stuff. - Sentry for crash reporting and Unleash for feature flags. - A SKILL.md system mirroring Anthropic's skills convention. - Subagents, an artifacts review workflow (sla…
If the agent won't tell you what it's programming is, it's not your agent.
Two fast reflections:
1. I personally really doubt you can stay competitive selling such low-agency products to agentic developers, who are used to having access to/ability to see & reform their agentic worlds.
2. Also impressed by the hubris of giving everyone a single month to make the transition! I'd love the Google Graveyard to keep track of how long between announcement and shut down products got; I expect Gemini CLI getting axed for Antigravity CLI with one month transition is close to a record.
Earlier quoted context omitted.
The rest of out here watching usage and telemetry to decide where to invest, meanwhile, over at Google…
What if their telemetry shows very low usage? I've seen virtually no discussion of Gemini CLI online.
It was a complete buggy mess - at one point I asked Gemini why it could not use the network despite having network access enabled in the sandbox settings, and it told me that although it had network access, it couldn't use mdnsresponder while running with the built-in sandbox. Like, how well thought out, network access without DNS.
After burning through about 80% of my 5-hour window of credits, I finally just went sandboxless to get the thing running. It hit the limit pretty quickly. I waited until the 5 hour limit was up, and found the 5 hour window had morphed into a one week window, still drained of credits.
I thought at least I can keep on using Gemini CLI until Google figures out this Antigravity thing. Oh well.
That is one reason I avoid Flutter at all costs despite other reasons.