[DOCS] Status line docs missing `effort.level` and `thinking.enabled` stdin fields

Resolved 💬 4 comments Opened Apr 24, 2026 by coygeek Closed Apr 29, 2026

Documentation Type

Incorrect/outdated documentation

Documentation Location

https://code.claude.com/docs/en/statusline

Section/Topic

"Available data" and "Full JSON schema" in the status line documentation

Current Documentation

The docs currently say:

Claude Code sends the following JSON fields to your script via stdin: | model.id, model.display_name | Current model identifier and display name | | cwd, workspace.current_dir | Current working directory. Both fields contain the same value; workspace.current_dir is preferred for consistency with workspace.project_dir. | | workspace.project_dir | Directory where Claude Code was launched, which may differ from cwd if the working directory changes during a session | ... | agent.name | Agent name when running with the --agent flag or agent settings configured |

It also says:

Your status line command receives this JSON structure via stdin: ``json { "cwd": "/current/working/directory", "session_id": "abc123...", "model": { "id": "claude-opus-4-6", "display_name": "Opus" }, ..., "agent": { "name": "security-reviewer" } } ``

The page does not document the newly added effort.level or thinking.enabled fields anywhere in the available-data table or JSON schema.

What's Wrong or Missing?

Changelog v2.1.119 says: "Status line: stdin JSON now includes effort.level and thinking.enabled".

The status line page presents the stdin payload as an explicit field list plus a full JSON schema, but both are missing these new fields. That makes the page outdated for users who want to show the current effort level or thinking state in a custom status line.

Suggested Improvement

Update https://code.claude.com/docs/en/statusline to document both new fields in the two places that describe the stdin payload:

  1. Add rows to the "Available data" table for:
  • effort.level — current effort level for the session/turn
  • thinking.enabled — whether thinking is currently enabled
  1. Add both fields to the "Full JSON schema" example.
  2. If either field can be absent or null in some situations, document that in the "Fields that may be absent" or "Fields that may be null" notes.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/statusline | Primary status line stdin field reference and JSON schema |

Total scope: 1 page affected

Source: Changelog v2.1.119

Exact changelog entry: Status line: stdin JSON now includes effort.level and thinking.enabled

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗