Antigravity + Gemini 3 are serious contenders

The News

Google’s rebirth as the AI behemoth it was always meant to be has finally come to fruition. With the release of Gemini 3, Google has made it clear that it can compete with—and even surpass—OpenAI and Anthropic. And now it seems everyone and their mother is shipping AI-enhanced IDEs which, in almost all cases, are forks of VS Code. Google’s offering is no exception: Antigravity—a rather interesting choice of name.

The Need

I’ve been working on a Node.js–based orchestration framework for AI agents—yes, yet another one, even though there are already countless options out there. I looked, but none really did what I wanted, so I went ahead and built my own, thanks in part to the helping hands of Claude Code (Anthropic). Bottom line: it works fine. There’s still a lot of manual tweaking required, but I was able to achieve things I couldn’t do with plain ChatGPT or Claude alone. However, it lacks a UI. I didn’t even consider building or using one, because I figured I just needed something simple. But I’ve now realized that once you have a workflow that works and want to expand, the lack of a UI is exactly what holds you back.

The Solution: Enter Antigravity + Gemini 3

I could have simply asked Claude to help me build a UI, but this felt like the perfect opportunity to try something new for something new. So I prompted my way through explaining what I wanted the UI to do, and to my amazement (a word I’ve used far too often this year given the rapid pace of progress), three prompts later I had a simple UI in which I could construct workflows by dragging in tasks and connecting them—similar to what you’d do in more advanced workflow tools. The incredible part—beyond the fact that it took only three prompts—is that it understood the existing workflow perfectly and generated a UI that didn’t modify any of the existing code. It literally just built a UI on top of it.

Antigravity in action

So What’s the Conclusion?

We’re nowhere near done advancing LLMs. Gemini 3 is so good that it’s scary all over again. I used to joke that Claude Code could easily replace ten developers; with Gemini 3, I’m starting to wonder if I was being too modest.

Comments

Vibe Coding Alert! How I Rebuilt a Wix Site and Fed the “AI Will End SaaS” Panic

My better half is an artist and maintains a Wix.com site. For the second time in two years, Wix decided to raise the hosting fees. That’s when I suggested to my spouse that I could rebuild the website and host it on Firebase (where I host most of my projects). I assumed this wouldn’t be a big deal (I was wrong) and started researching ways to use a lightweight CMS with Firebase support. Such a system exists — it’s called FireCMS — and it’s excellent. Before I dive deeper, here’s her original site (no longer a paid Wix site): Miyuki's WIX site Her instructions were clear: replicate it as closely as possible. So I went to work. I created a product development document with use cases, scope, screenshots from the original site, the required features, and of course FireCMS integration. I used ChatGPT to draft the document, then set up a new Firebase instance, and finally launched the Vibe Coding agent (Claude Code). The process wasn’t too different from my other projects, but what sur...

How I Ended Up Creating an AI Playground to Illustrate and Educate

TL;DR AI Playground User Guide

MCP + Context: engineering for the context – hard lessons learned

Intro I have built my own orchestration framework because most of what I’ve seen was too complex or tried to lock you into creating workflows a certain way. I wanted something very simple and yet maximally flexible. I’m not going into details here on the framework — that’s another blog post — but I will in some cases explain why I could do what I did thanks to the flexibility of the framework, which is a dynamic DAG, can do call-backs, and uses functions and MCP servers. I will also not explain in detail what I’m doing with my current workflow, other than to say I was looking for a way to bypass large language models and instead run it on my own system at home. I succeeded with that — but that’s another blog post. Instead, what I will try to explain in this post is the most important thing after prompt engineering: context engineering, and why it’s so crucial to manage that aspect (especially when you run this at home). Stage setting A couple of weeks ago, Anthropic posted this: ...

Digital Wire: Digital business, digital transformation, APIs, AI and payments

Search This Blog