gemini-cli - 💡(How to fix) Fix Shell Command UI Redundancy [3 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

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#26763Fetched 2026-05-11 03:28:54
View on GitHub
Comments
3
Participants
3
Timeline
16
Reactions
0
Timeline (top)
labeled ×6commented ×3mentioned ×2subscribed ×2
RAW_BUFFERClick to expand / collapse

What happened?

Problem: The shell command confirmation prompt currently displays the raw terminal command twice (once in the title and once in the box), which creates unnecessary visual clutter and ignores the plain-English intent provided by the agent.

Suggested Improvement:

  1. Simplify Title: Change the prompt title to a generic "? Shell".
  2. Display Intent: Use the "description" parameter (the plain English explanation) as the primary content in the box.
  3. Technical Detail: Show the raw command as a secondary detail below the explanation.

Example of Desired UI:

? Shell ┌──────────────────────────────────────────────────────────────────────────────┐ │ Intent: Search for Jest and Vitest configuration files to identify the │ │ testing framework. │ └──────────────────────────────────────────────────────────────────────────────┘ Command: find . -name "jest.config." -o -name "vitest.config." ...

Allow execution of [find]?

  1. Allow once
  2. Allow for this session
  3. No, suggest changes

Affected Components:

  • packages/cli/src/components/ToolConfirmation.tsx (or similar Shell UI component)
  • Logic should prioritize args.description for the box content and fallback to args.command only if the description is missing.

What did you expect to happen?

To see clearer information on the shell commands. I don't need to see the exact command twice. I need to see the what the command will do, in plain english, followed by the terminal command.

<img width="939" height="218" alt="Image" src="https://github.com/user-attachments/assets/5c391b47-f9c6-44a9-aea9-782e5f0341d1" />

Client information

  • CLI Version: 0.41.2
  • Git Commit: b0c7a1722
  • Session ID: 36452362-4a62-43e5-8395-09f503b6e396
  • Operating System: darwin v24.10.0
  • Sandbox Environment: no sandbox
  • Model Version: auto-gemini-3
  • Auth Type: oauth-personal
  • Memory Usage: 117.5 MB
  • Terminal Name: Unknown
  • Terminal Background: #1e1e1e
  • Kitty Keyboard Protocol: Unsupported

Login information

No response

Anything else we need to know?

No response

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