[FEATURE] Show full output by default in Bash mode

Resolved 💬 3 comments Opened Oct 1, 2025 by noughts Closed Jan 6, 2026

Problem Statement

When executing bash commands in Bash mode (e.g., !git status), only the first few lines of output are shown by default when verbose output is set to False. Users must press Ctrl+O each time to expand and view the full output, which is inconvenient for interactive command execution.

Proposed Solution

In Bash mode, command output should be displayed in full by default, regardless of the verbose output setting. Since users are explicitly running commands interactively with the ! prefix, it's natural to assume they want to see the complete results immediately.

The verbose output setting should continue to control the verbosity of Claude's tool usage (Read, Write, Edit, etc.), but Bash mode commands should always show full output.

Alternative Solutions

Currently, the workaround is to:

  • Press Ctrl+O after every Bash command to expand the output
  • Or enable verbose output globally, which also makes all other tool outputs more verbose

Priority

Medium - Would be very helpful

Feature Category

Interactive mode (TUI)

Use Case Example

Example scenario:

  1. User runs !git status to check modified files
  2. Currently, only the first few lines are shown with "... +N lines (ctrl+o to expand)"
  3. User must press Ctrl+O to see all modified files
  4. With this feature, all files would be immediately visible
  5. This would save time and improve the interactive Bash mode experience

Another example:

  1. User runs !git diff to review changes
  2. Currently needs to expand output manually every time
  3. With full output by default, can immediately review all changes

Additional Context

This feature request focuses specifically on Bash mode (commands prefixed with !) where users explicitly run shell commands interactively. The verbose output setting would still control the verbosity of Claude's automated tool usage.

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗