Skip to content

Conversation

@NguyenSiTrung
Copy link
Contributor

@NguyenSiTrung NguyenSiTrung commented Dec 24, 2025

Add support for parsing cachedContentTokenCount field in Gemini , Antigravity API responses.

This adds cached token tracking to:

  • parseGeminiCLIUsage
  • parseGeminiUsage
  • parseGeminiStreamUsage
  • parseGeminiCLIStreamUsage
  • parseAntigravityUsage
  • parseAntigravityStreamUsage

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @NguyenSiTrung, I'm Gemini Code Assist1! 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 introduces a new capability to accurately track cached content tokens within Gemini API responses. By incorporating the cachedContentTokenCount field into various usage parsing functions, the system can now provide a more comprehensive and precise accounting of token consumption, which is crucial for billing, resource management, and performance analysis.

Highlights

  • Gemini API Response Parsing: Added support for parsing the cachedContentTokenCount field from Gemini API responses, enhancing the detail of token usage tracking.
  • Expanded Token Tracking: Integrated the new cached token tracking into six existing usage parsing functions: parseGeminiCLIUsage, parseGeminiUsage, parseGeminiStreamUsage, parseGeminiCLIStreamUsage, parseAntigravityUsage, and parseAntigravityStreamUsage.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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.

@NguyenSiTrung NguyenSiTrung changed the title feat: add cached token parsing for Gemini API responses feat: add cached token parsing for Gemini , Antigravity API responses Dec 24, 2025
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request adds support for parsing cachedContentTokenCount from Gemini API responses across various usage parsing functions. The changes are correct and consistently applied. My main feedback is regarding code duplication. The logic for parsing usage details is now repeated in six different functions. I've left a comment suggesting a refactoring into a helper function to improve maintainability. This can be addressed in a follow-up PR.

@NguyenSiTrung
Copy link
Contributor Author

@hkfires , @luispater please help me review this . Thanks

@luispater luispater merged commit d502840 into router-for-me:dev Dec 24, 2025
2 checks passed
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.

2 participants