Issue Station
Sign In
Tools hereToolbox

gemini-cli - 💡(How to fix) Fix Properly format markdown in the AskUser tool [1 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#25023•Fetched 2026-04-10 03:45:17
View on GitHub
Comments
0
Participants
1
Timeline
6
Reactions
0
Author
david-saintdavid-saint
Participants
david-saintdavid-saint
Timeline (top)
labeled ×3issue_type_added ×1parent_issue_added ×1unlabeled ×1

Code Example

> /about
╭───────────────────────────────────────────────────────────────╮
│                                                               │
│ About Gemini CLI                                              │
│                                                               │
│ CLI Version          0.37.0                                   │
│ Git Commit           352bbe149                                │
│ Model                Auto (Gemini 3)                          │
│ Sandbox              no sandbox                               │
│ OS                   darwin                                   │
│ Auth Method         Signed in with Google                     │
│                     (***********@gmail.com)                   │
│ Tier                 Gemini Code Assist in Google One AI Pro  │
│                                                               │
╰───────────────────────────────────────────────────────────────╯
RAW_BUFFERClick to expand / collapse

What happened?

When using Conductor to plan a track and it asks to review a spec, it uses the AskUser tool. The markdown is not properly formatted in the tool, so it's difficult to read/understand the spec.

<img width="1453" height="581" alt="Image" src="https://github.com/user-attachments/assets/60c71942-1f15-4ce8-82f6-b47853be9410" />

What did you expect to happen?

The markdown should be properly formatted, making it easy for the user to read and understand the contents of what they're being asked.

Client information

<details> <summary>Client Information</summary>

Run gemini to enter the interactive CLI, then run the /about command.

> /about
╭───────────────────────────────────────────────────────────────╮
│                                                               │
│ About Gemini CLI                                              │
│                                                               │
│ CLI Version          0.37.0                                   │
│ Git Commit           352bbe149                                │
│ Model                Auto (Gemini 3)                          │
│ Sandbox              no sandbox                               │
│ OS                   darwin                                   │
│ Auth Method         Signed in with Google                     │
│                     (***********@gmail.com)                   │
│ Tier                 Gemini Code Assist in Google One AI Pro  │
│                                                               │
╰───────────────────────────────────────────────────────────────╯
</details>

Login information

No response

Anything else we need to know?

No response

extent analysis

TL;DR

The issue can be addressed by improving the markdown formatting in the AskUser tool.

Guidance

  • Verify that the markdown text is correctly formatted before being passed to the AskUser tool.
  • Check the documentation of the AskUser tool to see if there are any options for enabling markdown formatting.
  • Test the AskUser tool with a simple markdown example to see if the issue is specific to the spec text or a general problem with markdown rendering.
  • Consider reaching out to the Conductor or AskUser tool support team for assistance with markdown formatting.

Notes

The provided information does not include details about the implementation of the AskUser tool or the Conductor, so it's difficult to provide a more specific solution.

Recommendation

Apply workaround: The best course of action would be to try and improve the markdown formatting in the AskUser tool, possibly by using a different markdown parser or renderer.

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…
#generation error#database connection#vector store#embedding generation#cache error

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

gemini-cli - 💡(How to fix) Fix Properly format markdown in the AskUser tool [1 participants]