Gemini CLI — User Demand Report

Week: 2026-W14 Generated: 2026-04-03 Issues analyzed: 59 (54 included) Need clusters: 10

Top 10 User Needs

Rising Needs

Category Breakdown

• Developer Experience: 4 clusters
• Reliability: 3 clusters
• Performance: 1 clusters
• Configuration: 1 clusters
• UI/UX: 1 clusters

All Need Clusters

1. Optimize Resource Usage and Performance

Users are experiencing excessive token consumption, memory leaks, infinite loops, and performance regressions that waste computational resources and increase costs. They want the system to be more efficient with tokens, memory, and processing during agent operations, particularly during extended thinking, waiting states, and tool execution. These issues cause degraded performance and unexpected resource exhaustion.

• Volume: 5 issues (5 open, 0 closed)
• Demand Score: 4.0
• Avg Reactions: 0 | Avg Comments: 0.8
• Example issues: #24600, #24593, #24589, #24584, #24536

2. CLI Reliability and UX Bug Fixes

Users are experiencing multiple reliability issues with the CLI tool including hanging on 'thinking' states, incorrect output display in non-interactive contexts, authentication dialog handling problems, and inconsistent keyboard shortcuts across platforms. These fixes address session management, input handling, and display rendering to improve overall CLI stability.

• Volume: 12 issues (9 open, 3 closed)
• Demand Score: 3.2
• Avg Reactions: 0.1 | Avg Comments: 2.3
• Example issues: #24605, #24597, #24591, #24574, #24570

3. Google AI Pro authentication and quota fixes

Users are experiencing authentication failures, incorrect error messages, and quota visibility issues when using Google AI Pro accounts. Issues include 403 PERMISSION_DENIED errors after successful OAuth, race conditions in the OIDC login flow, and inability to distinguish between personal vs workspace accounts. Developers need reliable account type detection, clearer error messaging, and proper quota handling to effectively use the CLI.

• Volume: 8 issues (5 open, 3 closed)
• Demand Score: 2.5
• Avg Reactions: 0.5 | Avg Comments: 2.3
• Example issues: #24607, #24587, #24539, #24533, #24525

4. Graceful rate limit error handling

Users encountering HTTP 429 rate limit errors need the application to handle them gracefully, either through automatic retry logic with backoff or by providing clear, actionable error messages that explain why requests were blocked and when users can retry. This improves the developer experience and reduces frustration when hitting API limits.

• Volume: 2 issues (2 open, 0 closed)
• Demand Score: 2.0
• Avg Reactions: 0 | Avg Comments: 1
• Example issues: #24594, #24588

5. Bug Fixes and Quality Improvements

Users are reporting various bugs affecting core functionality, UI correctness, and data integrity. These include crashes when handling specific characters, infinite loops during MCP server connections, session persistence failures, and UI rendering issues in tables and sidebars. Addressing these issues will improve overall application stability and user experience.

• Volume: 11 issues (9 open, 2 closed)
• Demand Score: 1.5
• Avg Reactions: 0 | Avg Comments: 0.3
• Example issues: #24604, #24595, #24564, #24563, #24562

6. Agent Reliability and Stability Fixes

Users are experiencing multiple reliability issues with the agent, including unresponsiveness after updates, endless thinking loops, unhandled crashes during file operations, and failure to properly execute halt commands. These stability problems significantly impact workflow continuity and user trust in the agent's ability to complete tasks reliably.

• Volume: 5 issues (2 open, 3 closed)
• Demand Score: 1.5
• Avg Reactions: 0 | Avg Comments: 1.8
• Example issues: #24581, #24576, #24541, #24516, #24515

7. Fix editor bugs causing crashes and corruption

Users are experiencing multiple critical bugs in the editor and file handling systems that cause unexpected behavior, crashes, and data corruption. These issues range from minor UX problems like scroll reset when viewing diffs to serious issues like file content corruption on Windows. Fixing these bugs is essential for maintaining user trust and preventing data loss.

• Volume: 3 issues (2 open, 1 closed)
• Demand Score: 1.2
• Avg Reactions: 0 | Avg Comments: 2
• Example issues: #24602, #24580, #24560

8. Fix and enhance gemini extensions functionality

These issues relate to improving the gemini extensions system by fixing directory resolution bugs, enabling third-party extension submissions, and resolving missing files in the NPM bundle. Users need a reliable and extensible system for managing role-based SDLC skills through the CLI.

• Volume: 3 issues (3 open, 0 closed)
• Demand Score: 1.0
• Avg Reactions: 0 | Avg Comments: 0.3
• Example issues: #24572, #24543, #24534

9. Configuration Settings and Defaults

Users want settings to work as intended and have better default behaviors. One issue is that the 'inlineThinkingMode' setting is being ignored, causing unwanted thinking tokens to appear. Another request is to change the default value of 'Compact Tool Output' to be enabled by default, improving the user experience out of the box.

• Volume: 2 issues (2 open, 0 closed)
• Demand Score: 1.0
• Avg Reactions: 0 | Avg Comments: 0.5
• Example issues: #24583, #24509

10. Improve UI Information Display and Readability

Users want improvements to the interface including fixing missing information displays (like email and tier), adding persistent navigation elements (sticky header), and improving output readability with concise summaries. These enhancements would make the application more intuitive and reduce visual clutter while maintaining access to important context.

• Volume: 3 issues (3 open, 0 closed)
• Demand Score: 0.0
• Avg Reactions: 0 | Avg Comments: 0
• Example issues: #24601, #24553, #24507

This report analyzes public GitHub issues only. It represents a signal from public issue discussions, not the full user base.

Generated by ReadYourUsers