claude-code - 💡(How to fix) Fix [Feature Request] Expose current effort level in statusline JSON and environment variables [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#49630Fetched 2026-04-17 08:35:44
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
Participants
Timeline (top)
labeled ×4

Fix Action

Fix / Workaround

Workaround today: scanning /proc/<pid>/cmdline for --effort, which only catches launch-time value.

Code Example

[]
RAW_BUFFERClick to expand / collapse

Bug Description I can't invoke /feedback myself — it's an interactive built-in you have to run. Type ! /feedback or just /feedback in your prompt and paste this:

---Expose current effort level in statusline JSON / env

The new /effort selector (low/medium/high/xhigh/max/auto) has no way to be read from a statusline script or hook. Statusline JSON input has no effort field, no CLAUDE_EFFORT env var is set, and mid-session /effort changes don't touch --effort cmdline args or settings.json.

Request: add effort (or reasoningEffort) to the statusline JSON input, and/or expose it via env var to hooks. Would let statuslines display the active effort and react to mid-session changes.

Workaround today: scanning /proc/<pid>/cmdline for --effort, which only catches launch-time value.

Environment Info

  • Platform: linux
  • Terminal: kitty
  • Version: 2.1.112
  • Feedback ID: 431904b9-2415-423f-8dd4-990822ba89f6

Errors

[]

extent analysis

TL;DR

Add the effort level to the statusline JSON input or expose it via an environment variable to allow statuslines to display the active effort and react to mid-session changes.

Guidance

  • The current workaround of scanning /proc/<pid>/cmdline for --effort only catches the launch-time value, which may not reflect mid-session changes.
  • To improve this, consider adding an effort field to the statusline JSON input, similar to other fields that are already exposed.
  • Alternatively, exposing the effort level via an environment variable, such as CLAUDE_EFFORT, could provide a more straightforward way for hooks to access this information.
  • Investigate the feasibility of updating the statusline JSON input or adding a new environment variable in the current version (2.1.112) to address this limitation.

Example

No code example is provided as the issue does not contain sufficient information about the implementation details.

Notes

The issue highlights a limitation in the current implementation, where the effort level is not easily accessible to statusline scripts or hooks. The suggested workarounds or fixes aim to address this gap.

Recommendation

Apply workaround: Add the effort level to the statusline JSON input or expose it via an environment variable, as this would provide a more reliable way to access the current effort level and react to changes.

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