[Feature Request] Expose reasoning effort and thinking level in statusLine stdin JSON

Resolved 💬 1 comment Opened Apr 22, 2026 by kimhanse Closed Apr 22, 2026

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"}]

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗