[FEATURE] Feature Request: Allow configuration to prevent auto-collapsing of long Bash outputs

Preflight Checklist

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

Problem Statement

Problem

When executing Bash commands that generate long outputs (>200-300 lines), Claude Code automatically collapses the output,
requiring users to press Control+O to expand and view the full results.

## Current Behavior

• Long Bash outputs are automatically collapsed
• User must manually expand with Control+O to see full content
• No configuration option to disable this behavior

## Expected/Desired Behavior
Users should have the option to:

1. Configure the line threshold before auto-collapsing (or disable it entirely)
2. See full outputs directly without manual expansion for specific commands
3. Perhaps a setting like "bash.autoCollapseThreshold": 1000 in settings

## Use Case
I have a Python script that analyzes stock options data and outputs ~350 lines of formatted analysis (tables, charts,
metrics). The workflow involves:

• Running analysis multiple times per day
• Reviewing full output immediately each time
• Currently requiring Control+O every single execution

Having to expand outputs manually on every run adds friction to an otherwise smooth workflow.

## Suggested Solution
Add a configuration option in Claude Code settings:
```json
{
"bash.autoCollapseThreshold": 1000, // or -1 to disable
"bash.alwaysExpand": false
}

This would give users control over when outputs collapse, improving workflows for data analysis, logging, testing, and
other use cases with long outputs.

Thanks for considering this enhancement!

Proposed Solution

Add a configuration option in Claude Code settings to allow users to control when Bash outputs auto-collapse:

```json
{
"bash.autoCollapseThreshold": 1000, // Number of lines before collapsing, or -1 to disable
"bash.alwaysExpand": false // Always show full output without collapsing
}

This would give users control over the auto-collapse behavior, improving workflows for data analysis, logging, testing,
and other use cases with long outputs.

Alternative: Add a per-command flag or comment syntax like # @no-collapse to prevent specific commands from being
collapsed.

Alternative Solutions

_No response_

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_