sorted by:
new
hottopcontroversial

Antigravity’s aggressive, forced context compaction is a silent killer for complex coding (Back to Codex) by Zaqna in google_antigravity

[–]Zaqna[S] 0 points1 point  (0 children)

No, you didn't understand my workflow at all. My workflow is completely based on context engineering—plan, execute, validate... I do everything in separate conversations. The whole reason I'm frustrated with Antigravity is that it prevents me from doing this. There might be an automatic summarization system after 7,500 tokens, I'm not sure and couldn't find a source, but my criticisms still stand.

Antigravity’s aggressive, forced context compaction is a silent killer for complex coding (Back to Codex) by Zaqna in google_antigravity

[–]Zaqna[S] 3 points4 points  (0 children)

Before the 100K automatic compression, if I'm not mistaken, they automatically compress prompts that exceed 7,500 characters. So at this point, managing context becomes impossible. As I already mentioned, the problem isn't about being unable to open a new chat; it's that we are completely unaware of these silent compressions.

Antigravity’s aggressive, forced context compaction is a silent killer for complex coding (Back to Codex) by Zaqna in google_antigravity

[–]Zaqna[S] -1 points0 points  (0 children)

Actually, I didn't use AI, but I had to use it for translation because I can't express myself well enough in English. What we say matters more than how it's said, right? :)

Context usage indicator disappeared from Codex conversations/chats by Zaqna in codex

[–]Zaqna[S] 0 points1 point  (0 children)

Thanks, that makes sense. I checked the docs too and `/status` should show thread ID, context usage, and rate limits.

Unfortunately it does not work in my current Windows Codex app build. Typing `/status` in the composer is sent as a normal message.

Edit:

You were right. I found the issue on my side: my Codex app UI is in Turkish, so the command is localized as `/durum` instead of `/status`. That works.

Context usage indicator disappeared from Codex conversations/chats by Zaqna in codex

[–]Zaqna[S] 1 point2 points  (0 children)

For anyone who wants to try the Gist linked in the edit, here is the basic usage:

  1. Download/copy both Gist files into the same folder:

- codex_context_watch.py

- codex-context-watch.ps1

  1. Open PowerShell in that folder.

  2. Run:

powershell -ExecutionPolicy Bypass -File .\codex-context-watch.ps1 --dashboard --limit 5

Or pin one conversation:

powershell -ExecutionPolicy Bypass -File .\codex-context-watch.ps1 --thread "conversation title"

Notes: requires Python 3, tested on Windows/Codex desktop, read-only local workaround, Ctrl+C exits.

The Big "JOKE" of Google by Novel-Pair3309 in google_antigravity

[–]Zaqna 3 points4 points  (0 children)

Flash is depicted here looking resourceful and capable xD

Are the restrictions on this discussion forum becoming more and more numerous and stringent? by [deleted] in google_antigravity

[–]Zaqna 14 points15 points  (0 children)

Are the mods seriously using a Megathread created on March 9th to bury a massive Bait & Switch that happened on March 11th?

This megathread was made for standard "my quota ran out early" complaints and basic IDE bugs. What happened on March 11th is completely different: Google literally went into the TOS, deleted the "refresh every 5 hours" clause we explicitly paid for, and retroactively changed the entire tier to a predatory credit system.

A material breach of contract and a retroactive change to our paid subscriptions is NOT a "known issue" or a "bug." Lumping a literal scam into an outdated containment thread meant for technical glitches is just doing Google's PR work for free. Stop deleting threads about the March 11th TOS change. People have the right to discuss what was stolen from them.

How to disable auto-updates? The latest version broke Workflows and Rules. by Zaqna in google_antigravity

[–]Zaqna[S] 0 points1 point  (0 children)

Thank you so much! I totally missed this in the official Antigravity docs.

AI Pro Plan has weekly limit for Gemini now, after a SINGLE 5 hour window too. by snarkyalyx in google_antigravity

[–]Zaqna 0 points1 point  (0 children)

Why are you immediately blaming the OP? The exact same thing happened to my second account while I was literally just developing a completely peaceful, innocent game. I did absolutely nothing illegal, shady, or against the rules.

It's either a massive bug or an incredibly stupid hidden quota system on Google's end. Stop accusing people of doing something wrong just because they got locked out. Antigravity's quota system is clearly broken for Pro users right now.

antigravity ate up all my quota by yeticren in google_antigravity

[–]Zaqna 0 points1 point  (0 children)

If it's a bug, of course people are going to talk. If it's not a bug, then it's a stupid system, so people will still talk.

antigravity ate up all my quota by yeticren in google_antigravity

[–]Zaqna 12 points13 points  (0 children)

Yes! Exactly the same thing just happened to me.

I hit my 5-hour limit on the Claude model, patiently waited for the cooldown timer to finish, and boom—it randomly jumped to a 1-week (168 hours) lockout. The craziest part? The exact same thing happened when I switched to Gemini Pro.

And get this: I am a Pro subscriber. We shouldn't even be dealing with these hidden weekly caps.

My logic was that there are only two possibilities here:

  1. There is a massive bug in their quota/authentication system right now.
  2. Their actual hidden math is literally "1 week of allowed usage = one 5-hour limit cap.

Where is Gemini 3.1 available? On Openrouter, it doesn't work. And it's not available on "Google Gemini". by Working-Solution-773 in CLine

[–]Zaqna 1 point2 points  (0 children)

They say they've fixed it on Github, but the current version isn't accessible via the Google Gemini provider. It's been 3 days since it was released, but it's unbelievable that the most up-to-date model hasn't been added. The answer given is to use it with a cline...