claude-code - 💡(How to fix) Fix Expose active skills and running subagents in statusline JSON data [2 comments, 2 participants]

TL;DR

To address the limitation, add active_skill and subagents fields to the statusline JSON payload to provide visibility into the active skill and running subagents.

Guidance

• Review the proposed solution to add active_skill and subagents fields to the statusline JSON payload to determine if it meets the requirements.
• Consider the implications of adding these new fields on existing custom statuslines and their potential impact on user experience.
• Evaluate the proposed JSON structure for active_skill and subagents to ensure it is consistent with the existing statusline API.
• Assess the potential need for additional error handling or edge cases, such as when no skill is active or no subagents are running.

Example

{
  "active_skill": {
    "name": "craft-site"
  },
  "subagents": [
    { "name": "craft-planner", "status": "running" },
    { "name": "Explore", "status": "running" }
  ]
}

This example illustrates the proposed JSON structure for the new fields.

Notes

The proposed solution assumes that the statusline API can be modified to include the new fields. However, the issue does not provide information on the underlying implementation or potential constraints that may affect the feasibility of this solution.

Recommendation

Apply workaround: Add the proposed active_skill and subagents fields to the statusline JSON payload, as it provides a clear and structured approach to addressing the limitation.