projectb-statusline

Configure CLI status lines using the host's supported schema and paths.

Updated May 28, 2023
One-click install
npx skills add https://github.com/steveulrich/ProjectB --skill projectb-statusline-steveulrich
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: projectb-statusline
Source: https://github.com/steveulrich/ProjectB/tree/main/.agents/skills/projectb-statusline
Command: npx skills add https://github.com/steveulrich/ProjectB --skill projectb-statusline-steveulrich

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Configuring a CLI status line requires knowing the exact configuration schema, file paths, and payload format of the specific host CLI, and applying the wrong schema (such as the legacy Cursor JSON format) to a different host like Codex produces broken or ignored settings. ## Core Features & Use Cases - Host Identification: Identifies the target CLI and resolves its supported status-line configuration through current host documentation rather than assuming a fixed schema. - Schema-Aware Configuration: Uses the host's actual schema and resolved paths, explicitly avoiding the legacy Cursor JSON schema for Codex tasks. - Legacy Cursor Reference: Provides a detailed reference for Cursor-compatible hosts covering the statusLine config fields, stdin JSON payload schema, ANSI rendering, and example scripts. - Use Case: When asked to set up a status line showing model name and context usage, the Skill first determines whether the host is Codex or a Cursor-compatible CLI, then applies the correct configuration format and paths. ## Quick Start Configure a status line for my CLI that shows the current model name and context window usage percentage.

Frequently Asked Questions about projectb-statusline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure a CLI status line?▼

First identify which CLI host you are using, then consult its current documentation for the supported status-line schema and config file paths. The configuration format differs between hosts, so the correct schema must be resolved per host.

How to set up a status line in Cursor CLI?▼

Add a statusLine entry with type "command" and a command path to ~/.cursor/cli-config.json. The command receives a JSON payload on stdin describing the session, and its stdout is rendered as the status line with ANSI color support.

Can I use the Cursor status line schema with Codex?▼

No, the legacy Cursor JSON schema must not be applied to Codex. Codex has its own supported configuration schema and paths, which should be resolved from current Codex host documentation before configuring a status line.

What data is available in the status line stdin payload?▼

The payload includes session_id, transcript_path, cwd, model id and display name, context window usage percentages, output style, and optional vim mode and worktree fields. Fields like session_name and vim are absent when not applicable.

Why is my status line command not updating?▼

If the command exits non-zero with empty stdout, the previous status text is kept. Commands that exceed the timeout or overlap with a new update are killed, so keep scripts fast and ensure they write to stdout.