claude-code - 💡(How to fix) Fix [Feature Request] Expose effortLevel in statusLine.command JSON payload [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#52096Fetched 2026-04-23 07:36:42
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Timeline (top)
labeled ×3commented ×1

Fix Action

Fix / Workaround

Description Please expose the current reasoning effort level (effortLevel) in the JSON payload piped to statusLine.command scripts, alongside the existing model/workspace/context_window fields. The current workaround requires reading ~/.claude/settings.json out-of-band. Thank you for the great product!

RAW_BUFFERClick to expand / collapse

Description Please expose the current reasoning effort level (effortLevel) in the JSON payload piped to statusLine.command scripts, alongside the existing model/workspace/context_window fields. The current workaround requires reading ~/.claude/settings.json out-of-band. Thank you for the great product!

Environment Info

  • Platform: win32
  • Terminal: windows-terminal
  • Version: 2.1.117
  • Feedback ID: e45f2bc3-31b3-45c2-9bf9-878c9b5aea8c

extent analysis

TL;DR

Modify the JSON payload in the statusLine.command scripts to include the effortLevel field.

Guidance

  • Review the current implementation of statusLine.command scripts to identify where the JSON payload is constructed and modified.
  • Update the JSON payload construction to include the effortLevel field, potentially by reading it from the ~/.claude/settings.json file or another suitable source.
  • Verify that the updated JSON payload is correctly formatted and includes the required fields (model, workspace, context_window, and effortLevel).
  • Test the modified statusLine.command scripts to ensure the effortLevel field is correctly exposed and utilized.

Notes

The exact implementation details may vary depending on the specific codebase and scripting language used. This guidance assumes that the statusLine.command scripts have access to the required effortLevel information.

Recommendation

Apply workaround: Modify the statusLine.command scripts to include the effortLevel field in the JSON payload, as this is a targeted fix for the described issue.

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

claude-code - 💡(How to fix) Fix [Feature Request] Expose effortLevel in statusLine.command JSON payload [1 comments, 2 participants]