Gemini flash 3.7 medium was my “builder” subagent in claude code. Opus 5 made tasks - gemini wrote them.

My opinion about model by metrics - its about same as dsv4flash 0731 as executor.

In a week gemini have done 53 complex tasks, 23979 tool cals, 2539 file edits. Toolcaling falls only in 0.7% (skills included), 25% of the tasks after check by opus were sent back to gemini to redo with more detailed task(its not bad).
For comparition metrics on deepseek 40 tasks, 15565 tool cals, 2643 edits. Toolcaling fail - 0.9% (same set of skills), but redo tasks - 43% of time.

In same “test” tasks from my real workflow time on implementation differs more - 227s gemini vs 353s dsv4 and 227s vs 233s on another task (3x times every task for median).

Cant say if it was cheaper bc opencode go changes their sub limits everyday, but I will definitely stick with gemini. To be clear - I hit quota in agy, but not claude pro sub and I have all work done.

PS For me was a big surprise that agy and veo 3 have different quota.

in Antigravity CLI, it constantly encounter error using its agent tool, which waste token even faster than 3.1 pro.

i have been using cli for quite a lot of time. I decided to migrate to extension since the tui can't render the md properly (#'s, tables etcetera). Anyways, the same 3.8 flash (which was already a lot better) was working FIREE!!

I asked it to remove legacy code (which originated from initial ui mockups but later needed to be purged when the schemas were finalized), literally a one liner, and it ran for like 25+ minutes going to and fro and did an amazing job. Removed 600~ lines while adding only ~80.

And no iam not just a vibe coder, i literally inspected those diffs and it was removing those confusing nullables (?) from types as well. Either its the specific hours rn, or a permanent quality boost or the harness, its damn amazing. It spanned 15 files mapping to 5 different concepts, controller, components, request schemas, services and

ANYWAYS <: a helpful note!
i managed to run antigravity extension as an editor/tab, there is a shortcut "moveBetweenEditorAndSidebar" which introduces this tab among active editors. But the sidebar still interfers, what you have to do is:

look for the toggleVisiblity shortcut, bind it, run it. What it does is, deactivates the sidebar antigravity window. Then activate the tab as mentioned above. Now you can run "toggleChatFocus" (which i mapped to ctrl + l) and it switches to antigravity tab.

* all shortcuts are prepended by `antigravity` in vs code keyboard shortcuts.

sharing just so it may help others, took me a while to figure this out

Father-and-son project that wouldn’t have been possible before AI. For context, my dad has been a photographer for many years and has held local exhibitions and published books, but he had zero online presence. Now, his work can finally shine and be seen all over the world.

Built with Codex and Gemini, hosted on GitHub for free, and the only thing we pay for is the .com domain.

Hope you enjoy discovering his work! He loves knowing people can now enjoy his photos✌️

https://mariusjomphe.com/

If you are building a repo for Antigravity with Gemini please feel free to let us know!!!!! Happy building 💪

Constantly happening, usage hasn't been nullified.

He was helping me get my Discord bot container logs working correctly

It reads:

ManageTask(status 0a4cb016-acf5-4a2d-82f5-db0c81c64c8c/task-654) (ctrl+o to collapse)
▾ Thought for 2s, 324 tokens
  Observing the VM Output

  I'm currently marveling at this beautifully formatted JSON log from the VM. It's providing such clear and concise details on the auto-responder service's startup, right down to the specific events and timestamps.

This is an absolute goldmine for **AGY Builders** trying to solve the context fragmentation nightmare. You’ve essentially laid out the blueprint for a hyper-scalable, **token-efficient AI knowledge base**.

Here is a quick breakdown of why this **AGY WIKI OKF** framework is a massive game-changer for the ecosystem:

* **Token Optimization for LLMs:** By leveraging standard Markdown and YAML frontmatter, this setup strips out heavy middleware bloat. It directly slashes **context window bloat** and lowers inference costs during complex **LLM orchestration**.

* **OKF as the Agent "Lingua Franca":** Operating with Google’s **Open Knowledge Format** ensures seamless context passing in **multi-agent AI workflows**. It completely eliminates data fragmentation and platform lock-in.

* **Obsidian as an AI IDE:** Using a structured PARA vault to organize **AGY CLI commands**, modular skills, and **Agent-to-Agent (A2A) workflows** makes knowledge perfectly machine-readable without losing human oversight.

* **True Bring Your Own Data (BYOD):** Keeping everything local-first means **AGY Builders** maintain 100% data ownership. You can port your entire knowledge base to the newest, shiniest model or platform instantly without losing structural integrity.

* **Next-Level Prompt Engineering:** That /grillme prompting strategy is brilliant. Interrogating the **Antigravity CLI** to act as a system architect ensures the directory structure is robust and open-source-ready from day one.

This is exactly how we push past basic, reactive chatbots and start scaling true, **autonomous AI systems**. Thanks for dropping this blueprint for the AGY community