claude-code - 💡(How to fix) Fix Include effortLevel in statusline stdin JSON [1 comments, 2 participants]

TL;DR

Add an optional effort_level field to the statusline stdin JSON to provide the accurate, per-invocation effort level value.

Guidance

• Review the current implementation of the statusline stdin JSON to determine the best approach for adding the effort_level field.
• Consider the cases where effort_level is not applicable (e.g., Haiku model) and decide whether to omit the field or set it to null.
• Update the statusline scripts to handle the new effort_level field and display it alongside the model name.
• Test the changes to ensure the effort_level value is accurately displayed and updated in real-time.

Example

{
  "model": {"display_name": "Opus 4.6"},
  "effort_level": "high",
  "context_window": "...",
  "rate_limits": "...",
  "cost": "..."
}

Notes

The proposed change requires updates to the statusline stdin JSON and the corresponding scripts that handle this data. The implementation details may vary depending on the specific requirements and constraints of the project.

Recommendation

Apply workaround: Add the effort_level field to the statusline stdin JSON as proposed, to provide accurate and up-to-date effort level information to statusline scripts.