Gemini coding tools / Gemini CLI

Unknown — conflicting Whether consumer Google-account Gemini CLI daily request quotas are still current

• Source A: Gemini Code Assist consumer account deprecation — Starting June 18, 2026, Gemini Code Assist IDE extensions and Gemini CLI stopped serving requests for Gemini Code Assist for individuals, Google AI Pro, and Google AI Ultra. Login with Google access for those consumer paths ended.
• Source B: Gemini Code Assist and Gemini CLI quotas — Current Gemini Code Assist / Gemini CLI quota documentation still describes consumer Google-account daily request numbers and still tells individual developers they can obtain higher daily limits via Google AI Pro or Ultra.
• Applies to: Individual Google-account / consumer Gemini CLI authentication versus remaining Code Assist Standard and Enterprise subscriptions
• Decision impact: Do not publish a Gemini CLI usage-limits owner that treats consumer daily request numbers as current Fact. Standard (1500) and Enterprise (2000) remain the documented remaining subscription path, but consumer-tier numbers are in official-source conflict.
• TraceCheck status: Unresolved — Derived outputs must not treat one side as settled Fact.
• Last checked Sep 10, 2026, 12:00 PM UTC

Unknown — conflicting Whether Gemini CLI still recommends personal Google login after the 18 June 2026 consumer cutoff

• Source A: Gemini Code Assist consumer account deprecation — Starting June 18, 2026, Gemini Code Assist IDE extensions and Gemini CLI stopped serving requests for Gemini Code Assist for individuals, Google AI Pro, and Google AI Ultra. Login with Google for those consumer paths ended.
• Source B: Gemini CLI authentication setup — The Gemini CLI authentication setup page, last updated 17 August 2026, still recommends that most users log in with a personal Google account and still lists Google AI Pro and Ultra under individual Google accounts.
• Applies to: Individual Google-account / consumer Gemini CLI authentication after 18 June 2026
• Decision impact: Do not treat the setup guide's personal-Google-login recommendation as current Fact for consumer individuals, AI Pro, or AI Ultra. Standard/Enterprise and paid API-key paths remain documented remaining routes.
• TraceCheck status: Unresolved — Derived outputs must not treat one side as settled Fact.
• Current interpretation: TraceCheck treats the dated deprecation and I/O timeline as the consumer-login cutoff, and records the later authentication guide as an unresolved official-source conflict rather than current consumer Fact.
• Last checked Sep 10, 2026, 8:00 AM UTC