claude-code - 💡(How to fix) Fix Feature: Expose effort level in statusline data [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#45003Fetched 2026-04-09 08:15:39
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
Timeline (top)
labeled ×2closed ×1commented ×1

Code Example

{
  "effort": "high",   // "low" | "medium" | "high" | "auto"
  ...
}
RAW_BUFFERClick to expand / collapse

Feature Request

Currently, the statusline command receives a JSON object via stdin, but it does not include the current effort level (set via /effort).

Requested change: Add an effort field to the statusline JSON data, for example:

{
  "effort": "high",   // "low" | "medium" | "high" | "auto"
  ...
}

Use case: Users who configure a custom statusline shell command want to display the current thinking effort level alongside model name and context usage. Without this field, there is no way to reflect effort level changes in the statusline.

Related: alwaysThinkingEnabled is already readable from settings.json, but effort level is session-only state and not persisted anywhere accessible to external scripts.

extent analysis

TL;DR

Add an effort field to the statusline JSON data to display the current thinking effort level.

Guidance

  • Review the current implementation of the statusline command to determine where the effort level is stored and how it can be accessed.
  • Modify the statusline command to include the effort level in the JSON object sent via stdin.
  • Consider adding error handling to ensure the effort level is correctly parsed and displayed in the statusline.
  • Investigate how to make the session-only state of the effort level accessible to external scripts, potentially through an API or environment variable.

Example

No code snippet is provided as the issue does not contain sufficient information about the current implementation.

Notes

The solution may require changes to the underlying architecture or API to make the effort level accessible to external scripts.

Recommendation

Apply workaround: Modify the statusline command to include the effort level in the JSON object, and investigate alternative methods to make the effort level accessible to external scripts, as upgrading to a fixed version is not mentioned in the 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