Preflight Checklist

• I have searched existing requests and this feature hasn't been requested yet
• This is a single feature request (not multiple features)

Problem Statement

Tool Output Verbosity Creates Visual Noise During Multi-Step Workflows

Problem

When executing tool calls with large string parameters (comments, batch operations, documentation updates), the CLI displays full parameter values, creating excessive visual noise that obscures the actual work being done.

Workaround

None currently available. Users must scroll past verbose output to see results.

Related Issues

• Feature: Option to suppress 'Async hook X completed' status messages #21761 (Suppress async hook messages - similar goal of reducing output noise)

Environment

• Claude Code CLI v2.1.25
• Multiple MCP servers (issue tracking, database operations)
• Platform: Linux (Docker)

Labels: enhancement, ux, cli

Proposed Solution

Option 1: Compact Display (Preferred)

✓ linear:create_comment (PROJ-123, 847 chars)
✓ mcp_server:batch_operation (5 items)
✓ linear:update_issue (PROJ-123 → Done)

Alternative Solutions

Option 2: Verbosity Setting

json
// .claude/settings.json
{
"tool_output_verbosity": "summary" // "summary" | "full" | "minimal"
}

Option 3: Collapsible Sections

• Collapse tool parameters by default
• Expand with ctrl+o (already works for responses)
• Show summary line when collapsed

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case Example

Current Behavior

Example from a typical workflow:

● linear - create_comment (MCP)(issueId: "PROJ-123", body: "## Completion Verification\n\nStatus: Complete\n\n###
Results\n\nVerified the following:\n- ✅ Code committed and pushed\n- ✅ Tests passing\n- ✅ Deployment successful\n- ✅
Feature accessible\n\n### Evidence\n\n[detailed logs and verification steps spanning multiple paragraphs]...
[continues for 800+ characters]

This makes it difficult to:

• Scan what actions were taken
• Understand workflow progress at a glance
• Review conversation history efficiently

A typical workflow might involve:

1. Posting a detailed status comment to an issue tracker (500+ chars)
2. Recording multiple audit trail entries (200+ chars each)
3. Posting a completion comment with evidence (800+ chars)
4. Updating issue metadata

Each step generates large parameter displays that fill the screen, making it hard to follow the actual workflow progress.

Additional Context

High impact for:

• Multi-step verification workflows
• Batch operations (bulk updates, multiple recordings)
• Documentation workflows (creating/updating issue comments)
• Any workflow with repeated tool calls
• Audit trail generation