claude-code - 💡(How to fix) Fix Expose reasoning effort level in statusline hook input [1 comments, 2 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#45148Fetched 2026-04-09 08:12:06
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
Timeline (top)
labeled ×3commented ×1

Code Example

["context_window", "cost", "cwd", "exceeds_200k_tokens", "model", "output_style", "rate_limits", "session_id", "session_name", "transcript_path", "version", "workspace"]
RAW_BUFFERClick to expand / collapse

Feature Request

The statusline hook receives JSON input with fields like model, context_window, rate_limits, output_style, etc. However, it does not include the current reasoning effort level.

Use case: Displaying the effort level (e.g. "99%") next to the model name in the status bar so users can see at a glance what effort level is active.

Current available fields (from dumping the input JSON):

["context_window", "cost", "cwd", "exceeds_200k_tokens", "model", "output_style", "rate_limits", "session_id", "session_name", "transcript_path", "version", "workspace"]

Requested: Add a field like reasoning_effort or model.reasoning_effort containing the current effort level value (e.g. 99, "high", etc.).

The output_style field exists but only contains {"name": "default"} or {"name": "fast"}, which is not the reasoning effort level.

extent analysis

TL;DR

Add a reasoning_effort field to the JSON input received by the statusline hook to display the current effort level.

Guidance

  • Identify the source of the JSON input and modify it to include the reasoning_effort field with the current effort level value.
  • Verify that the reasoning_effort field is correctly populated by dumping the input JSON after the modification.
  • Consider adding error handling to ensure the statusline hook behaves correctly even if the reasoning_effort field is missing or empty.
  • Review the available fields in the input JSON to confirm that none of them already contain the reasoning effort level information.

Notes

The exact implementation details may vary depending on how the JSON input is generated and processed, which is not specified in the issue.

Recommendation

Apply workaround: Modify the JSON input to include the reasoning_effort field, as this is a targeted solution to the specific problem of displaying the effort level in the status bar.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING