Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [DOCS] Status line docs outdated about context-low warning location [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#45481•Fetched 2026-04-09 08:04:25
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
coygeekcoygeek
Participants
coygeekcoygeek
Timeline (top)
labeled ×3closed ×1
RAW_BUFFERClick to expand / collapse

Documentation Type

Incorrect/outdated documentation

Documentation Location

https://code.claude.com/docs/en/statusline

Section/Topic

"Notifications share the status line row"

Current Documentation

The docs currently say:

Notifications share the status line row

  • System notifications like MCP server errors, auto-updates, and token warnings display on the right side of the same row as your status line
  • Enabling verbose mode adds a token counter to this area
  • On narrow terminals, these notifications may truncate your status line output

What's Wrong or Missing?

Claude Code v2.1.97 changed the context-low warning UI: it now shows as a transient footer notification instead of a persistent row item.

That makes the current status line documentation outdated. The page still tells users that token warnings display on the same row as the status line, which no longer matches the documented low-context warning behavior from the v2.1.97 changelog.

Users reading the status line docs to understand why their custom status line is being truncated or displaced can come away with the wrong mental model about where this warning appears.

Suggested Improvement

Update the "Notifications share the status line row" section to distinguish the context-low warning from notifications that still occupy the status line row.

Suggested minimum fix:

The context-low warning appears as a transient footer notification rather than a persistent status-line-row item.

If other notifications such as MCP server errors or auto-update notices still share the status line row, keep those documented separately so the page reflects the current UI accurately.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

PageContext
https://code.claude.com/docs/en/statuslineThe troubleshooting section still says token warnings display on the same row as the status line, which conflicts with the v2.1.97 context-low warning UI change

Total scope: 1 page affected

Source: Changelog v2.1.97

Exact changelog entry:

Improved context-low warning to show as a transient footer notification instead of a persistent row

extent analysis

TL;DR

Update the "Notifications share the status line row" section in the documentation to reflect the changed behavior of context-low warnings in Claude Code v2.1.97.

Guidance

  • Review the current documentation on the status line and identify all instances where it mentions token warnings displaying on the same row as the status line.
  • Update these instances to reflect that context-low warnings now appear as transient footer notifications, as per the v2.1.97 changelog.
  • Ensure that other notifications, such as MCP server errors or auto-update notices, are documented separately if they still share the status line row.
  • Verify the changes by checking the affected page (https://code.claude.com/docs/en/statusline) to ensure the documentation accurately reflects the current UI.

Example

A suggested minimum fix could be adding the following sentence to the documentation: "The context-low warning appears as a transient footer notification rather than a persistent status-line-row item."

Notes

The fix only applies to the specific page mentioned (https://code.claude.com/docs/en/statusline) and is based on the changelog entry for v2.1.97.

Recommendation

Apply workaround: Update the documentation to reflect the changed UI behavior, as this will help users understand the feature correctly and mitigate the issue of outdated documentation.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#ssr#installation#API versioning#request timeout

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING