gemini-cli - ✅(Solved) Fix A large number of logs leads to inefficiency in troubleshooting and affects scrolling performance [1 pull requests, 1 participants]

Official PRs (…)
ON THIS PAGE

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
google-gemini/gemini-cli#25439Fetched 2026-04-16 07:06:31
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
Participants
Timeline (top)
labeled ×2cross-referenced ×1issue_type_added ×1

Fix Action

Fixed

PR fix notes

PR #25352: fix(cli): Massive logs cause scrolling lag and inefficient positioning

Description (problem / solution / changelog)

Summary

Add search and level-based filtering to the debug console so users can narrow console output faster when troubleshooting. This improves both the CLI debug console experience and the devtools client by making high-volume logs easier to inspect. @Samee24

录屏 2026-04-13 16-58-32.webm

录屏 2026-04-13 16-05-36.webm

Details

  • Adds console log filtering by level (All, Log, Info, Warn, Error, Debug) and free-text search in the devtools client.
  • Introduces reusable filtering helpers and test coverage for count calculation, level filtering, text filtering, combined filters, and empty-result behavior.
  • Extends console message data with stable id support to improve list rendering and filtering behavior.
  • Adds theme support for per-log-level colors across CLI themes, semantic tokens, and custom theme configuration.
  • Prevents IDE context detail from being triggered while the debug console is open, avoiding shortcut conflicts during debugging.
  • Updates CLI UI tests and snapshots to cover the new debug console behavior and theme changes.

Related Issues

https://github.com/google-gemini/gemini-cli/issues/25439

How to Validate

  1. Run the relevant test suites:
    • npm test -- packages/devtools/client/src/App.test.ts
    • npm test -- packages/cli/src/ui/components/DetailedMessagesDisplay.test.tsx
    • npm test -- packages/cli/src/ui/hooks/useConsoleMessages.test.tsx
  2. Start the devtools client and open the console view.
  3. Verify level filter buttons show counts for each log type and correctly filter displayed logs.
  4. Enter search text and confirm matching is case-insensitive and trims surrounding whitespace.
  5. Combine a level filter with search text and confirm only matching logs remain.
  6. Clear filters and confirm the full log list returns.
  7. In CLI debug console flow, verify F12 opens error/debug details and F4 does not trigger IDE context detail while the debug console is open.
  8. Optionally switch themes or use a custom theme and confirm log levels render with distinct colors.

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

Changed files

  • packages/cli/src/ui/AppContainer.test.tsx (modified, +16/-0)
  • packages/cli/src/ui/AppContainer.tsx (modified, +1/-0)
  • packages/cli/src/ui/components/ColorsDisplay.test.tsx (modified, +14/-0)
  • packages/cli/src/ui/components/Composer.test.tsx (modified, +26/-1)
  • packages/cli/src/ui/components/Composer.tsx (modified, +7/-0)
  • packages/cli/src/ui/components/DetailedMessagesDisplay.test.tsx (modified, +399/-21)
  • packages/cli/src/ui/components/DetailedMessagesDisplay.tsx (modified, +279/-49)
  • packages/cli/src/ui/components/Header.test.tsx (modified, +7/-0)
  • packages/cli/src/ui/components/__snapshots__/DetailedMessagesDisplay.test.tsx.snap (modified, +33/-8)
  • packages/cli/src/ui/components/__snapshots__/ThemeDialog.test.tsx.snap (modified, +10/-0)
  • packages/cli/src/ui/components/shared/TextInput.tsx (modified, +6/-1)
  • packages/cli/src/ui/hooks/useConsoleMessages.test.tsx (modified, +27/-10)
  • packages/cli/src/ui/hooks/useConsoleMessages.ts (modified, +7/-2)
  • packages/cli/src/ui/semantic-colors.ts (modified, +3/-0)
  • packages/cli/src/ui/themes/builtin/dark/solarized-dark.ts (modified, +7/-0)
  • packages/cli/src/ui/themes/builtin/light/solarized-light.ts (modified, +7/-0)
  • packages/cli/src/ui/themes/builtin/no-color.ts (modified, +7/-0)
  • packages/cli/src/ui/themes/semantic-tokens.ts (modified, +21/-0)
  • packages/cli/src/ui/themes/theme-manager.ts (modified, +7/-0)
  • packages/cli/src/ui/themes/theme.ts (modified, +14/-0)
  • packages/cli/src/ui/types.ts (modified, +1/-0)
  • packages/core/src/config/config.ts (modified, +7/-0)
  • packages/devtools/client/src/App.test.ts (added, +65/-0)
  • packages/devtools/client/src/App.tsx (modified, +206/-15)
RAW_BUFFERClick to expand / collapse

What would you like to be added?

A large number of logs leads to inefficiency in troubleshooting and affects scrolling performance

Why is this needed?

Provide log classification search function

Additional context

No response

extent analysis

TL;DR

Implementing a log classification search function can help mitigate the issue of a large number of logs affecting troubleshooting efficiency and scrolling performance.

Guidance

  • Consider categorizing logs based on severity, component, or timestamp to enable more targeted searches.
  • Develop a search function that allows users to filter logs by specific keywords or categories.
  • Evaluate existing logging frameworks or libraries that support log classification and search functionality.
  • Assess the current logging infrastructure to determine the best approach for integrating a log classification search function.

Example

No specific code example can be provided without more context, but a basic log search function might involve using a data structure like a dictionary or a database to store and query logs based on their classification.

Notes

The effectiveness of the solution depends on the specific logging infrastructure and requirements of the application. More information about the current logging setup and the desired search functionality would be necessary for a more detailed solution.

Recommendation

Apply workaround: Implement a basic log classification and search function to improve troubleshooting efficiency, as the exact requirements and infrastructure details are not provided.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING