Issue Station
Sign In
Tools hereToolbox

gemini-cli - 💡(How to fix) Fix Feedback: Code Output Formatting in CLI Environments

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…
RAW_BUFFERClick to expand / collapse

What would you like to be added?

Issue: When Gemini generates commands or code blocks for CLI usage, it often wraps them in numbered lists or includes step numbers directly next to the code.

Impact: This creates a poor user experience for CLI developers. When copying commands from the terminal or CLI interface, the numbers (1., 2., 3., etc.) get copied along with the code. This forces the user to manually edit and delete the numbers before the code can be executed or pasted into configuration files.

▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄

Why is this needed?

Suggestion: Please train the model or adjust the system prompt to never use numbered lists when providing terminal commands, scripts, or raw configuration files. Code blocks should be provided as pure text blocks to allow for seamless copy-pasting.

Additional context

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