Tag: tooling

TL;DR

• Google tripled Gemini usage limits for Antigravity twice in one week after developers hit caps within hours; other Gemini Apps surfaces kept tighter quotas. [1]
• This is not generosity; it’s a live-fire test of compute-based metering for agentic dev tools that Google will extend and harden across Gemini Apps, Cloud, and Antigravity in 2026. [1][2][3]
• Rivals (GitHub Copilot and AWS Q Developer) are shipping the same playbook—rate limits, usage credits, and request-based billing—so quota-aware workflows are now table stakes. [4][5][6]

What the source said

9to5Google reported during the week of Google I/O 2026 that Google introduced compute-based usage limits for Gemini and then raised Antigravity’s ceilings twice—first a 3× rate-limit increase and later a 3× weekly quota bump—after users hit caps within a few hours of work. Varun Mohan of Google DeepMind said some users reached the weekly limit “after a couple work sessions,” and Google reset paid-plan quotas two times in the same week. The site added that post-reset quotas remained below prior levels and that increases applied only to Antigravity, not to other Gemini Apps surfaces like web or mobile. [1]

Why it matters

Google Antigravity is the agent-first developer suite—CLI, desktop app, and orchestration layer—pitched at Google I/O 2026 as “agents that do work,” not just chat. Caps that bite during compile–test–debug loops jeopardize the IDE of record and erode trust on day 1 of an agent pitch. Teams that adopted Antigravity 2.0 following the I/O keynote now face a quota regime that can interrupt multi-step sessions mid-sprint. [2][7]

The people who feel the blast radius aren’t only individual coders. They include SRE leads forecasting throughput for Q3 2026, procurement managers matching AI spend to monthly budgets in USD, and vendors like JetBrains or the VS Code marketplace whose extensions fail if an agent loop ends early. The fact that Google raised Antigravity limits twice while leaving other Gemini surfaces unchanged signals a priority: keep developer stickiness in the IDE hub where session economics matter most. [1][3]

Original analysis

Contrarian read

• Consensus: Two quota hikes in one week show that Google listened, and the worst is over.
• My take: The hikes are a pressure release, not a reversal. Google is normalizing compute-based metering because agent loops are bursty and costly; Antigravity merely hit the wall first. Gemini access already hinges on plan-bound limits, and Cloud services publish quota regimes; expect more explicit meters, not fewer, through 2026. [3][7]

Why? Major rivals are aligning revenue to inference cost. GitHub begins request-based Copilot billing on June 1, 2026 and documents rate limits by surface. AWS Q Developer lists concrete service quotas per account and region. The industry favors quotas because they curb runaway loops and create predictable upsell ladders across Pro, Business, and Enterprise tiers. [5][6][4]

Back-of-envelope: the “lockout tax” on a team

Assumptions (midsize product group in the US):

• Fully loaded developer cost: $120/hour.
• Antigravity weekly limit hit “after a couple work sessions,” forcing context rebuilds, tool re-wiring, or model swapping; assume 15 minutes of friction per lockout per engineer. [1]
• Ten engineers rely on Antigravity for code generation, refactors, and agent tasks; each hits one friction event per week.

Math (shown):

• 0.25 hours × $120/hour = $30 friction per engineer per event.
• $30 × 10 engineers = $300/week.
• If two events per week before the second reset, that’s ~$600/week.
• $600/week × 52 weeks ≈ $31,200/year.

Even if the second quota increase halves the friction, you still pay a five-figure ($10k+) annual “lockout tax” unless you add quota-aware automation—e.g., route to a backup model when Antigravity nears its ceiling or shift longer loops to off-peak/cloud jobs with batch scheduling. The exact number varies, but the slope is clear: invisible ceilings become silent productivity losses that compound. [1]

2x2: Who tolerates Gemini usage limits for Antigravity?

• Budget high, tolerance high: S&P 500 engineering orgs and big tech platforms. They’ll buy higher tiers or negotiate enterprise quotas and SLOs; the risk is hidden throttling on new agent behaviors until contracts land. [6]
• Budget high, tolerance low: YC and Series B startups in launch weeks. They’ll multi-home across Gemini, Copilot, and Claude; a single mid-sprint lockout pushes vendor diversification within 24 hours. [4][5]
• Budget low, tolerance high: GitHub Student Pack users and hobbyists. They’ll live with caps but practice “quota hygiene” (shorter sessions, fewer tool calls) and push bulk tasks to cheaper or local options. [3]
• Budget low, tolerance low: One-person US consultancies on fixed-fee milestones. They’ll switch IDE agents or plugins the first time a quota blocks a client deadline.

Named-stakeholder breakdown

• Google: Keep Antigravity credible as the agentic coding cockpit announced at I/O 2026. Ship visible meters, predictable resets, and paid expansion paths that never strand a session mid-loop. [2][3]
• GitHub (Copilot): The June 1, 2026 request-based billing shift lowers the PR cost of Google’s caps—“everyone’s doing it”—but raises expectations for in-IDE transparency and dashboards. [5][4]
• AWS (Q Developer): Quota-first culture is an advantage; documented limits with knobs look safer to CIOs who want predictable spend and throughput. [6]
• Tool vendors (JetBrains, VS Code extensions): Build quota-aware orchestration (retry/backoff + model failover) so long-running agent runs don’t collapse at 95% completion.
• Team leads/procurement: Push for multi-vendor agent stacks and SLAs with concrete daily/weekly and per-session ceilings rather than vague “fair use.” [6][4]

What others are missing

The real unit of value is shifting from tokens to agent sessions in the IDE. Antigravity runs a loop of code edits, test runs, file ops, and tool invocations; a weekly token pool hides the cost shape of that loop. A cap that feels roomy for chat can choke a refactor+test+debug cycle in VS Code or JetBrains. That’s why Google raised Antigravity limits while leaving other Gemini surfaces unchanged: session economics bite first in the IDE, which needs session-oriented quotas and in-IDE telemetry to prevent brittle loops. [1][2][3]

What to watch next

1. By June 30, 2026, Google will publish explicit per-tier Antigravity numeric ceilings (daily and weekly) and ship an in-product “quota meter” in the Antigravity UI or CLI release notes; you can verify this in public docs and changelogs. [2]

2. By September 30, 2026, GitHub will add an in-IDE Copilot quota dashboard for Pro/Business that shows remaining weekly/monthly usage and reset times, confirmed via VS Code or JetBrains extension changelogs. [5][4]

3. By Q4 2026, at least one mainstream IDE or agent framework will ship automatic “quota-aware scheduling” (defer/route/shorten loops near cap) with documented support for Google Antigravity and one rival such as Copilot or AWS Q Developer. [6][4]

My take

Raising Antigravity limits twice was the right triage in May 2026, but the message is louder than the move: agent work costs real compute, so quotas are product strategy. If Google wants developers to live in Antigravity, quotas must become a first-class UX surface—clear meters, graceful degradation, and paid escape hatches that never dead-end a sprint. Otherwise, Copilot’s request-based world and AWS’s quota-first culture will peel off teams that prize predictability in 2026 and 2027. The winners will be the tools that make quotas boring. [1][5][6]

Sources

1. Google has tripled Gemini usage limits for Antigravity, twice — 9to5Google (https://9to5google.com/2026/05/21/google-has-tripled-gemini-usage-limits-for-antigravity-twice/) — Details the two 3× increases, user lockouts, and Varun Mohan’s quota resets during I/O week.

2. All the news from the Google I/O 2026 Developer keynote — Google Developers Blog (https://developers.googleblog.com/all-the-news-from-the-google-io-2026-developer-keynote/) — Confirms Antigravity as Google’s agent-first developer platform introduced at I/O 2026.

3. Gemini Apps limits & upgrades for Google AI subscribers — Google Support (https://support.google.com/gemini/answer/16275805?hl=en) — Documents plan-bound Gemini access and the existence of usage limits across tiers.

4. Usage limits for GitHub Copilot — GitHub Docs (https://docs.github.com/en/enterprise-cloud%40latest/copilot/concepts/rate-limits) — Explains Copilot rate limits and guidance when users hit them.

5. Requests in GitHub Copilot (usage-based billing) — GitHub Docs (https://docs.github.com/en/copilot/concepts/billing/copilot-requests) — States Copilot’s move to request-based, usage-linked billing starting June 1, 2026.

6. Amazon Q Developer endpoints and quotas — AWS General Reference (https://docs.aws.amazon.com/general/latest/gr/amazonqdev.html) — Lists Q Developer service quotas and regions, illustrating quota-first design in rival tooling.

7. Google is making Gemini CLI users switch to its new Antigravity 2.0 — TechRadar Pro (https://www.techradar.com/pro/google-is-making-gemini-cli-users-switch-to-its-new-antigravity-2-0-so-what-will-it-mean-for-you) — Independent coverage of Antigravity 2.0 (CLI and SDK) around the I/O 2026 timeframe.

Title: Minecraft Java Edition is removing code obfuscation — here’s what it means for modders

If you’ve ever squinted at a decompiled class named something like a.b.c and wondered what on earth it did, today’s news will make your day. Mojang is removing code obfuscation from Minecraft: Java Edition, a change designed to make creating, updating, and debugging mods far simpler. (minecraft.net)

Why this matters
For years, Java Edition shipped with obfuscated code — an industry‑standard tactic that hides internal names to slow down reverse engineering. In 2019 Mojang met modders halfway by publishing “obfuscation mappings,” a Rosetta Stone that mapped scrambled names back to human‑readable ones. That helped, but it still left modders juggling remappers, toolchains, and crash logs full of gibberish. Now Mojang says the game will stop being obfuscated altogether, starting with the first snapshot after the “Mounts of Mayhem” launch. (minecraft.net)

What exactly is changing

• Snapshots after the Mounts of Mayhem release will ship un‑obfuscated: class, method, field, and variable names will be readable by default. That means clearer crash logs and easier debugging. (minecraft.net)
• During the transition, Mojang will publish side‑by‑side “experimental” un‑obfuscated builds and the traditional obfuscated builds so tool authors can adapt. (minecraft.net)
• Obfuscation maps will disappear from version JSONs because they’re no longer needed. Each client/server JAR will also include a LICENSE file that links to the EULA and Usage Guidelines. Importantly, the EULA itself isn’t changing. (minecraft.net)

A quick look back
Publishing mappings in 2019 (Snapshot 19w36a) was the first big step toward a more transparent codebase. At the time, Mojang explicitly framed the move as a way to help the community navigate updates without months of detective work — and those mappings became a staple of modern mod toolchains. The new policy simply removes the intermediary step. (minecraft.net)

What modders should expect

• Tooling updates: Many mod frameworks, patchers, and loaders were designed for an obfuscated game. Expect a short period where maintainers update remapping logic, build scripts, and bytecode transformers to the new reality. Mojang’s dual‑release window should cushion that landing. (minecraft.net)
• Faster updates: Readable names reduce guesswork when upstream changes land, which should shorten the time between a new snapshot/release and mod updates. That was the spirit of the 2019 mappings — and it’s even more true without obfuscation in the way. (minecraft.net)
• Clearer crash reports: With original names preserved, crash logs become far more actionable for both modders and players filing bug reports. (minecraft.net)
• Same rules as before: You’ll see a LICENSE inside the JAR that points to the EULA/Usage Guidelines. This is about easier development, not changing how Minecraft’s code or assets can be used or redistributed. (minecraft.net)

Key takeaways

• Mojang is ending code obfuscation for Minecraft: Java Edition, beginning with the first snapshot after “Mounts of Mayhem.” (minecraft.net)
• Temporary dual builds (obfuscated and un‑obfuscated) will help tool authors and modders transition. (minecraft.net)
• Obfuscation maps are going away; original class/method/field/variable names will ship by default. (minecraft.net)
• EULA and Usage Guidelines remain unchanged; a LICENSE file inside the JAR links to them. (minecraft.net)
• This builds on Mojang’s 2019 step of publishing mappings with every release (Snapshot 19w36a). (minecraft.net)

SEO-friendly FAQ

• What is code obfuscation in Minecraft: Java Edition?
  It’s the process of renaming classes, methods, and fields to unreadable identifiers to hinder reverse engineering. Java Edition has used it since release; Mojang began publishing mappings in 2019 to help modders. (minecraft.net)

• When will obfuscation be removed?
  With the first snapshot that follows the