OpenRuna
Sign in
SKILL.md

name: statusline description: >- Configure a custom status line in the CLI. Use when the user mentions status line, statusline, statusLine, CLI status bar, prompt footer customization, or wants to add session context above the prompt.

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.

Configuration

Add a statusLine entry to ~/.cursor/cli-config.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 '...'.

FieldRequiredDefaultDescription
typeyesMust be "command"
commandyesPath to an executable or inline command. ~ is expanded.
paddingno0Horizontal inset (in characters) for the status line container.
updateIntervalMsno300Minimum interval between invocations. Clamped to >= 300ms.
timeoutMsno2000Maximum time the command may run before it is killed.

Stdin payload

The command receives a JSON object on stdin. The TypeScript interface is StatusLinePayload in packages/agent-cli/src/hooks/use-status-line.ts.

Full JSON schema

{
  "session_id": "abc123",
  "session_name": "my session",
  "transcript_path": "/path/to/transcript.jsonl",
  "render_width_chars": 120,
  "cwd": "/Users/me/project",
  "autorun": false,
  "model": {
    "id": "claude-4-opus",
    "display_name": "Claude 4 Opus",
    "param_summary": "(Thinking)",
    "max_mode": true
  },
  "workspace": {
    "current_dir": "/Users/me/project",
    "project_dir": "/Users/me/project/.cursor/transcripts",
    "added_dirs": []
  },
  "version": "1.2.3",
  "output_style": {
    "name": "default"
  },
  "context_window": {
    "total_input_tokens": 15234,
    "total_output_tokens": null,
    "context_window_size": 200000,
    "used_percentage": 34.5,
    "remaining_percentage": 65.5,
    "current_usage": null
  },
  "vim": {
    "mode": "NORMAL"
  },
  "worktree": {
    "name": "my-feature",
    "path": "/Users/me/.cursor/worktrees/repo/my-feature"
  }
}

Available fields

FieldDescription
session_idUnique session identifier
session_nameCustom session name. Absent if no name has been set
transcript_pathPath to conversation transcript file
render_width_charsUsable terminal columns minus built-in padding
cwd, workspace.current_dirCurrent working directory (both contain the same value)
autoruntrue when auto-run is enabled for the current session
workspace.project_dirDirectory where transcripts are stored
workspace.added_dirsAdditional directories (empty array for now)
model.id, model.display_nameCurrent model identifier and display name
model.param_summaryFormatted parameter summary (e.g. "(Thinking)", "High"). Absent when empty
model.max_modetrue when max mode is enabled. Absent otherwise
versionCLI version string
output_style.name"default" or "compact"
context_window.total_input_tokensEstimated input tokens (derived from used_percentage)
context_window.total_output_tokensCumulative output tokens (null when not tracked)
context_window.context_window_sizeMaximum context window size in tokens
context_window.used_percentagePercentage of context window used
context_window.remaining_percentagePercentage of context window remaining
context_window.current_usageToken counts from the last API call (null before first call)
vim.mode"NORMAL" or "INSERT" when vim mode is enabled
worktree.nameWorktree name when running inside a worktree
worktree.pathAbsolute path to the worktree directory

Fields that may be absent

  • session_name — only present when a custom name has been set
  • model.param_summary — only present when model has non-default parameters
  • model.max_mode — only present when max mode is enabled
  • vim — only present when vim mode is enabled
  • worktree — only present when running in a worktree

Fields that may be null

  • context_window.current_usage — null before the first API call
  • context_window.used_percentage, context_window.remaining_percentage — may be null early in the session

Stdout / rendering

  • Multiple lines are supported: each line of stdout renders as a separate row in the status area.
  • ANSI color codes are supported (use chalk, tput, \033[32m, etc.).
  • If the command exits non-zero with empty stdout, the status line is not updated (previous text is kept).
  • If the command times out or a new update arrives while the script is running, the in-flight process is killed.
  • The status line runs locally and does not consume API tokens.

Examples

Basic: model + context usage

#!/usr/bin/env bash
payload=$(cat)
model=$(echo "$payload" | jq -r '.model.display_name')
pct=$(echo "$payload" | jq -r '.context_window.used_percentage // 0' | cut -d. -f1)
printf "\033[90m%s  ctx %s%%\033[0m" "$model" "$pct"

Context progress bar

#!/usr/bin/env bash
input=$(cat)
MODEL=$(echo "$input" | jq -r '.model.display_name')
PCT=$(echo "$input" | jq -r '.context_window.used_percentage // 0' | cut -d. -f1)

BAR_WIDTH=10
FILLED=$((PCT * BAR_WIDTH / 100))
EMPTY=$((BAR_WIDTH - FILLED))
BAR=""
[ "$FILLED" -gt 0 ] && printf -v FILL "%${FILLED}s" && BAR="${FILL// /▓}"
[ "$EMPTY" -gt 0 ] && printf -v PAD "%${EMPTY}s" && BAR="${BAR}${PAD// /░}"

echo "[$MODEL] $BAR $PCT%"

Multi-line with git info

#!/usr/bin/env bash
input=$(cat)
MODEL=$(echo "$input" | jq -r '.model.display_name')
DIR=$(echo "$input" | jq -r '.workspace.current_dir')
PCT=$(echo "$input" | jq -r '.context_window.used_percentage // 0' | cut -d. -f1)

BRANCH=""
git rev-parse --git-dir > /dev/null 2>&1 && BRANCH=" | 🌿 $(git branch --show-current 2>/dev/null)"

echo -e "\033[36m[$MODEL]\033[0m 📁 ${DIR##*/}$BRANCH"
echo -e "ctx $PCT%"

Inline jq command (no script file)

{
  "statusLine": {
    "type": "command",
    "command": "jq -r '\"[\\(.model.display_name)] \\(.context_window.used_percentage // 0)% context\"'"
  }
}

Testing

Test a script with mock input:

echo '{"model":{"display_name":"Opus"},"context_window":{"used_percentage":25}}' | ./statusline.sh

The command is spawned with child_process.spawn (no shell on Unix, shell: true on Windows for .cmd/.bat compatibility). Updates are debounced at the configured interval. If a new update triggers while a script is running, the in-flight process is killed via AbortController and the new invocation starts immediately.

Overview

statusline is a free skill on OpenRuna. Configure a custom status line in the CLI. Use when the user mentions status line, statusline, statusLine, CLI status bar, prompt footer customization, or wants to add session cont

What this skill does

Looking for a dependable skill? "statusline" gives you a tested starting point instead of a blank prompt box. Configure a custom status line in the CLI. Use when the user mentions status line, statusline, statusLine, CLI status bar, prompt footer customization, or wants to add session context above the prompt. OpenRuna cross-links it to related prompts, agents, and tools, which makes assembling a full workflow around it straightforward. Paste it straight into a chat, drop it into a system prompt, or store it as a reusable skill.

Use cases

  • Use "statusline" when you need a repeatable skill for professional work without rewriting instructions every time.
  • Hand "statusline" to a new teammate so their skill output matches your team's quality bar from day one.
  • Combine it with related tools and prompts in the same OpenRuna category to build an end-to-end workflow.
  • Reach for it during planning or review sessions when you want consistent, AI-assisted structure.

Example output

Running this skill produces output shaped like the source material below:

# 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…

Results vary by model and temperature; treat the first response as a draft and refine it with follow-up prompts.

Tips by platform

Claude

Claude works best when you paste this skill up front and ask it to outline its plan before writing. Use the artifact panel to refine structured output turn by turn.

ChatGPT

ChatGPT responds well when you paste this skill and immediately give one concrete example of your input. Use a reasoning-capable model for multi-step work.

Cursor

In Cursor, lift the key instructions from this skill into .cursorrules or a SKILL.md file, then reference it in Agent mode with @ mentions. Keep the title in a comment so teammates can find it on OpenRuna.

Frequently asked questions

What is "statusline"?
It is a skill listed on OpenRuna — Configure a custom status line in the CLI. Use when the user mentions status line, statusline, statusLine, CLI status bar, prompt footer customization, or wants to add session context above the prompt. You can copy and adapt it for ChatGPT, Claude, Cursor, or any other AI assistant.
Is "statusline" free to use?
Most OpenRuna resources are open or CC0-licensed. Check the license shown on this page before commercial use; premium collections are clearly marked as such.
How do I get the best results from this skill?
Replace any placeholders, add your project context, and ask the model to confirm its assumptions first. Iterate over 2–3 follow-up turns rather than expecting a perfect first response.
Does "statusline" work with both Claude and ChatGPT?
Yes — it is model-agnostic text, so it runs on Claude, ChatGPT, Gemini, and Cursor. The tips on this page cover each of those assistants specifically.
Where can I find resources related to "statusline"?
Scroll to the Related resources section on this page, or open the matching category hub on OpenRuna to find connected prompts, tools, agents, and datasets in the same topic area.

Related resources