@henryqw/pi-footer

Keep checkout identity, model usage, elapsed agent work, and extension status visible while you work in Pi. See repository, pull request, model, cost, and status details without separate commands.

Install

pi install npm:@henryqw/pi-footer

Works with

Use

After installing, start a Pi TUI session to see checkout, usage, model, thinking, and extension statuses.

pi-harness · clear-field-f8d2 [+2 ~3 ?1 ↑2] · PR #123 · approved    Codex #1 · 50% · 7d 1d 1h 22m
↑ 12.4k · ↓ 2.1k · ↺ 84.3% · ⚡ 87.4 t/s · $ 0.127 · ◔ 36.8%    gpt-5.6-luna • high
✓ CG · ●  🐴 ponytail: ⚡ FULL                                           ◷ 12m 34s

• The first line shows the repository, branch, Git state, and pi-pr pull request status beside the checkout identity. The pi-multi-codex quota status, when non-empty, occupies the right side. Linked-worktree branches drop the generated worktree/ prefix.
• The second line shows cumulative input tokens, output tokens, latest cache-hit rate, and tokens per second for the most recent assistant response. The rate is timed from the response's first streamed content to its last, so request latency, time to first token, and provider work after the stream ends (such as Claude bridge shutting down Claude Code) are excluded. A response that arrives without streamed content, or all at once, shows —. It also shows estimated cost and context usage. Totals include reported tool usage and finished pi-subagent background workflows. The active model and thinking level are right-aligned. Under a virtual model, the physical model and thinking level of the latest successful response follow an arrow, for example auto • high → gpt-5.6-luna • medium, matching Pi's built-in footer.
• The third line shows a compact CodeGraph badge first when loaded: ✓ CG indexed, ● CG in use, ◐ CG checking or indexing, ○ CG missing, ! CG setup problem, or ? CG unknown state. Its icon uses the active theme's state color; CG remains plain so the badge is readable without color. When pi-codegraph is not loaded, no badge appears. A middle dot separates the CodeGraph badge from other extension statuses; cumulative agent-work time stays on the right, beneath the active model.

Git badges appear only when action is needed:

?N counts porcelain status entries. In --untracked-files=normal mode, Git may collapse a whole untracked directory to one entry.

Active operations appear first, such as REBASE 3/7, MERGING, or CHERRY-PICKING. Detached HEAD uses the short commit form @a1b2c3d.

The extension reads local Git data with git status --porcelain=v2 --branch --untracked-files=normal. It refreshes after each agent run and branch change. It does not make an LLM call or fetch a remote. Ahead and behind counts use the last fetched upstream state.

Unavailable values render as — without a misleading percent sign.

off uses the same dim grey as the model name. Active levels use an ANSI-256 gradient: green minimal, yellow-green low, lime medium, yellow high, orange xhigh, and red max.

ultra renders as a rainbow when the active Pi runtime supplies that thinking level. Unsupported levels never appear.

Only the non-empty pi-multi-codex quota status occupies the right side of the first line. The pi-pr pull-request status stays beside checkout identity, and CodeGraph appears separately on the third line.

Statuses from other extensions, including Ponytail and pi-rewind, share the left side of the third line. They are sorted by key; colors, links, glyphs, and interior spacing are preserved. Leading and trailing whitespace is trimmed, line breaks become spaces, and long statuses may be clipped to fit the footer. Only direct codegraph_explore tool calls trigger the ● CG badge; CodeGraph queries made from inside scripted tools are not shown.

Limits and recovery

When the configured executable is code and Pi reports hyperlink support, the accent-colored checkout name links to the current path. The link opens a new window for code -n or code --new-window. A missing config silently uses code. Other executables and terminals with hyperlinks disabled render plain text.

Use Pi fullscreen TUI so Pi handles the custom URI:

{
  "tuiMode": "fullscreen"
}

Set this through /settings, or launch with --tui-mode fullscreen. Then use normal primary click. Regular TUI delegates OSC 8 activation to the terminal.

Ghostty uses Cmd+click but may not open custom URI schemes.