gemini-cli - 💡(How to fix) Fix Feature Request: Implementation of /feedback Slash Command [1 participants]

What did you expect to happen?

The current Gemini CLI implements a /bug command for reporting technical failures. However, it lacks a dedicated /feedback command for qualitative user experience telemetry and feature suggestions.

In a rapid "build-and-ship" ecosystem, the absence of a direct feedback loop within the terminal interface creates a friction point for power users who want to influence the product's architectural direction without leaving their workflow.

Proposed Solution

Implement a /feedback slash command that allows users to submit structured qualitative data directly to the product team. Architectural Logic & ROI

• Reduced Friction: Users are most likely to provide insightful feedback during their session. Forcing them to navigate to a browser/GitHub UI creates a drop-off in telemetry quality and quantity.

• User Hope & Engagement: Providing a /feedback command gives the user base the "hope" that the product is evolving based on direct input, fostering a more committed community of developers.

• Categorization: The command could support optional flags (e.g., /feedback --ux, /feedback --feature) to assist Google in triaging input.

Desired Behavior

• User types /feedback "The context window management for K8s manifests needs improvement".
• The CLI confirms receipt: > Feedback received. Thank you for helping us architect a better Gemini.
• Data is sent to the official telemetry endpoint for the Gemini CLI team.

Client information

• CLI Version: 0.39.1
• Git Commit: 4d73f3413
• Session ID: 2ea780ea-0461-4b4a-bae0-2bee1d6c1b99
• Operating System: darwin v25.2.1
• Sandbox Environment: no sandbox
• Model Version: auto-gemini-3
• Auth Type: oauth-personal
• Memory Usage: 107.2 MB
• Terminal Name: iTerm2 3.6.9
• Terminal Background: #edf0e1
• Kitty Keyboard Protocol: Supported

Login information

No response

Anything else we need to know?

No response