[BUG] option to hide or minimize the built-in “status footer” (multi-line debug/cost panel)
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?
There's a persistent – but not very useful – notice at the bottom of the TUI. Could you add a setting/flag to suppress or minimize the built-in status footer?
Right now it occupies five terminal lines and shows what looks like debug/telemetry-style fields (e.g., total cost, durations, lines added/removed). This reduces usable vertical space and is distracting during normal use, demos, and screen recordings.
I’m also using a custom statusLine command via ~/.claude/settings.json, but this footer remains visible and appears not user-configurable.
What I’m referring to
The bottom panel that renders something like:
- model indicator (e.g.
[Sonnet]) - JSON-ish fields like
total_cost_usd,total_duration_ms,total_lines_added/removed - additional status (e.g. “accept edits on …”)
<img width="2871" height="1527" alt="Image" src="https://github.com/user-attachments/assets/0453a71c-5292-4760-9e92-446b295ad1ae" />
Expected
A way to disable the footer entirely, or switch it to a minimal mode (e.g., single-line), via:
~/.claude/settings.json(preferred), and/or- CLI flag (e.g.
--no-status-footer), and/or - env var (e.g.
CLAUDE_CODE_STATUS_FOOTER=0)
Actual
Footer is always displayed and (as far as I can tell) cannot be suppressed via settings.json or the custom statusLine feature.
Why this matters
- Consumes 4–6 lines of vertical space in smaller terminals
- Adds cognitive noise (“esoteric” stats) during normal development
- Can reveal cost/usage metrics in streams/screen shares unintentionally
- Users who already configure a custom status line likely want full control over terminal chrome
Suggested implementation (one option)
Add a setting like:
{
"ui": {
"statusFooter": "off" // or: "minimal" | "debug"
}
}
Or similar (statusFooter: false, etc.). Even “minimal vs debug” would be a big improvement.
Clarification: not the “Show PR status footer” setting
This request is not about the Config menu option “Show PR status footer”. Toggling “Show PR status footer” does not remove the multi-line status/debug footer shown in the screenshot.
In other words:
“Show PR status footer” appears to control PR-related UI only.
The always-on multi-line footer (cost/duration/lines-changed style metrics) seems to be a separate built-in UI element and currently has no user-facing toggle.
Thanks for considering—happy to test a preview build or provide more details if helpful.
What Should Happen?
- Users can turn off the built-in multi-line status footer entirely, so the terminal uses the full screen for the conversation/output.
- Alternatively (or additionally), users can switch the footer to a minimal/single-line mode that only shows high-signal info (e.g., model + brief state), without the JSON-like cost/duration/LOC counters.
- The setting should be configurable via ~/.claude/settings.json and/or a CLI flag/env var, and it should work even when statusLine is customized.
Error Messages/Logs
Steps to Reproduce
- Open a terminal with a modest height (e.g., ~30–40 rows) to make the impact obvious.
- Run Claude Code (e.g., claude).
- Start or continue any session and let it produce output (ask any question or run any command).
- Observe the bottom of the UI: a multi-line “status footer” appears and stays visible, showing cost/duration/lines-changed style fields.
- (Optional) Configure a custom status line in ~/.claude/settings.json, restart Claude Code, and observe that the built-in footer still appears and cannot be suppressed.
Claude Model
Sonnet (default)
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
2.1.70
Platform
Anthropic API
Operating System
Ubuntu/Debian Linux
Terminal/Shell
WSL (Windows Subsystem for Linux)
Additional Information
_No response_
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗