DOCS: Update quota and pricing page

[g-samroberts]

Summary

Update quota and pricing page. Additionally, add callouts to the plans page of the website.

Fixes google-gemini/maintainers-gemini-cli#1507

• Updated relevant documentation and README (if needed)
• Added/updated tests (if needed)
• Noted breaking changes (if any)
• Validated on required platforms/methods:
  • MacOS
    • npm run
    • npx
    • Docker
    • Podman
    • Seatbelt
  • Windows
    • npm run
    • npx
    • Docker
  • Linux
    • npm run
    • npx
    • Docker

[gemini-cli]

Hi @g-samroberts, thank you so much for your contribution to Gemini CLI! We really appreciate the time and effort you've put into this.

We're making some updates to our contribution process to improve how we track and review changes. Please take a moment to review our recent discussion post: Improving Our Contribution Process & Introducing New Guidelines.

Key Update: Starting January 26, 2026, the Gemini CLI project will require all pull requests to be associated with an existing issue. Any pull requests not linked to an issue by that date will be automatically closed.

Thank you for your understanding and for being a part of our community!

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on enhancing the documentation related to Gemini CLI quotas and pricing. It updates the primary quota-and-pricing.md page with clearer explanations, improved structure, and more actionable advice for users managing their costs and understanding subscription tiers. Additionally, it integrates new callouts within other relevant documentation pages to guide users directly to the comprehensive 'Plans page' for detailed subscription comparisons and upgrade options, streamlining the user experience for understanding available services.

Highlights

• Documentation Update: Updated the quota-and-pricing.md documentation to improve clarity and provide more detailed information on subscription options and usage tips.
• Plans Page Integration: Introduced callouts in authentication.md and gemini-3.md to direct users to the new 'Plans page' for subscription comparisons and upgrades.
• Wording Refinement: Refined language across the documentation to better describe free tier usage, API key benefits, and differences between Gemini API and Vertex AI.

Changelog

• docs/get-started/authentication.md
  • Added a note box with a link to the 'Plans page' for subscription comparisons.
• docs/get-started/gemini-3.md
  • Added a note box with a link to the 'Plans page' for upgrading subscription limits.
• docs/resources/quota-and-pricing.md
  • Updated the introductory sentence to use 'increased' instead of 'higher limits' for clarity.
  • Moved the 'Note' about negotiated commercial discounting and replaced it with a direct link to the 'Plans page' for a high-level comparison of subscriptions.
  • Added a new 'Overview' subheading.
  • Modified the description of free usage limits to be more explicit: 'Your free usage is governed by the following limits...'
  • Simplified the link for purchasing a Gemini Code Assist Subscription through Google Cloud, removing the 'Set up Gemini Code Assist' link.
  • Changed 'This includes:' to 'This includes the following request limits:' for clarity.
  • Refined the wording for API key usage to state 'reaching a limit on your quota' instead of 'quota limits.'
  • Renamed the section 'Check usage and quota' to 'Check usage and limits.'
  • Updated the description for checking usage to refer to 'applicable limits' and 'information about the limits associated with your current quota.'
  • Changed 'Pay as you Go API key' to 'pay-as-you-go plan' in the 'Tips to avoid high costs' section.
  • Expanded the 'Tips to avoid high costs' with more detailed advice, including being selective with suggestions, using precise prompts, and monitoring usage.
  • Renamed the section 'Gemini API vs. Vertex' to 'Gemini API vs. Vertex AI.'
  • Updated the descriptions for Gemini API and Vertex AI with more detailed explanations and bullet points.

Activity

• The author updated relevant documentation as indicated by the checked checkbox in the PR description.
• The pull request addresses and fixes issue google-gemini/maintainers-gemini-cli#1507.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates the quota and pricing documentation and adds callouts to the plans page in other related documents. The changes generally improve clarity and provide more helpful information to users. However, I've noted one concern in docs/resources/quota-and-pricing.md where a potentially important pricing disclaimer was removed. Please see the specific comment for details.

_{Note: Security Review has been skipped due to the limited scope of the PR.}

[github-actions]

Size Change: -2 B (0%)

Total Size: 26 MB

ℹ️ View Unchanged

Filename	Size	Change
./bundle/gemini.js	25.5 MB	-2 B (0%)
./bundle/node_modules/@google/gemini-cli-devtools/dist/client/main.js	221 kB	0 B
./bundle/node_modules/@google/gemini-cli-devtools/dist/src/_client-assets.js	227 kB	0 B
./bundle/node_modules/@google/gemini-cli-devtools/dist/src/index.js	11.5 kB	0 B
./bundle/node_modules/@google/gemini-cli-devtools/dist/src/types.js	132 B	0 B
./bundle/sandbox-macos-permissive-open.sb	890 B	0 B
./bundle/sandbox-macos-permissive-proxied.sb	1.31 kB	0 B
./bundle/sandbox-macos-restrictive-open.sb	3.36 kB	0 B
./bundle/sandbox-macos-restrictive-proxied.sb	3.56 kB	0 B
./bundle/sandbox-macos-strict-open.sb	4.82 kB	0 B
./bundle/sandbox-macos-strict-proxied.sb	5.02 kB	0 B

_{compressed-size-action}

[chrstnb]

Build failed: Build process failed with link errors:

05:14:29 [ERROR] ✗ Found 2 invalid links in 2 files.
05:14:29   └─ /plans/ - invalid link to custom page
05:14:29   └─ /plans/ - invalid link to custom page
05:14:29 [ERROR] [starlight-links-validator-integration] An unhandled error occurred while running the "astro:build:done" hook
    Some invalid links point to custom pages which cannot be validated, see the `exclude` option for more informations at https://starlight-links-validator.vercel.app/configuration#exclude

[g-samroberts]

Link issue is a false positive, I believe it needs an exclusion for the /plans/ page in the website config. I've tested a staged version and it works.