Skip to content

Conversation

@rlazo
Copy link
Collaborator

@rlazo rlazo commented Dec 11, 2025

Gemini 3 models support thinking levels, an alternative to thinking budgets. They are preset values that can use to limit how many tokens are dedicated to the thinking process.

The thinking documentation gives more details.

Gemini 2.5 series models and newer utilize a thinking process before
generating a response. Thinking levels are an alternative to thinking
budgets as they are preset values that Gemini 3 models can use to
limit how many tokens are dedicated to the thinking process.

The [thinking
documentation](https://firebase.google.com/docs/ai-logic/thinking)
gives more details.
@gemini-code-assist
Copy link
Contributor

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

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.

@github-actions
Copy link
Contributor

github-actions bot commented Dec 11, 2025

📝 PRs merging into main branch

Our main branch should always be in a releasable state. If you are working on a larger change, or if you don't want this change to see the light of the day just yet, consider using a feature branch first, and only merge into the main branch when the code complete and ready to be released.

@google-oss-bot
Copy link
Contributor

google-oss-bot commented Dec 11, 2025

@google-oss-bot
Copy link
Contributor

The public api surface has changed for the subproject firebase-ai:
error: Added method com.google.firebase.ai.type.ThinkingConfig.Builder.setThinkingLevel(com.google.firebase.ai.type.ThinkingLevel) [AddedMethod]
error: Added class com.google.firebase.ai.type.ThinkingLevel [AddedClass]

Please update the api.txt files for the subprojects being affected by this change by running ./gradlew ${subproject}:generateApiTxtFile. Also perform a major/minor bump accordingly.

@google-oss-bot
Copy link
Contributor

google-oss-bot commented Dec 11, 2025

@google-oss-bot
Copy link
Contributor

The public api surface has changed for the subproject firebase-ai:
error: Added method com.google.firebase.ai.type.ThinkingConfig.Builder.setThinkingLevel(com.google.firebase.ai.type.ThinkingLevel) [AddedMethod]
error: Added class com.google.firebase.ai.type.ThinkingLevel [AddedClass]

Please update the api.txt files for the subprojects being affected by this change by running ./gradlew ${subproject}:generateApiTxtFile. Also perform a major/minor bump accordingly.

@rlazo rlazo requested a review from thatfiredev December 16, 2025 10:29
rlazo and others added 2 commits December 17, 2025 18:02
We couldn't keep the implementation where it was originally placed due
to java compatibility issues. Custom setters, necessary to enable
checks in place when using the build pattern, are not compatible with
`@JvmField`s

Also, added tests.
@rlazo rlazo marked this pull request as ready for review December 22, 2025 21:44
Remove print statement from request text validation.
@rlazo rlazo requested a review from emilypgoogle December 22, 2025 22:05
@rlazo rlazo merged commit 6dab936 into main Dec 24, 2025
27 of 29 checks passed
@rlazo rlazo deleted the rl.thinking.level branch December 24, 2025 05:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants