chore(ui): remove outdated tip about model routing

[sehoon38]

Summary

This PR removes the outdated tip about "Enable model routing based on complexity" from the CLI tips list.

Details

The model routing is no longer configurable from /settings, but is automatically applied if one uses Auto mode.

Related Issues

Related to #19225

How to Validate

1. Run npm test -w packages/cli to ensure no tests are broken.
2. Verify that the tip no longer appears in the list of informative tips.

Pre-Merge Checklist

• Updated relevant documentation and README (if needed)
• Added/updated tests (if needed) - Verified existing tests pass.
• Noted breaking changes (if any)
• Validated on required platforms/methods:
  • MacOS
    • npm run

[gemini-code-assist]

Summary of Changes

Hello @sehoon38, 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 maintaining the relevance and accuracy of the CLI's user-facing information. It specifically targets and removes a tip that is no longer applicable, ensuring that the guidance provided to users remains up-to-date and helpful. This cleanup contributes to a more streamlined and less confusing experience for anyone interacting with the CLI.

Highlights

• Outdated Tip Removal: The pull request removes an outdated tip regarding 'Enable model routing based on complexity' from the CLI's informative tips list.
• Improved User Experience: By removing irrelevant information, this change ensures that users are presented with current and useful tips, enhancing the overall user experience of the CLI.

Changelog

• packages/cli/src/ui/constants/tips.ts
  • Removed the 'Enable model routing based on complexity' entry from the INFORMATIVE_TIPS array.

Activity

• The author has updated relevant documentation and READMEs where needed.
• Existing tests have been verified to pass, indicating no regressions.
• The changes have been validated on MacOS using 'npm run'.

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 @sehoon38, 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 removes an outdated tip regarding model routing. The change is a simple line removal from a list of strings and is consistent with the pull request's goal of cleaning up outdated user-facing information. The modification is correct and I see no issues with it.

[github-actions]

Size Change: -66 B (0%)

Total Size: 24.4 MB

ℹ️ View Unchanged

Filename	Size	Change
./bundle/gemini.js	24.4 MB	-66 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}