[BUG] Verbose setting silently affects status line area — unclear, undocumented behavior

Resolved 💬 4 comments Opened Jan 31, 2026 by beastyrabbit Closed Mar 1, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

The verbose configuration option (toggled via /config → "Verbose output") secretly controls whether current: X.X.X · latest: X.X.X version information is rendered in the status line area. This is unexpected because:

  1. "Verbose output" doesn't suggest status line changes. The setting name implies more detailed logging/debug output, not UI layout changes in the status bar.
  2. It conflicts with custom status lines. Users who configure a custom statusLine command (e.g. ccstatusline) get an extra version line they didn't configure and can't trace back to the verbose setting without reading source code.
  3. There's no documentation connecting the two. Nothing in the /config menu description or docs indicates that verbose affects the status line area.
  4. Showing identical versions is noisy. When current and latest are the same, displaying current: 2.1.27 · latest: 2.1.27 adds no value — it should be hidden or show "up to date".
  5. No link to changelog. When there is a new version available, the display doesn't link to release notes so users can't see what changed.

What Should Happen?

  • The version display should have its own dedicated toggle (e.g. showVersionInStatusLine), or the /config description for "Verbose output" should clearly state it affects the status line.
  • When versions match, hide the line or show a simple "up to date" indicator.
  • When an update is available, link to the release notes / changelog.

Error Messages/Logs

Steps to Reproduce

  1. Enable verbose output via /config → "Verbose output" → true
  2. Configure a custom statusLine command in ~/.claude/settings.json (e.g. bunx -y ccstatusline@latest)
  3. Observe the current: X.X.X · latest: X.X.X line appearing in the status area below the custom statusline
  4. Note there is no indication anywhere that "Verbose output" controls this — users must read the Claude Code source to discover the connection

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.27

Platform

Anthropic API

Operating System

Other Linux

Terminal/Shell

Other

Additional Information

Running Arch Linux with Kitty terminal. The verbose setting also shows full file paths instead of relative ones in tool output, but the status line effect is the most confusing part since it looks like it's coming from the custom statusLine command.

View original on GitHub ↗

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