statusline

# CLI Status Line The CLI supports a user-configurable status line rendered above the prompt. A command is spawned on each conversation update, receives a JSON payload on stdin describing the session, and its stdout is displayed as the status line. The spec is aligned with [Claude Code's status line](https://code.claude.com/docs/en/statusline). ## Configuration Add a `statusLine` entry to `~/.cursor/cli-config.json`: ```json { "statusLine": { "type": "command", "command": "~/.cursor/statusline.sh", "padding": 2 } } ``` The `command` field supports full paths, `~` expansion, and shell-style argument splitting. You can point it at a script file or use an inline command like `jq -r '...'`. | Field | Required | Default | Description | |-------|----------|---------|-------------| | `type` | yes | — | Must be `"command"` | | `command` | yes | — | Path to an executable or inline command. `~` is expanded. | | `padding` | no | `0` | Horizontal inset (in characters) for the status line container. | | `updateIntervalMs` | no | `300` | Minimum interval between invocations. Clamped to >= 300ms. | | `timeoutMs` | no | `2000` | Maximum time the command may run before it is killed. | ## Stdin payload The command receives a JSON object on stdin. ### Full JSON schema ```json { "session_id": "abc123", "session_name": "my session", "transcript_path": "/path/to/transcript.jsonl", "render_width_chars": 120, "cwd": "/Users/me/project", "model": { "id": "cla...