fix(cli): support legacy onConfirm callback in ToolActionsContext#19369
fix(cli): support legacy onConfirm callback in ToolActionsContext#19369SandyTao520 merged 1 commit intomainfrom
Conversation
|
Hi @SandyTao520, 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! |
|
Hi there! Thank you for your contribution to Gemini CLI. To improve our contribution process and better track changes, we now require all pull requests to be associated with an existing issue, as announced in our recent discussion and as detailed in our CONTRIBUTING.md. This pull request is being closed because it is not currently linked to an issue. Once you have updated the description of this PR to link an issue (e.g., by adding How to link an issue: Thank you for your understanding and for being a part of our community! |
Summary of ChangesHello @SandyTao520, 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 addresses a critical bug that prevented legacy tool actions, particularly custom slash commands, from being confirmed correctly. By implementing a fallback mechanism to invoke local Highlights
Changelog
Activity
Using Gemini Code AssistThe 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
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 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
|
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
There was a problem hiding this comment.
Code Review
This pull request effectively addresses a bug where legacy tool confirmations were being ignored by adding a fallback to the onConfirm callback in ToolActionsContext. The logic is sound, and the addition of a unit test in ToolActionsContext.test.tsx is excellent for preventing regressions. I have one suggestion to improve the type safety of the new type guard function, which will make the code more robust.
62db876 to
235aab7
Compare
Fixes a bug where custom slash commands using legacy confirmations would hang because the local onConfirm callback was ignored in favor of MessageBus publishing.
235aab7 to
3da14b0
Compare
|
Size Change: +270 B (0%) Total Size: 24.5 MB ℹ️ View Unchanged
|
Summary
Fixes a bug where tool confirmations without a
correlationId(specifically custom slash commands) would hang because the localonConfirmcallback was ignored.Details
Custom commands using the legacy confirmation style rely on a local
onConfirmcallback instead of the newer MessageBus-based confirmation system.ToolActionsContext.tsxwas only handling MessageBus responses, causing these clicks to be dropped.Changes:
hasLegacyCallbacktype guard to safely check for the presence of theonConfirmcallback.confirmfunction inToolActionsContext.tsxto call the legacy callback as a fallback when nocorrelationIdis present.ToolActionsContext.test.tsxto verify the fix and prevent regressions.Related Issues
Reported in chat by user
dutidMKN7NY. Related to #18007How to Validate
Pre-Merge Checklist