claude-code - 💡(How to fix) Fix [Feature Request] Expose reasoning effort and thinking level in statusLine stdin JSON [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#51982Fetched 2026-04-23 07:39:43
View on GitHub
Comments
0
Participants
1
Timeline
5
Reactions
1
Author
Participants
Timeline (top)
labeled ×3closed ×1subscribed ×1

Error Message

[{"error":"Error: NON-FATAL: Lock acquisition failed for /home/kim/.local/share/claude/versions/2.1.117 (expected in multi-process scenarios)\n at Dn$ (/$bunfs/root/src/entrypoints/cli.js:2756:2177)\n at tq6 (/$bunfs/root/src/entrypoints/cli.js:2756:1257)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-22T13:39:18.245Z"},{"error":"Error: Request was aborted.\n at makeRequest (/$bunfs/root/src/entrypoints/cli.js:50:3448)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-22T13:39:32.920Z"}]

Code Example

[{"error":"Error: NON-FATAL: Lock acquisition failed for /home/kim/.local/share/claude/versions/2.1.117 (expected in multi-process scenarios)\n    at Dn$ (/$bunfs/root/src/entrypoints/cli.js:2756:2177)\n    at tq6 (/$bunfs/root/src/entrypoints/cli.js:2756:1257)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-22T13:39:18.245Z"},{"error":"Error: Request was aborted.\n    at makeRequest (/$bunfs/root/src/entrypoints/cli.js:50:3448)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-22T13:39:32.920Z"}]
RAW_BUFFERClick to expand / collapse

Bug Description ▎ Feature request: expose reasoning effort (and thinking level) in statusLine stdin ▎ ▎ The statusLine command receives a JSON payload on stdin with model, context_window, rate_limits, etc., but not the current reasoning effort or thinking level. effortLevel exists in ▎ settings.json, but reading it from a statusLine script is unreliable for users who toggle effort mid-session or run many concurrent sessions — settings.json holds the persisted default, ▎ while session-scoped overrides live only in memory. ▎ ▎ Please add effort (and thinkingLevel if distinct) to the statusLine stdin JSON, reflecting the live session value. This would let users surface the current effort right next to the model ▎ name in their statusline.

Environment Info

  • Platform: linux
  • Terminal: ghostty
  • Version: 2.1.117
  • Feedback ID: c48a93c8-6e3d-44b9-a071-31df55a5793b

Errors

[{"error":"Error: NON-FATAL: Lock acquisition failed for /home/kim/.local/share/claude/versions/2.1.117 (expected in multi-process scenarios)\n    at Dn$ (/$bunfs/root/src/entrypoints/cli.js:2756:2177)\n    at tq6 (/$bunfs/root/src/entrypoints/cli.js:2756:1257)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-22T13:39:18.245Z"},{"error":"Error: Request was aborted.\n    at makeRequest (/$bunfs/root/src/entrypoints/cli.js:50:3448)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-22T13:39:32.920Z"}]

extent analysis

TL;DR

To address the issue, modify the statusLine command to include the current reasoning effort and thinking level in the JSON payload received on stdin.

Guidance

  • Review the settings.json file to understand how the effortLevel is persisted and how it differs from the live session value.
  • Investigate the cli.js file, specifically lines 2756:2177 and 50:3448, to understand the lock acquisition failure and request abortion errors.
  • Consider adding the current reasoning effort and thinking level to the statusLine stdin JSON payload, reflecting the live session value.
  • Verify that the statusLine command can access and include the live session values for effort and thinkingLevel in the JSON payload.

Example

No code snippet is provided as the issue lacks specific implementation details.

Notes

The provided errors may be unrelated to the feature request, but rather indicate issues with lock acquisition and request handling in the cli.js file.

Recommendation

Apply workaround: Modify the statusLine command to include the current reasoning effort and thinking level in the JSON payload, as this directly addresses the feature request and may not require a version upgrade.

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