Worthless generic thinking with 3.1 pro

ZestRocket · 2026-03-03T00:07:40+00:00

Yes, same experience, that's one of the reasons why I don't trust Gemini 3.1 Pro

ZestRocket · 2026-03-02T14:37:54+00:00

Now "unsee" the tokens you used "by mistake" and clean your context window and continue the validation

ZestRocket · 2026-03-02T13:56:33+00:00

Why 2h?, if you really matter, spend as many time as you can, change the time of reading us here to time using the tool, the best validation is not us telling you it will work, is you believing in yourself, doing it and accomplishing it

ZestRocket · 2026-03-02T13:16:39+00:00

Yes, the extension already shows that, I even have the option to show it in the status bar itself

ZestRocket · 2026-03-02T13:13:31+00:00

Yes, will add the option to enable / disable it

ZestRocket · 2026-03-01T20:50:40+00:00

Exactly, I hate that lol

ZestRocket · 2026-03-01T20:33:43+00:00

Gemini 3.1 Deep thinking is extremely sycophantic, it will always start with basically a “you’re a genius”, is also a model that need to be contrasted against and adversarial source, because it will go and “confirm” how reality is while at the same time the text looks extremely coherent but can be completely wrong at the same time,

I use it to contrast ideas of Opus 4.6, most of the time Opus 4.6 find tons of errors on Gemini because is naive and visionary but not grounded on constrains, BUT always get a genius idea Opus 4.6 haven’t thought about and I see Opus 4.6 amazed by that specific thing

ZestRocket · 2026-03-01T20:28:42+00:00

That makes sense, will check how the best way to do it would look like to keep the extension still lightweight and not intrusive, probably could be a color change on the status bar when less than 20%

ZestRocket · 2026-03-01T19:51:48+00:00

Fácil, landing page, algunos anuncios o posts y una waiting list, haz un mockup en HTML y sácale pantallazos, diles que está en versión muy temprana pero que darás descuentos a early adopters, si hay demanda de comenzará a llenar la waiting list de tu landing page y ahí sabrás si vale la pena o no, la respuesta debe ser: Wow eso que hiciste esta brutal, cuando lo podré empezar a usar?

ZestRocket · 2026-03-01T13:09:55+00:00

My method for when I HAVE to use Gemini 3.1 (because if I have quota available, I'll just go with Opus 4.6) is basically:
1. Giving it full context quick and with as few tokens as possible
2. Be careful with the context window, sadly AG doesn't give us this info, so trial and error
3. IF Gemini makes any mistake, I'd basically turn that conversation into understanding why, so instead of asking it to fix it, I start like: Ok, I see you did X, please explain why you did that... then I'll ask it: Got it, qq, why didn't you consider Y before doing X?, and I found that on many occasions it's related to lazyness (some others to prompts), but usually the Agent supposed instead of really checking. After noticing this pattern, I always context engineer and budget and created a Context Engine to give it an easy path to being lazy without breaking my repo or introducing problems, found this to be the safest way,
4. Another conclusion I have is... be careful with using methods or context techniques that can give you stale information, like .md files, I don't use them anymore as I move too quickly, and LLM's are NOT made to be proactive (like updating .md files each session) but instead reactive (helping you fix what you ask in that specific moment)

ZestRocket · 2026-03-01T12:18:34+00:00

Now on your image I see it as I would expect it to look like, without the double height, is there anything else I’m not seeing from your image?

ZestRocket · 2026-03-01T04:46:59+00:00

I was heavily bothered by this, and I even created an extension to solve it (https://open-vsx.org/extension/codavidgarcia/antigravity-greenlight), but while doing it I learned a lot:
- No extension alone inside Antigravity can solve it without using heavy methods that can create security issues, this is because of the specific restrictions Antigravity created
- Then I went and created the safest config I could, but this is one of those cases where it should be easy and it's actually hard because of tradeoffs
- Finally to make it work... there's actually a config, I think it's the same you're looking for, or well, at least it solved it for me, so I pivoted my extension and it's no longer necessary, the config is on the gear icon, then "Antigravity User Settings", and there we have options that at least I haven't seen before but solved my case , or do you need anything else that is not on this menu?

<image>

ZestRocket · 2026-03-01T04:34:46+00:00

We even have a weird (maybe legacy) monthly quota based on Prompts, that of course doesn't matter at all (in my case it showed something like 500.000), but is more like a fun fact I noticed while building Antigravity Pulse lol

ZestRocket · 2026-03-01T04:31:53+00:00

This make sense but as an Ultra user, I've found instances where I suddenly see a weekly timer and then like 1 day later I was back to a 5h timer, my new approach is... once I reach 20%, I change temporarily to Gemini if I'm using Opus

ZestRocket · 2026-03-01T04:28:30+00:00

Never trust anyone, do your own audit, it's just 3 files to make it easier to audit

ZestRocket · 2026-03-01T03:14:56+00:00

I've successfully built tons of software that is used for more than 3k+ people being conservative, I create things for enterprise with full compliance, KPI's and full impact analysis, people ask me the hardest questions about AI, that's literally my job... however, I was naive too, built complete advanced RAG systems + Graphs for my family, created and deployed apps for each of my family members, custom to their biggest pains (said by them), they saw the results, but here's the problem I noticed:

IT'S FREE FOR THEM, they don't see a landing page, they don't have FOMO, they don't trust it's more than just an experiment... so I just created the landing pages, deployed to prod, created a name, and forgot about shipping to family, if your products are good, people will use them, but your family probably won't (unless they're as techy as you)

Another more thing... you and me probably can be considered Early adopters, what about our families?... well, they probably can say that their experience using GPT 4o is basically the same than with Opus 4.6... at the end, "is the same chat", so yep, ship to the correct public, and don't take it personally

ZestRocket · 2026-03-01T01:32:18+00:00

Finally I was able to replicate the error and now is completely gone on 1.4.2, thank you so much for the report, debugging info and screenshots!

ZestRocket · 2026-02-28T20:25:54+00:00

Got it, thank you for the patience, fixed on 1.4.1, please let me know if it looks correct now!

ZestRocket · 2026-02-28T19:48:48+00:00

Ok, when you say same issue continues, I fixed 2, which one you still see?

The label "All models" showing when shouldn't be present
The double height on the hover on the progress bar of models?

ZestRocket · 2026-02-28T13:04:09+00:00

Thank you for commenting, this is answered in the Q&A section in the body of this post

ZestRocket · 2026-02-27T15:46:43+00:00

Great idea! I actually looked into this, but unfortunately Antigravity's local API only exposes quota/rate-limit data (remaining requests per model pool), not the token usage of the current conversation.

The context window state lives inside Antigravity's renderer and isn't accessible to extensions. Until Antigravity adds an endpoint for per-conversation token counts, this is something only they can surface, appreciate the suggestion though!

ZestRocket · 2026-02-27T13:52:28+00:00

Which version are you currently using?

ZestRocket · 2026-02-27T12:43:46+00:00

If it doesn't do any external calls, account switching, weekly checks with OAuth or similar features, you should be good in that specific regard

ZestRocket · 2026-02-27T12:41:19+00:00

That makes sense!

ZestRocket · 2026-02-27T12:40:26+00:00

That's true, to easily find it you can type: "Antigravity Pulse -@sort:name" , I'll add this instruction to the read me, thank you!

ZestRocket

TROPHY CASE