fix(core): update telemetry token count after session resume

[psinha40898]

Summary

resume should emit event in order to change lastPromptToken count which re renders ContextUsageDisplay

Details

Related Issues

Fixes #15486

How to Validate

main
paste a long file in your workspace like the text of a novel as longfile.txt
input gemini cli
"scan @longfile.txt"
see context percent go down
restart gemini cli
see context is 100%
resume previous chat
notice context still 100% until you send msg

this pr
paste a long file in your workspace like the text of a novel as longfile.txt
input gemini cli
"scan @longfile.txt"
see context percent go down
restart gemini cli
see context is 100%
resume previous chat
notice context goes down to what it was

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 @psinha40898, 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 resolves an issue where the ContextUsageDisplay was not accurately reflecting the lastPromptToken count after a chat session was resumed. By explicitly invoking the telemetry token count update method upon session resumption, the system now correctly refreshes and displays the token usage, ensuring data consistency and an accurate user experience.

Highlights

• Telemetry Token Count Update: Ensures that the telemetry token count is correctly updated when a chat session is resumed, addressing an issue where the lastPromptToken was not being refreshed, which impacted the ContextUsageDisplay.

🧠 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. ↩

[gemini-code-assist]

Code Review

This pull request introduces a fix to update the telemetry token count when a chat session is resumed. The change adds a call to updateTelemetryTokenCount within the resumeChat method, ensuring that the UI is correctly updated with the token count from the resumed session's history. This makes the behavior consistent with other session initialization methods like initialize and resetChat. The change is correct and effectively resolves the described issue.