-
Notifications
You must be signed in to change notification settings - Fork 13k
[Feature Request] Suppress or control verbose tool output (JSON) in the CLI UI #14569
Copy link
Copy link
Closed
Copy link
Labels
area/coreIssues related to User Interface, OS Support, Core FunctionalityIssues related to User Interface, OS Support, Core Functionalitykind/enhancementpriority/p2Important but can be addressed in a future release.Important but can be addressed in a future release.status/bot-triagedworkstream-rollupLabel used to tag epics and features that are associated with one of the three primary workstreamsLabel used to tag epics and features that are associated with one of the three primary workstreams🔒 maintainer only⛔ Do not contribute. Internal roadmap item.⛔ Do not contribute. Internal roadmap item.
Metadata
Metadata
Assignees
Labels
area/coreIssues related to User Interface, OS Support, Core FunctionalityIssues related to User Interface, OS Support, Core Functionalitykind/enhancementpriority/p2Important but can be addressed in a future release.Important but can be addressed in a future release.status/bot-triagedworkstream-rollupLabel used to tag epics and features that are associated with one of the three primary workstreamsLabel used to tag epics and features that are associated with one of the three primary workstreams🔒 maintainer only⛔ Do not contribute. Internal roadmap item.⛔ Do not contribute. Internal roadmap item.
Type
Fields
Give feedbackNo fields configured for Feature.
Projects
Status
Closed
What would you like to be added?
When the AI uses tools that return large structured data (like
search_issuesorlist_filesreturning JSON), the raw JSON output is printed directly to the chat interface. This "clogs" the screen with pages of text, making it hard to read the AI's actual response.I would like the CLI to either:
tools.showOutput: falseor similar).Why is this needed?
Currently, simple queries like "find issues about X" result in massive JSON dumps that scroll critical context off the screen. This degrades the user experience significantly, even when the model provides a concise summary afterwards.
Additional context
The model itself cannot prevent this output from being displayed as it seems to be a function of the CLI's tool execution rendering logic.
Distinction from Related Issues:
I am aware of related issues such as #3904 and #12241, which focus primarily on hiding/suppressing MCP tool responses. This request is distinct and important because:
search_issues,list_files,run_shell_command), not just MCP-specific ones, as all can be equally verbose and disruptive.