Language: English | 简体中文
Web Archive: https://antigravity-256k-context-discrepancy.pages.dev/
Google Antigravity (including the Antigravity 2.0 desktop application, Antigravity IDE, and the agy command-line interface) advertises and displays in its client interface a 1,048,576 (1M) token context window for Gemini 4 Argon and Gemini 3.8 Flash. However, static disassembly of the official client binaries and analysis of local session databases show that a hardcoded machine-code instruction clamps the automatic context compaction threshold at 256,000 tokens (25% of the advertised window). Around the same period, Google support staff reversed 10 prior written forum confirmations regarding local subprocess invocations of agy -p from third-party coding tools by updating a non-contractual FAQ page without amending the formal Additional Terms of Service (ToS).
This repository organizes the technical records, disassembly data, and public forum/issue history into two text-only parts: Part I — Incident Research & Analysis (research/) and Part II — Static Binary Disassembly & Local Database Report (evidence/). All documents default to English at the top level of each directory, with corresponding Chinese editions in zh-cn/ subdirectories. No third-party binary executables or installers are stored in this repository; all analyzed official binaries are referenced by their direct Google Cloud Storage (storage.googleapis.com) download URLs and SHA-256 / SHA-512 cryptographic hashes so they can be verified independently.
Important
Latest Official Update (2026-11-06 11:50 UTC — Forum Thread #198430): This archive's findings were posted to the developer forum on 2026-11-05 at 16:21 UTC (raw snapshot: evidence/raw/forum_198430.json). Eight seconds later the forum's discourse_ai_spam system unlisted the topic; it was relisted on 2026-11-06 at 04:09 UTC. Forum support engineer @Rebbanpalli_Naveen then replied:
- App and CLI threshold confirmed together, with a new rationale: "In Antigravity App (2.29.0) and Antigravity CLI (1.5.1), automatic context compaction triggers by default around ~250K–256K tokens to maintain latency, reliability, and token efficiency, and is not currently user-configurable. We have shared your feedback requesting a configurable compaction threshold and clearer trigger indicators in
/contextwith our engineering team." The day before,#1432gave the reason as "multi-step reasoning quality, turn latency, and per-turn quota consumption"; quota is no longer mentioned. - Quota multipliers: "subscription quota consumption correlates with the complexity and volume of agent work and adjusts dynamically based on system capacity, so fixed per-model multipliers are not published."
agy -p: "The Google Antigravity Terms of Service (Section 6) and Official FAQ apply together"; wrappingagyinside third-party coding agents is not permitted under consumer plans.- Not addressed: the request to state the 256K limit in documentation and model listings, the
base = 0parser defect inAGY_CLI_AUTO_COMPACT_OVERRIDE, and the 512K/900K options gated behind the single-entry whitelist. A follow-up comment posted in#1432at 10:24 UTC on 2026-11-06 has not received a reply. - Follow-up (2026-11-06 15:44 UTC, Post #5):
@A_Fengreplied that a threshold no setting can raise is a ceiling rather than a default, noted the change in stated rationale, and asked four questions answerable with yes, no, or a date: whether any supported setting lets a session exceed 256,000 tokens before compaction, which public page discloses the 256K compaction before purchase, which rationale is official, and whether (and in which release) the docs, model listings, and/contextwill be corrected to show 256,000.
Note
Official Update (2026-11-05 19:56–20:00 UTC — GitHub Issue #1432): Five hours after this archive's disassembly report was filed as a [Bug] in google-antigravity/antigravity-cli#1432 (raw API snapshots: evidence/raw/issue_1432.json, evidence/raw/issue_1432_comments.json), official repository collaborator @chandrashakherkamasani self-assigned the issue, labeled it duplicate, feature request, and feedback (omitting bug while leaving the issue state OPEN), and posted the first on-record GitHub engineering response confirming both the intentional 256,000 clamp and the /context display discrepancy:
- Intentional
256,000-token clamp for per-turn quota control: "Even on models with a 1M-token (1,048,576) context window, Antigravity CLI intentionally sets the default automatic compaction threshold to256,000tokens. Because agentic turns re-send the active conversation context on every step, compacting at ~256K balances multi-step reasoning quality, turn latency, and per-turn quota consumption (larger active windows consume significantly more quota on every subsequent turn). As noted in the forum thread you linked, user-selectable context window tiers above 256K are not available yet." - Acknowledgement of misleading
1.0M/contextdisplay: "/contextcurrently reports the selected model's total underlying context capacity (1,048,576tokens) rather than the active256,000-token auto-compaction threshold. We agree that showing1.0Mwithout surfacing where automatic compaction will trigger makes this look like an unexpected cap rather than a compaction threshold." - Unaddressed instruction-level defects: The response did not address why
AGY_CLI_AUTO_COMPACT_OVERRIDEinv1.5.1passesbase = 0(xor %eax,%eaxbefore both parser calls at VA0x9c34c9aand0x9e875aa, causing percentage overrides to evaluate to0), or why a mismatch between published/UI specifications (1,048,576) and shipped binary behavior (0x3E800/256,000) is classified as afeature requestrather than abug.
- Advertised
1,048,576(1M) Window vs. Hardcoded0x3E800(256,000) Binary Clamp: In both Desktopv2.29.0(language_server.exe) and CLIv1.5.0–v1.5.1(antigravity),defaultmodels.Gemini4Argonregisters a maximum context window of0x100000(1,048,576tokens). However, the checkpoint configuration calculatorcortex/utils/utils.GetCheckpointConfigexecutes the hardcoded x86-64 instruction sequencecmp $0x3e800, %edx; mov $0x3e800, %esi; cmovb %edx, %esi(81 fa 00 e8 03 00 be 00 e8 03 00 0f 42 f2, at file offset0x7fe5802inv1.5.0and0x7fb0fe2inv1.5.1), clamping the automatic compaction trigger threshold tomin(calculated, 256,000)across all models. Whilev1.5.0andv1.5.1quietly restored theos.LookupEnv("AGY_CLI_AUTO_COMPACT_OVERRIDE")lookup that had been compiled out as an empty string inv1.3.5–v1.4.x(inv1.5.1it accepts only absolute token counts and applies only to whitelisted models), the0x3E800clamp itself remains unchanged (see Volume 2 and Evidence Report §2.3 & §4). On 2026-11-04, Google staff member@chundurivconfirmed in developer forum thread#198191that Gemini models in the Desktop app compact automatically at around 250K tokens and that the threshold "is a fixed default and isn't user-configurable yet" (see Volume 5, Quote 1.8). On 2026-11-05 (19:56 UTC), CLI maintainer@chandrashakherkamasanifurther confirmed in GitHub Issue#1432that the CLI "intentionally sets the default automatic compaction threshold to256,000tokens" to limit "per-turn quota consumption," and agreed that showing1.0Min/contextwithout surfacing the active256,000threshold "makes this look like an unexpected cap." On 2026-11-06 (11:50 UTC), forum support engineer@Rebbanpalli_Naveenstated in#198430that in both App 2.29.0 and CLI 1.5.1 compaction "triggers by default around ~250K–256K tokens to maintain latency, reliability, and token efficiency, and is not currently user-configurable." - Consistent
256,000Token Ceiling & 70-Second Compaction Overhead: In 209 pre-patch local Antigravity CLI 1M-Gemini sessions (~/.gemini/antigravity-cli/conversations/*.dbprior to2026-11-04 00:00:00 UTC+8, 15,575 model calls), all 15,575 request metadata records setmax_context_tokens = 256000, and no single-attempt call (retries = 0) exceeded 300K tokens.@murias002's independent Issue#878audit of 310 CLI sessions (65,613 model calls) measured a consistent ceiling from input sizes: a maximum single-call input of255,999tokens and no calls above 300K. Each automatic compaction pauses the session for a median of 70 seconds, omits the summarization call's token usage fromgen_metadata, replaces ~250K tokens of history with a15K–17Kprose summary (CORTEX_STEP_TYPE_CHECKPOINT = 23,truncation_reason = 2), and invalidates the 240K+ implicit prompt cache (see Evidence Report §2.5–§3 and Volume 2 §3). Gemini 4 Argon3.0x Quota Consumption Ratio & Gated Context Tiers: Controlled A/B testing within the same 5-hour quota window shows that, when normalized by published API list prices,Gemini 4 Argonconsumes subscription quota at 3.00x the rate ofGemini 3.8 Flash(equivalent to$6/$30per 1M tokens vs.$2/$10published, and7.64x–9.25xin web pure-input tests). Meanwhile, the client binaries already include512K(1.3xquota multiplier) and900K(1.8xquota multiplier,Expensive: true) context window options restricted by a length-1"Gemini 4 Argon"whitelist and server-side feature flags (see Volume 2 §3–§4 and Evidence Report §2.4).agy -pPolicy Reversal Without a ToS Amendment: Between September 16 and October 8, 2026 (16:23 UTC), three Google support engineers posted 10 written confirmations on the official developer forum stating that running the unmodifiedagy -pbinary as a local subprocess from third-party coding tools (such as Codex and Claude Code) complied with Section 6 of the Additional Terms of Service. On October 8 at 17:34 UTC, 71 minutes after the last of these confirmations and 26.5 hours after the confirmation in#186246, staff reversed this position in#187241and warned of automated account suspensions (cloudcode-pa.googleapis.comHTTP 403TOS_VIOLATION), later confirming in Forum Thread#191689Post #8 that the formal ToS had not changed since September and that only a non-contractual FAQ page had been edited in mid-October (see Volume 3 and Volume 5).
Documents the timeline from July 2025 through November 5, 2026 (v1.5.1), covering the binary disassembly of the context window gates, the AGY_CLI_AUTO_COMPACT_OVERRIDE behavior across versions, empirical quota consumption measurements, the forum records before and after the agy -p policy change, community and official responses to the limit, and verbatim source excerpts.
| Document | English Edition (Default) | 简体中文版 (zh-cn/) |
Contents |
|---|---|---|---|
| Overview Report | research/dossier.md | research/zh-cn/dossier.md | Summary of findings, key metrics table, stakeholder perspectives, and all 57 footnote definitions |
| Volume 1 | 01-incident-overview-and-timeline.md | zh-cn/01-incident-overview-and-timeline.md | Project background, Windsurf team acquisition, legacy gemini-cli retirement, quota pool rules, and chronological timeline |
| Volume 2 | 02-256k-hardcoded-gates-and-binary-teardown.md | zh-cn/02-256k-hardcoded-gates-and-binary-teardown.md | Context window statistics, AGY_CLI_AUTO_COMPACT_OVERRIDE changes (1.3.5 vs. 1.5.0–1.5.1), three binary gates (0x3e800), 70s compaction overhead, and Argon quota measurements |
| Volume 3 | 03-agy-p-headless-policy-reversal-and-bans.md | zh-cn/03-agy-p-headless-policy-reversal-and-bans.md | Record of the 10 prior forum confirmations, the October 8 reversal, confirmation that only the FAQ was edited, and account suspension appeal cases |
| Volume 4 | 04-community-and-official-responses.md | zh-cn/04-community-and-official-responses.md | Community and official responses to the limit: the community patch as client-side evidence, Google staff guidance, Google's ADK case study, third-party context tools, and cross-tool boundaries |
| Volume 5 | 05-verbatim-quotes-and-evidence-vault.md | zh-cn/05-verbatim-quotes-and-evidence-vault.md | Reverse-engineering posts, assembly listings, forum replies before and after the policy change, and side-by-side ToS/FAQ texts |
| Sources Index | research/sources.md | research/zh-cn/sources.md | Metadata and verbatim excerpts for 57 cited sources and 9 supplementary references |
| Single-File Report | antigravity-256k-report.md | — | Consolidated English report in one file covering findings, timeline, disassembly, quota tests, policy records, verbatim quotes, binary hashes, and all 57 cited sources |
Provides a read-only static disassembly comparison between language_server.exe (PE32+ x86-64, SHA-256 c98e7c33...e1c3d5) extracted from the official desktop installer Antigravity-x64.exe (v2.29.0) and the antigravity CLI binary (v1.5.0 BuildID 5fb6af4f..., plus v1.5.1 BuildID 696031ae...), a complete breakdown of the Antigravity CLI SQLite schema and Protobuf metadata decoded across 237 local pre-patch CLI conversation databases (209 1M-Gemini sessions, 15,575 model calls), and raw GitHub API records across 10 related Issues.
| Document / Directory | Path | Description |
|---|---|---|
| English Report (Default) | evidence/evidence-report.md | 10-section static analysis report in English (installer verification, machine-code offsets, SQLite statistics, and reproduction commands) |
| Chinese Report (简体中文版) | evidence/zh-cn/evidence-report.md | 10-section static analysis report in Chinese (matching the English structure section by section) |
| Raw JSON Snapshots & Manifests | evidence/raw/ | Official manifest_linux_amd64.json, 23 raw GitHub API JSON responses (including issue_1432.json and issue_1432_comments.json), and 2 forum thread JSON snapshots (forum_198191.json, forum_198430.json; 26 text files) |
No binary executables are hosted in this repository. The original files can be downloaded directly from Google's official cloud storage (storage.googleapis.com/antigravity-public) and verified against the hashes below:
| Component | Version / Platform | Official Download URL / Source | Size & Cryptographic Hash |
|---|---|---|---|
| Desktop Installer | v2.29.0 (Windows x64) |
Antigravity-x64.exe |
169,295,640 bytesSHA-256: 944b109bcb377f9f94f86eeea7cfa9315d4b42d84fb9d5bad689058fc11c12ba |
| Desktop Language Server | v2.29.0 (resources/bin/language_server.exe) |
Bundled inside app-64.7z within the Antigravity-x64.exe installer above |
187,342,336 bytesSHA-256: c98e7c331da5bcc37002a550e7d625b4c636f775fa2804f73777c6a500e1c3d5 |
CLI Release Archive (v1.5.0) |
v1.5.0 (Linux x64, 2026-11-04) |
cli_linux_x64.tar.gz (Manifest: linux_amd64.json) |
Archive: 69,781,910 bytes (antigravity binary: 238,604,688 bytes, BuildID 5fb6af4f2e1d489f3ada0fd785060f48)SHA-512: e6031f850929210705d8c2393a5665b82b8c3b19684a6d3c556cafa31f26f77acbf164dfee96ca84a5ae7670ac0cc238a974c981c517b269194bdccff271cbd5 |
CLI Binary (v1.5.1) |
v1.5.1 (Linux x64, 2026-11-05) |
cli_linux_x64.tar.gz (manifest: linux_amd64.json; CHANGELOG.md) |
Archive 72,209,583 bytes, SHA-512: f70406654ebd966f211424338259e2d38d099c48734e901dc06975063e5a0137d55b6eb9366b75983c6908bbc20ae92a2617656bb191d8ed6fe429d654bca4f5Extracted antigravity: 240,857,488 bytes (BuildID 696031ae34e5e5e26a9d7c436e85317f), SHA-256: 72738cf0445918483956a5f0da33abdfcfb21a12dd9a421fd57d063782826669 |
| CLI Install Script | Cross-platform entry point | https://antigravity.google/cli/install.sh |
7,643 bytesSHA-256: 62966c07365423bd4dc209355060744058fb30d60f5323e2d360e39de64e5042(not redistributed here; retrieved 2026-11-04, unchanged on 2026-11-05) |
antigravity-256k-context-discrepancy/
├── README.md # English overview, key findings, index & binary hashes
├── README.zh-CN.md # Chinese overview, key findings, index & binary hashes
├── LICENSE # Multi-licensing terms & Fair Use notice (English & Chinese)
├── antigravity-256k-report.md # Single-file English report consolidating Parts I and II
├── research/ # [Part I] Incident research reports (English default + zh-cn/)
│ ├── dossier.md # Overview report & key metrics table
│ ├── 01-incident-overview-and-timeline.md
│ ├── 02-256k-hardcoded-gates-and-binary-teardown.md
│ ├── 03-agy-p-headless-policy-reversal-and-bans.md
│ ├── 04-community-and-official-responses.md
│ ├── 05-verbatim-quotes-and-evidence-vault.md
│ ├── sources.md # Metadata & excerpts for 57 cited sources + 9 supplementary sources
│ └── zh-cn/ # Chinese edition (filenames 1:1 identical to English)
│ ├── dossier.md
│ ├── 01-incident-overview-and-timeline.md
│ ├── 02-256k-hardcoded-gates-and-binary-teardown.md
│ ├── 03-agy-p-headless-policy-reversal-and-bans.md
│ ├── 04-community-and-official-responses.md
│ ├── 05-verbatim-quotes-and-evidence-vault.md
│ └── sources.md
├── evidence/ # [Part II] Static binary disassembly & SQLite database report
│ ├── evidence-report.md # English 10-section static analysis report
│ ├── zh-cn/
│ │ └── evidence-report.md # Chinese 10-section static analysis report
│ └── raw/ # Raw text artifacts (23 text/JSON files, zero binaries)
│ ├── manifest_linux_amd64.json # Official CLI release manifest (v1.5.0 SHA-512 source)
│ ├── forum_198191.json # Forum thread #198191 snapshot (official reply on the fixed ~250K threshold)
│ └── *.json # 21 raw GitHub API JSON responses
└── index.html # Self-contained single-file static web archive (https://antigravity-256k-context-discrepancy.pages.dev/)
This repository applies different terms to original and quoted material (see LICENSE for full bilingual terms):
- Research Reports, Disassembly Notes & Data Tables (
research/*.md,research/zh-cn/*.md,evidence/evidence-report.md,evidence/zh-cn/evidence-report.md,antigravity-256k-report.md,index.html): Licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). You may copy, redistribute, translate, or quote these materials for any purpose, provided you credit either this GitHub repository (https://github.com/magiccodelab/antigravity-256k-context-discrepancy) or the author's blog post (https://afengblog.com/blog/antigravity-256k-context-discrepancy.html). - Third-Party Raw API Snapshots (
evidence/raw/) & Quoted Texts: The release manifest, 21 GitHub API JSON snapshots, the forum thread JSON snapshot, and quoted forum replies, Additional Terms of Service (ToS), and Official FAQ texts remain the copyright property of their respective rightsholders (including Google LLC and respective community contributors). They are included here under Fair Use (17 U.S.C. § 107) for technical research and documentation, and are excluded from the CC BY 4.0 license above. Third-party scripts are not redistributed: the official install script is cited by URL and SHA-256, and the communitypatch_agy.pyscript remains with its author@LiraNuna.
- Compilation & Verification: The materials in this repository were organized by the author in collaboration with Google Antigravity (
Gemini 4 Argon). Given the volume of material, minor omissions or inaccuracies may exist; if you notice any discrepancy, please refer directly to the primary cited sources (research/sources.md) and raw API snapshots (evidence/raw/). - Timezone Note (
UTC+8): Because the author is based in the UTC+8 timezone, some calendar dates or local file/build timestamps mentioned in the reports reflectUTC+8local time and may differ by up to one calendar day fromUTC(or US Pacific Time) timestamps on GitHub and the developer forum. These date differences are timezone offsets rather than factual errors; where exact timestamps are needed, please check the explicitUTCtimestamps in the timeline or the original records inresearch/sources.mdandevidence/raw/.
Interestingly: Had this investigation relied solely on the unmodified default
256,000-token (0x3E800) auto-compaction threshold enforced by the official Google Antigravity CLI, Antigravity itself would have lost context mid-way and been incapable of assisting in completing this archive.
🙏 Special Acknowledgements:
Our sincere gratitude goes to the Google DeepMind Gemini team for training such a genuinely remarkable 1M-context model (Gemini 4 Argon) capable of synthesizing this entire forensic archive.
Equally, a special thank-you to the Google Antigravity Product & Monetization team for their truly visionary product decisions—most notably their commitment to "Get Out of the Model's Way" by hardcoding 0x3E800 (256,000) into the binary and overturning 10 official written assurances via an FAQ edit. Without your "user-first" engineering, this repository would have had no reason to exist.