pi-tui-status-beautifier

Minimalist status bar formatter & layout engine for Pi TUI.

Clean up fragmented extension status strings. Enjoy adaptive narrow-terminal folding and zero render-loop disk I/O, with zero telemetry hijacking.

English | 日本語 | 简体中文

  ┌─ Native Status Bar (Fragmented & Cluttered) ────────────────────────────────────────────────────────┐
  │  plannotator: 🟢 3 tasks    pi-mcp-adapter: [connected]    toolflow: active (2/5)    anchor: 3 items │
  └─────────────────────────────────────────────────────────────────────────────────────────────────────┘
                                                    │
                                                    ▼
  ┌─ pi-tui-status-beautifier (Normalized, Coherent & Adaptive) ────────────────────────────────────────┐
  │  plan ❯ ◆ 3    mcp ❯ ● ready    toolflow ❯ ⌬ 2/5    anchor ❯ ⌖ 3    chrome ❯ ● connected            │
  └─────────────────────────────────────────────────────────────────────────────────────────────────────┘

Install directly inside Pi:

pi install npm:pi-tui-status-beautifier

Takes effect immediately. Type /beautify anytime to switch styles interactively.

As the Pi extension ecosystem grows, developers routinely install multiple tools (plannotator, pi-mcp-adapter, toolflow, pi-anchor, pi-lingual). The status bar quickly runs into four frictions:

Every extension authors status text independently. Some prefix long package names (pi-mcp-adapter:), some wrap counts in brackets ([2]), and others dump raw emojis. Inconsistent character metrics create visual distraction at the bottom of your screen. pi-tui-status-beautifier strips package suffixes and normalizes raw text into uniform, structured micro-badges.

In split-pane layouts (tmux, WezTerm, or windows < 80 columns), long status strings wrap onto multiple lines, shoving your prompt up and down and breaking typing flow. The built-in column budget guard automatically collapses idle badges into (+3 idle) when width tightens, prioritizing errors and running tasks.

Many status bar plugins take a heavy-handed approach: completely replacing Pi's native footer via ctx.ui.setFooter. In doing so, they wipe out essential system metrics—git branches, token counts (↑1.2k ↓3.4k), cache read rates, and thinking levels (• high). This extension defaults to a non-intrusive micro-hook (status-only): it normalizes extension badges while leaving Pi's native system telemetry 100% intact.

Reading configuration files synchronously inside high-frequency TUI animation redraw loops causes disk contention and sluggish typing. This extension loads settings into memory at startup and uses dirty-checking caches, performing zero synchronous file reads during TUI redraws.

  /beautify (Open interactive theme switcher anytime)

Type /beautify to switch styles interactively:

  1. stream (Default Minimalist Stream)
     chrome ❯ ● ready    toolflow ❯ ⌬ 2/5    anchor ❯ ⌖ 3    plan ❯ ◆ 1

  2. powerline (Angled Brackets & Distinct Glyphs)
     chrome ‹◆ ready›    toolflow ‹◈ 2/5›    anchor ‹⌖ 3›    plan ‹◆ 1›

  3. matrix (Dot-Matrix Framing & Star Accents)
     chrome ⦗✦ ready⦘    toolflow ⦗✧ 2/5⦘    anchor ⦗⌖ 3⦘    plan ⦗✦ 1⦘

  4. glow (High-Contrast Inverse Pill Badges)
     chrome [ ● ready ]  toolflow [ ⌬ 2/5 ]  anchor [ ⌖ 3 ]  plan [ ◆ 1 ]

  5. minimal (Fixed 10-Column Aligned Stream)
     chrome     ❯ ● ready    toolflow   ❯ ⌬ 2/5    anchor     ❯ ⌖ 3

  6. custom (AI-Assisted Co-Design)
     Describe your aesthetic in plain text; your agent generates 3 ASCII mockups.

• 🛡️ Non-Destructive Dual Scopes:
  • status-only (Default & Recommended): Only hooks ctx.ui.setStatus badges. Preserves Pi's native Git branch, working directory, token counts, and thinking levels 100% untouched.
  • full-footer: Formats the entire bottom bar with system telemetry on line 1 and badges on line 2.
• 📐 Unicode UAX #11 & Surrogate-Pair Safety: Built-in character scanner accurately measures East Asian Wide (2 cols), ASCII (1 col), and ANSI escape codes (0 cols), eliminating cursor jitter and column misalignments.
• ⚡ Zero Render-Loop Disk I/O: Loads configuration once into memory. Redraw loops perform zero synchronous disk reads (fs.readFileSync), using dirty-checking to skip duplicate renders.
• ◐ Terminal Micro-Spinners: Active background tasks (running, working) trigger a smooth 300ms spinner (◐, ◓, ◑, ◒).
• 🗑️ Zero-Trace Physical Cleanup (off): Turning the extension off restores all original status strings and deletes the beautifier block from settings.json, leaving zero orphaned configuration behind.

/beautify                # Open interactive style picker
/beautify stream         # Switch directly to stream preset
/beautify off            # Revert to native status bar and delete config

Preferences persist in ./.pi/settings.json (project-level) or ~/.pi/agent/settings.json (global):

{
  "beautifier": {
    "style": "stream",
    "fullFooter": false
  }
}

The inspiration behind pi-tui-status-beautifier comes from daily aesthetic frustration: visual noise.

As I installed more extensions for Pi, the bottom status bar turned into a chaotic billboard. Every extension author used their own punctuation, raw emojis, and arbitrary string widths. In split-pane tmux or compact windows, lines wrapped awkwardly and the screen constantly flickered.

When I looked into existing status bar plugins, many took a sledgehammer approach: completely replacing Pi's native footer via ctx.ui.setFooter. In doing so, they wiped out essential platform metrics—token usage, cache read rates, thinking levels, and git branches. Even worse, some plugins read configuration files synchronously inside the animation redraw loop, causing typing sluggishness.

I built this beautifier around three strict constraints:

1. Never hijack native telemetry: Normalize extension badges while keeping system metrics untouched.
2. Zero render-loop disk reads: Memory-cached configuration with dirty-checking.
3. Zero-trace revert: Turning it off physically deletes the config block (delete config.beautifier).

A good status bar should be quiet, balanced, and invisible until you need it.

npm test            # 18/18 Vitest unit tests pass
npm run lint        # Zero ESLint warnings

Each extension occupies a distinct terminal slot (aboveEditor, belowEditor, status-only footer, and runtime tool hooks) so all four run together with zero widget overlap:

MIT © Jason