statusline

Configure a custom command-based status line for the Cursor CLI prompt.

Updated Oct 15, 2019
One-click install
npx skills add https://github.com/kkkaoru/dotfiles --skill statusline-kkkaoru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: statusline
Source: https://github.com/kkkaoru/dotfiles/tree/main/.cursor/skills-cursor/statusline
Command: npx skills add https://github.com/kkkaoru/dotfiles --skill statusline-kkkaoru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developers using the Cursor CLI lack visibility into session state such as the active model, context window usage, working directory, and git branch while working in the terminal. ## Core Features & Use Cases - Command-based status line: Register any executable or inline command in ~/.cursor/cli-config.json that receives a JSON session payload on stdin and renders stdout above the prompt. - Rich session payload: Access model info, context window percentages, workspace paths, vim mode, worktree details, and output style from the stdin JSON. - Multi-line and ANSI rendering: Display multiple rows with ANSI color codes, with configurable padding, update interval, and timeout. - Use Case: Show the current model name, a context-usage progress bar, and the current git branch in two colored lines above the prompt so you always know your session state. ## Quick Start Ask the assistant to set up a status line script that shows the current model and context usage percentage, and register it in the CLI config.

Frequently Asked Questions about statusline

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

FAQPage Schema
How do I configure a custom status line in the Cursor CLI?

Add a statusLine entry with type "command" and a command path to ~/.cursor/cli-config.json. The command receives a JSON session payload on stdin and its stdout is rendered above the prompt.

What data is available in the status line JSON payload?

The payload includes session_id, transcript_path, cwd, model id and display name, context window token counts and percentages, workspace paths, vim mode, worktree info, CLI version, and output style.

Can the status line show multiple lines and colors?

Yes, each line of stdout renders as a separate row, and ANSI color codes are fully supported. You can use tools like jq, tput, or escape sequences to produce colored multi-line output.

Why is my status line not updating or showing stale text?

If the command exits non-zero with empty stdout, the previous text is kept. Commands that exceed the timeout (default 2000ms) or overlap with a new update are killed, so keep scripts fast.

Does the status line command consume API tokens?

No, the status line runs locally on your machine and does not consume API tokens. Updates are debounced at the configured interval, clamped to a minimum of 300ms.