Docs: Update release information regarding Gemini 3.1

[jkcinouye]

Summary

Gemini 3.1 is currently rolling out. It is not available to all users, but will show up under /models once available.

Details

This update clarifies how to look for Gemini 3.1 availability and how to use it once available.

Related Issues

Related to #19532

How to Validate

This is a docs-only change; please look for any unintended changes or mistakes.

Pre-Merge Checklist

• 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-code-assist]

Summary of Changes

Hello @jkcinouye, 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 updates the documentation to reflect the ongoing rollout of Gemini 3.1 Pro Preview. The changes provide users with clear instructions on how to verify access to the new model and integrate it into their workflow, ensuring they can leverage the latest features as they become available.

Highlights

• Gemini 3.1 Information Added: New documentation has been added to guide users on how to check for Gemini 3.1 Pro Preview availability and how to use it once accessible, including direct launch via the -m flag.
• Model Routing Clarification: The update clarifies that if Gemini 3.1 is available, it will be automatically included in model routing when 'Auto (Gemini 3)' is selected.

Changelog

• docs/get-started/gemini-3.md
  • Added a note detailing the rollout of Gemini 3.1 Pro Preview.
  • Included instructions on how to check for Gemini 3.1 availability using the /model command.
  • Provided guidance on using Gemini 3.1 with model routing and direct launch via the -m flag.
  • Linked to additional documentation on models and model routing.

Activity

• No human activity has been recorded on this pull request yet.

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-cli]

Hi @jkcinouye, 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]

Code Review

This pull request updates the documentation to include information about the Gemini 3.1 Pro Preview. The change is helpful, but I've identified an inconsistency in the command-line flag used in the example. The new documentation introduces -m, while other parts of the documentation consistently use --model. I've suggested a change to align them and prevent potential user confusion.

[github-actions]

Size Change: +483 B (0%)

Total Size: 24.5 MB

ℹ️ View Unchanged

Filename	Size	Change
./bundle/gemini.js	24.5 MB	+483 B (0%)
./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}