[irvandikky]

Fixes a bug in combos where an exhausted antigravity/agy model blocks all other models in the same provider connection due to connection-wide quota exhaustion short-circuiting in quotaCache.ts. Scopes rate limiters by model family in rateLimitManager.ts and updates antigravityQuotaFamily.ts for 'agy' spelling alias.

[gemini-code-assist]

Code Review

This pull request adds support for the 'antigravity' and 'agy' providers to the quota and rate-limiting systems, ensuring that model families (such as Claude and Gemini) are properly isolated. It updates prefix normalization, provider checks, rate limiter key generation, and quota exhaustion logic, and adds corresponding unit tests. Feedback on these changes highlights two key issues: in both the quota cache and the rate limiter, grouping unknown models under the generic 'other' family will cause them to incorrectly share quota evaluations and rate limits. To prevent this, exact-model scoping should be preserved for any models classified under the 'other' family.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

Grouping all unknown models under the 'other' family in isQuotaExhaustedForRequest causes them to share a single quota evaluation. If one unknown model is exhausted but another is not, the exhausted model will not be correctly blocked because matchingWindows.every(...) will evaluate to false. To preserve exact-model scoping for unknown models, we should match the exact model name when the family is 'other'.

    const requestedFamily = getAntigravityQuotaFamily(requestedModel);
    const matchingWindows = quotaNames.filter((windowName) => {
      const family = getAntigravityQuotaFamily(windowName);
      if (family === "other" || requestedFamily === "other") {
        const getBare = (m: string) => {
          const norm = m.toLowerCase().trim().replace(/^(antigravity|agy)\/\//, "");
          const idx = norm.indexOf("/");
          return idx >= 0 ? norm.slice(idx + 1) : norm;
        };
        return getBare(windowName) === getBare(requestedModel);
      }
      return family === requestedFamily;
    });

[gemini-code-assist]

Using the 'other' family name directly in the rate limiter key groups all unknown models under a single rate limiter. A 429 on one unknown model would then incorrectly pause requests for all other unknown models on the same connection. We should use the exact model name as the scope when the family is 'other' to preserve exact-model rate limiting.

Suggested change

	if ((provider === "antigravity" || provider === "agy") && model) {
	const family = getAntigravityQuotaFamily(model);
	return `${provider}:${connectionId}:${family}`;
	}
	if ((provider === "antigravity" || provider === "agy") && model) {
	const family = getAntigravityQuotaFamily(model);
	const scope = family === "other" ? model : family;
	return `${provider}:${connectionId}:${scope}`;
	}

[diegosouzapw]

Nice fix — the family-scoping approach is correct and I confirmed the 'other' family exact-scoping issue flagged by the automated review is already handled in your second commit. Tests are well-targeted (Claude/Gemini isolation + 'agy' alias + 'other' exact-scope). Looks ready to merge as-is.

[diegosouzapw]

Thanks @irvandikky! Real fix for connection-wide quota exhaustion short-circuiting on antigravity/agy multi-model combos. I extracted three helpers from isQuotaExhaustedForRequest so it clears the cognitive-complexity cap (behavior unchanged, tests green). Validated in local merge-train @ 2ae9ba63c (FAST gates green: static + changed tests + vitest).