Skip to content

Conversation

@LyalinDotCom
Copy link
Contributor

@LyalinDotCom LyalinDotCom commented Feb 1, 2026

Summary
This PR improves inline thinking UX by rendering each thought as its own compact bubble and adding distinct summary/full settings for display.

Details

  • Thought Bubbles: Inline thinking now renders one bubble per thought event (no grouped counts), avoiding flicker-prone growth and making scroll behavior stable in both regular and alternate buffer modes.
  • Display Modes: Added separate UI settings for full vs summary inline thinking, with full taking precedence when both are enabled. The deprecated showInlineThinking toggle is hidden from the settings dialog but kept for backward compatibility.
  • Consistent Rendering: Propagated inline thinking display to alternate buffer/pending/quitting renders so behavior matches regular buffer mode.
  • Visual Cleanup: Removed the redundant “Thinking” header line; bubbles now display the subject/summary inline with a chat bubble icon.
  • Reusable UI: Added shared IconText component to handle emoji-with-fallback rendering, used by thinking bubbles.
  • Docs/Schema: Regenerated settings schema and docs to reflect the new settings.

Related Issues
Related to #15052

How to Validate

Thinking Subject (summary):

  1. Enable summary mode: /settings → Show Inline Thinking (Summary) = true (Full = false).
  2. Ask a question that emits thoughts; expect one compact bubble per thought with a 💬 icon (fallback ◆ if emoji isn’t supported).

Full Thinking Comments:

  1. Enable full mode: /settings → Show Inline Thinking (Full) = true.
  2. Expect bubbles to show full subject + description per thought.

For both, test in both regular and alternate buffer modes: bubbles should render consistently during streaming and in history.

Note:

a. In the future we should consolidate the setting to one setting that supports an enum of options
b. We should explore with actual thought summaries using Flash-lite

@LyalinDotCom LyalinDotCom requested review from a team as code owners February 1, 2026 00:27
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @LyalinDotCom, 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 significantly refines the user experience for displaying model thinking processes within the CLI. It transitions from a potentially disruptive display to a more organized, bubble-based interface. Users now have granular control over the level of detail shown for these thoughts, choosing between a concise summary or a comprehensive view, ensuring a more stable and visually clean interaction regardless of the terminal's operational mode.

Highlights

  • Enhanced Inline Thinking UI: Model thoughts are now displayed as individual, compact bubbles, improving readability and stability by preventing UI flicker and ensuring consistent scroll behavior.
  • Flexible Display Modes: Introduced distinct settings (ui.showInlineThinkingFull and ui.showInlineThinkingSummary) allowing users to choose between a full or summarized view of inline thoughts, with full mode taking precedence. The old ui.showInlineThinking is deprecated.
  • Consistent Cross-Buffer Rendering: Inline thinking display is now uniformly rendered across regular, alternate buffer, pending, and quitting modes.
  • Streamlined Visuals: The redundant "Thinking" header has been removed, and thought bubbles now present the subject/summary alongside a chat bubble icon (💬 or ◆ fallback).
  • Reusable Icon Component: A new IconText component was added to handle emoji rendering with a fallback mechanism for environments that don't support emojis.
  • Updated Configuration: The settings schema and documentation have been regenerated to reflect the new inline thinking settings.
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.

@chrstnb
Copy link
Collaborator

chrstnb commented Feb 1, 2026

Build failed: Build process failed (no specific link errors found). Check logs for details.

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 introduces a significant improvement to the user experience by rendering model thoughts as individual, compact bubbles with distinct 'summary' and 'full' display modes. The implementation is well-structured, encompassing new settings, UI components, and updated documentation. My review has identified two high-severity issues: one concerning a behavioral inconsistency with a deprecated setting, and another related to unsafe string truncation that could corrupt Unicode characters in the UI.

Comment on lines +96 to +103
if (description.length <= MAX_THOUGHT_SUMMARY_LENGTH) {
return { subject: description, description: '' };
}

const trimmed = description
.slice(0, MAX_THOUGHT_SUMMARY_LENGTH - 3)
.trimEnd();
return { subject: `${trimmed}...`, description: '' };
Copy link
Contributor

Choose a reason for hiding this comment

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

high

The summarizeThought function uses description.length and description.slice() for truncation. These methods operate on UTF-16 code units, which can lead to incorrect truncation and rendering of garbled text if the description contains multi-byte Unicode characters (like emojis or complex scripts). For example, an emoji consisting of a surrogate pair could be split in half. To handle Unicode correctly, you should operate on grapheme clusters, for instance by converting the string to an array using Array.from().

  const descriptionGraphemes = Array.from(description);
  if (descriptionGraphemes.length <= MAX_THOUGHT_SUMMARY_LENGTH) {
    return { subject: description, description: '' };
  }

  const trimmed = descriptionGraphemes
    .slice(0, MAX_THOUGHT_SUMMARY_LENGTH - 3)
    .join('')
    .trimEnd();
  return { subject: `${trimmed}...`, description: '' };
Comment on lines +24 to +26
if (ui?.showInlineThinking) {
return 'full';
}
Copy link
Contributor

Choose a reason for hiding this comment

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

high

The deprecated showInlineThinking setting is being mapped to 'full' mode. However, its description in settingsSchema.ts states it's for showing "model thinking summaries". This creates an inconsistency and changes the behavior for users who had this setting enabled, as they will now see full thoughts instead of summaries. For correct backward compatibility, it would be better to map this setting to 'summary' mode.

Suggested change
if (ui?.showInlineThinking) {
return 'full';
}
if (ui?.showInlineThinking) {
return 'summary';
}
@gemini-cli gemini-cli bot added the area/agent Issues related to Core Agent, Tools, Memory, Sub-Agents, Hooks, Agent Quality label Feb 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/agent Issues related to Core Agent, Tools, Memory, Sub-Agents, Hooks, Agent Quality

2 participants