Conversation
|
Hi @jacob314, 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! |
Summary of ChangesHello, 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 refines the terminal UI's shell height management to ensure accurate display and interaction. It introduces a more precise calculation for the available vertical space within the shell, accounting for UI elements like borders and headers. This change centralizes the PTY resizing logic, leading to a more robust and predictable user experience, especially when dealing with varying terminal sizes and shell outputs. 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
|
There was a problem hiding this comment.
Code Review
This pull request refactors the shell height calculation and PTY resizing logic, moving it from AppContainer to the more specialized ShellToolMessage component. This is a positive change for modularity. The introduction of a constant for UI overhead is also a good step towards fixing height miscalculations. However, I've identified a critical issue where inconsistent height calculation methods are used for the display component and the underlying PTY, which could lead to UI rendering bugs. My review includes a suggestion to resolve this inconsistency, aligning with our guidelines for maintaining layout consistency.
|
Size Change: +345 B (0%) Total Size: 26 MB ℹ️ View Unchanged
|
Summary
Shells are now rendered in a small box in Gemini CLI but we were still telling nodepty that they had
a much larger height making them unusable.
Details
Report the correct height and width and simplify so reporting is done from the UI components
themselves rather than AppContainer. The logic has been correctly relocated to
ShellToolMessage.tsx.Related Issues
Fixes #21494
How to Validate
Run vim, gemini or other interactive apps from with the embedded shells. Verify that the shell now
renders at the expected height and width.