useful-pi-extensions

English | 中文

A small collection of pi extensions, installed with one command. Every extension in it is also published on its own, so you can take the collection or just the piece you want.

• useful-pi-extensions, the collection — npm · pi packages gallery
• @reedchan/statusline — npm · pi packages gallery

pi install npm:useful-pi-extensions

What is in here

Extension	What it does
@reedchan/statusline	Replaces pi's footer with a labelled two-row one: context pressure as a fixed-size meter, the session's input/output tokens, cache hit rate and cost (in whatever currency you configure), the model and effort level, and the latest turn's TTFT and decode throughput in tokens/second

Only one extension owns the footer, so statusline is a complete replacement rather than an addition. If you want pi's stock footer back, remove this package and /reload.

Screenshots

statusline

Install

# the collection: every extension in this repository
pi install npm:useful-pi-extensions

# one extension on its own
pi install npm:@reedchan/statusline

# from the repository, pinned to a tag
pi install git:github.com/reedchan7/useful-pi-extensions@v1.0.0

# from a local checkout (development)
pi install /absolute/path/to/useful-pi-extensions

Then reload pi in the running session with /reload, or start a new one.

Install one surface, not both. The collection and the individual package ship the same extension file, so installing useful-pi-extensions and @reedchan/statusline loads it twice. Nothing breaks, but there is nothing to gain either.

Removing a loose copy first. If you were running the extension as a single file in ~/.pi/agent/extensions/, delete that file before installing this package. Both would load, and two footers race for the same slot — the later one wins, which decides nothing useful.

Requirements

• pi 0.85 or newer (pi --version)
• No runtime dependencies. @earendil-works/pi-coding-agent and @earendil-works/pi-tui are peer dependencies supplied by pi itself.

Layout

Two things are published from this repository: the collection, which is the repository root, and each extension under packages/, on its own.

package.json                     # the collection package, published as useful-pi-extensions
packages/
  statusline/                    # published as @reedchan/statusline
    package.json
    extensions/statusline/
      index.ts                   # pi entry point: events and footer wiring
      render.ts                  # pure helpers: number formatting, the meter, row layout
      render.test.ts             # unit tests for render.ts
tools/                           # repository tooling: docs pairing, commit lint, publishing

The collection declares "pi": { "extensions": ["packages/*/extensions"] } and the individual package declares "./extensions". pi resolves the glob, finds every extensions/<name>/index.ts and loads it — no build step, no bundling. Adding an extension is therefore adding a directory under packages/: no manifest needs editing, because the collection's glob picks the new package up on its own, and make publish discovers it the same way.

Development

make install      # bun install
make check        # every gate: format, lint, types, docs pairing, tests
make hooks        # install the git hooks (run once, needs a git checkout)
make help         # list every target

make check runs the same gates as CI:

Gate	Command	What it enforces
Format	bun run fmt:check	oxfmt: 100 columns, single quotes, no semicolons
Lint	bun run lint	oxlint in type-aware mode with --deny-warnings, so a warning fails the run
Types	bun run typecheck	--strict plus noUncheckedIndexedAccess, exactOptionalPropertyTypes and verbatimModuleSyntax, which is what keeps every file loadable by pi without a transform
Docs	bun run docs:check	every README.md has a README_CN.md with the same heading sequence and a working language switcher
Tests	bun test	the unit tests under packages/*/

Commits follow Conventional Commits: the commit-msg hook rejects a subject that is not type(scope): summary, and the pre-commit hook formats and lints only the staged files. The toolchain is pinned to exact versions in package.json (bunfig.toml sets install.exact = true). The @earendil-works/* packages are deliberately left at *: they are the host API pi supplies, and tracking it is what surfaces an upstream break early.

License

MIT. See LICENSE.