box-factory-status-line

Status lines should display 3-4 glanceable data points with actionable insights rather than cosmetic details. Focus on cost awareness, context window usage, model visibility, git branch, session duration, and project orientation, updating every 300ms to stay current during development.

Include the current model name and accumulated cost to make spending visible during real-time sessions. This prevents budget overruns and helps you make informed decisions about model selection and session length.

Yes. Combine git branch awareness, context window management metrics, and session duration into a single status line. The Skill provides safe git command checks and data caching to keep script overhead minimal while rendering ANSI color and emoji support.

Cache data where possible and target a 300ms update cadence to avoid performance overhead. The Skill handles real-time JSON input rendering to stdout with minimal scripting requirements while maintaining glanceable output.

Status lines should prevent problems and remain scannable at a glance. Select 3-4 high-priority data points aligned with your workflow needs—cost, model, branch, or context—rather than attempting to show every available metric.