fix: move toasts location to left side

[jackwotherspoon]

Summary

This PR refactors the "toast" display logic (Ctrl+C/Ctrl+D exit prompts, warnings, etc.) out of StatusDisplay (right side of UI) and into a dedicated ToastDisplay component. It moves it to left side above prompt.

fix.toasts.mp4

Details

• Separation of Concerns: Moved toast-related logic from StatusDisplay.tsx to a new ToastDisplay.tsx.
• UI Refinement: In Composer.tsx, toasts are now prioritized and displayed in place of indicators (like th
  Approval Mode Indicator) when active, while keeping StatusDisplay (context) visible.
• Improved Testing:
  • Added ToastDisplay.test.tsx with comprehensive coverage for all toast states.
  • Updated Composer.test.tsx to verify that toasts correctly toggle visibility of other UI elements.

Related Issues

How to Validate

1. Run the new component tests:

   npm test -w @google/gemini-cli -- src/ui/components/ToastDisplay.test.tsx

2. Run the updated composer tests:

   npm test -w @google/gemini-cli -- src/ui/components/Composer.test.tsx

3. Manually trigger toasts in the CLI (e.g., press Ctrl+C once) and verify the "Press Ctrl+C again to exit"
   message appears in the footer area.

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

[gemini-cli]

Hi @jackwotherspoon, 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!

[gemini-cli]

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 Fixes #123 or Related to #123), it will be automatically reopened.

How to link an issue:
Add a keyword followed by the issue number (e.g., Fixes #123) in the description of your pull request. For more details on supported keywords and how linking works, please refer to the GitHub Documentation on linking pull requests to issues.

Thank you for your understanding and for being a part of our community!

[gemini-code-assist]

Summary of Changes

Hello @jackwotherspoon, 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 significantly refactors the user interface by isolating and relocating transient 'toast' messages. The primary goal is to enhance user experience by moving these critical prompts to a more prominent and consistent location on the left side of the screen, ensuring they are noticed without obscuring essential context. This change also cleans up the StatusDisplay component, making the codebase more modular and testable.

Highlights

• Refactored Toast Display Logic: The logic for displaying 'toast' messages (like Ctrl+C/D exit prompts, warnings, etc.) has been extracted from StatusDisplay into a new, dedicated ToastDisplay component, improving separation of concerns.
• UI Placement Change: Toast messages are now displayed on the left side of the UI, above the prompt, instead of their previous location on the right side within the StatusDisplay area.
• UI Prioritization: When a toast message is active, it now takes precedence and is displayed in place of other indicators (such as the Approval Mode Indicator), while the StatusDisplay (context) remains visible.
• Enhanced Testing: Comprehensive unit tests have been added for the new ToastDisplay component, and existing Composer tests were updated to verify the correct toggling and visibility of UI elements based on toast presence.

Changelog

• packages/cli/src/ui/components/Composer.test.tsx
  • Added mocks for StatusDisplay and ToastDisplay components.
  • Updated test descriptions to reflect the new display logic for status and toast components.
  • Modified tests to assert the presence of ToastDisplay and the absence of ApprovalModeIndicator when toasts are active.
• packages/cli/src/ui/components/Composer.tsx
  • Imported the new ToastDisplay component.
  • Introduced a hasToast boolean variable to determine if any toast message should be displayed.
  • Implemented conditional rendering to show ToastDisplay when hasToast is true, otherwise rendering other indicators.
• packages/cli/src/ui/components/StatusDisplay.test.tsx
  • Removed tests related to the display of Ctrl+C/D prompts, warning messages, hint messages, escape prompts, and queue error messages, as this logic has been moved to ToastDisplay.
• packages/cli/src/ui/components/StatusDisplay.tsx
  • Removed all conditional rendering logic for Ctrl+C/D prompts, warning messages, hint messages, escape prompts, and queue error messages.
• packages/cli/src/ui/components/ToastDisplay.test.tsx
  • Added a new test file for the ToastDisplay component.
  • Included comprehensive tests for rendering various toast types, including Ctrl+C/D prompts, warning/hint messages, escape prompts, and queue error messages.
• packages/cli/src/ui/components/ToastDisplay.tsx
  • Added a new component file, ToastDisplay, responsible for rendering all transient 'toast' messages.
  • Implemented logic to display Ctrl+C/D prompts, warning/hint messages, escape prompts, and queue error messages based on uiState.
• packages/cli/src/ui/components/snapshots/StatusDisplay.test.tsx.snap
  • Updated snapshot to remove entries corresponding to toast messages previously rendered by StatusDisplay.
• packages/cli/src/ui/components/snapshots/ToastDisplay.test.tsx.snap
  • Added a new snapshot file containing expected output for ToastDisplay component tests.

Activity

• The author, jackwotherspoon, created this pull request to address the refactoring and relocation of toast messages.
• The pull request description includes a detailed summary, specific implementation details, related issues, and validation steps.
• The author has completed the pre-merge checklist items for adding/updating tests and validating on MacOS via npm run.

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 refactors the toast notification logic into a dedicated ToastDisplay component, improving separation of concerns. However, it introduces a critical regression in Composer.tsx where the logic to determine if a toast should be shown (hasToast) uses an incorrect property (warningMessage instead of transientMessage). This leads to the suppression of all transient warnings, including critical security or safety information from the system or LLM safety filters, and also prevents hint messages from being displayed. This issue is also reflected in the updated test suite for Composer.tsx, which uses the same incorrect property, masking the bug.

[github-actions]

Size Change: +582 B (0%)

Total Size: 23.9 MB

ℹ️ View Unchanged

Filename	Size	Change
./bundle/gemini.js	23.9 MB	+582 B (0%)
./bundle/sandbox-macos-permissive-closed.sb	1.03 kB	0 B
./bundle/sandbox-macos-permissive-open.sb	890 B	0 B
./bundle/sandbox-macos-permissive-proxied.sb	1.31 kB	0 B
./bundle/sandbox-macos-restrictive-closed.sb	3.29 kB	0 B
./bundle/sandbox-macos-restrictive-open.sb	3.36 kB	0 B
./bundle/sandbox-macos-restrictive-proxied.sb	3.56 kB	0 B

_{compressed-size-action}

[jacob314]