statusline

Configure a CLI status line with session context above the prompt.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/OM-bit-hub/daily_tracker --skill statusline-om-bit-hub
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: statusline
Source: https://github.com/OM-bit-hub/daily_tracker/tree/main/.agents/skills-cursor/statusline
Command: npx skills add https://github.com/OM-bit-hub/daily_tracker --skill statusline-om-bit-hub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configure a custom status line in the CLI to keep session context visible above the prompt during every interaction.

Core Features & Use Cases

  • Dynamic status updates on each conversation
  • Easy customization via a statusLine JSON in ~/.cursor/cli-config.json
  • Supports custom commands, padding, update intervals, and timeouts

Quick Start

Add a statusLine entry to your CLI config and point it at a script or inline command to render the status line.

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 CLI to show session context?

To configure a custom CLI status line, add a statusLine entry to ~/.cursor/cli-config.json and point it at a script or inline command to render the status line above the prompt.

What is a CLI status line used for during terminal workflows?

A CLI status line provides persistent contextual cues during terminal workflows, displaying session naming, directory awareness, and quick status at a glance above the prompt for every interaction.

Does the CLI status line support custom update intervals and timeouts?

Yes, the status line configuration in ~/.cursor/cli-config.json supports fields like updateIntervalMs and timeoutMs, along with type, command, and padding for dynamic status updates.

Can I use a custom shell script to render the terminal session status line?

Yes, you can point the statusLine command field at a custom script or inline command within ~/.cursor/cli-config.json to render the terminal session context dynamically.

What are the limitations of using a JSON configuration for the CLI status line?

The status line requires a JSON configuration in ~/.cursor/cli-config.json, meaning any syntax errors or missing fields like type and command will prevent the status line from rendering above the prompt.