One developer treats the Pi coding agent like an OS

What it does

A monorepo of 25 independently installable extensions for the Pi Coding Agent, published under the @narumitw npm scope. The catalog spans coding and delegation (pi-lsp, pi-plan-mode, pi-subagents), browser automation (pi-chrome-devtools, pi-firecrawl), workflow management (pi-worktree, pi-goal), and terminal ergonomics — statuslines, timestamps, even a plugin that keeps your machine awake while the agent grinds. There’s also pi-tui-kit, a reusable TUI library for people writing their own extensions.

The interesting bit

The boring extensions are the tell: account switching, a Starship-style footer, response timestamps, and a /btw command for side questions that don’t pollute the main context. This is the toolkit of someone who lives in the agent all day and has started treating it like an operating system — which, judging by the breadth here, is roughly what it’s becoming.

Key highlights

• pi-lsp — language-server diagnostics and code actions across TypeScript, Python, Rust, Go, C/C++, JVM, .NET, and more
• pi-btw — ask a quick side question without adding it to the main conversation
• pi-accounts — switch named OAuth accounts across OpenAI, Anthropic, GitHub Copilot, Kimi, OpenRouter, Radius, and xAI
• pi-goal — keeps the agent working until a goal is verified complete
• pi-tui-kit — declarative navigation, settings, and multi-select flows for extension authors, built on @earendil-works/pi-tui

Caveats

• Extensions run with your full user permissions; the README itself warns to review any third-party extension before installing
• pi-subagents is source-only — it’s not published to npm
• pi-starship and pi-statusline can’t be enabled together, and the deprecated pi-workflow package has no atomic migration path

Verdict

If you run the Pi Coding Agent, this is a one-stop catalog worth an afternoon of browsing. If you don’t, it’s still a preview of what agent ecosystems look like once someone takes extension APIs seriously.