LazyPi

A one-command installer and configuration bundle for Pi, Mario Zechner's minimal coding agent. Run npx @robzolkos/lazypi and it installs Pi if you don't have it, then sets up the skills, themes, and extensions the Pi community has converged on — 60+ skills, 67 themes, MCP adapter, sub-agents, persistent memory, planning mode, cost/usage tracking, todo tracking. The pitch on lazypi.org is "the fastest way to fall in love with Pi": vanilla Pi ships with 0 skills and 2 themes; LazyPi takes you to 60+ and 67 with a single command and no config. By Rob Zolkos.

The distinction that matters

LazyPi is not a fork. This is the line that separates it from oh-my-pi, the other "batteries-included Pi." Where oh-my-pi forks the Pi codebase and bundles tools (LSP, IPython, browser automation) directly into the agent binary, LazyPi leaves upstream Pi completely untouched and installs a curated set of community npm/git packages around it. You still run the same pi that Mario Zechner ships; LazyPi is the curation-and-install layer on top.

That gives the Pi ecosystem three distinct shapes:

Pi — minimal core, extend-it-yourself, 0 skills out of the box
oh-my-pi — a maximalist fork that bakes the common tools into the binary (the oh-my-zsh relationship: replace the thing)
LazyPi — a distribution/installer over unmodified Pi that pulls in community packages (the LazyVim relationship: keep the thing, curate what sits on it)

The practical trade: LazyPi stays current with upstream Pi automatically (it doesn't own the binary), and you keep the exact agent everyone else runs; the cost is that you inherit the fragmentation of many small third-party packages instead of one integrated fork. It's the strongest evidence yet that Pi's deliberate "features belong in community packages, not the core" bet actually produced an ecosystem worth curating.

What it installs

The catalog is hand-picked ("curated, not exhaustive") and grouped, with an interactive picker or an install-everything option. A representative slice:

core — pi-subagents (isolated parallel sub-agents), pi-mcp-adapter (connect Pi to any MCP server), pi-web-access (search + URL fetch), pi-memory-md (persistent memory as Markdown), pi-plan (read-only planning mode with approval-based execution), pi-simplify, pi-add-dir, pi-claude-cli (use Claude Code CLI auth as a Pi model provider)
ui — plannotator (visual plan review), pi-slopchop (terminal diff review with FIX/DISCUSS annotations, also by robzolkos), pi-powerbar (status line with live context), pi-usage-extension (token/cost tracking), pi-manage-todo-list, pi-btw (side questions without polluting history), pi-interactive-shell
research — pi-autoresearch (long-running research loop), pi-ralph-wiggum (iterative dev loops with goals and self-reflection)
frameworks — Official Compound Engineering, Every's planning-and-review methodology for Pi via the official upstream converter (requires Bun)
themes — 67 community themes (Kanagawa, Carbonfox, Gruvbox Dark, Hackerman, …)

A recurring cast of authors shows up across the catalog — nicobailon (much of core), tmustier, juanibiapina, and Zolkos himself — which is what an actual community ecosystem, rather than a single vendor's plugin list, looks like.

Usage

# One command — installs Pi if missing, then configures everything:
npx @robzolkos/lazypi

# Re-run anytime; it skips what's already installed.

After install, Pi's own First Steps doc covers launching, authenticating, and the high-value commands. There's no separate binary and no config file to write — that's the whole point ("0 config needed").

Limitations

v0.6.x, single author (Rob Zolkos). It's young and its value is entirely curation, so it depends on one person tracking a fast-moving set of third-party packages.
Curation risk cuts both ways. Because it installs many independent community packages rather than one integrated fork, breakage in any upstream package (or an abandoned one) is LazyPi's problem to notice and re-curate. oh-my-pi absorbs that risk into a single codebase; LazyPi distributes it.
Some packages need Bun — notably the Compound Engineering framework — so it's not purely a Node/npx story for the full catalog.
It's a convenience layer, not a capability layer. Everything LazyPi installs, you could npm install yourself into vanilla Pi. The value is the picking and wiring, which means its moat is taste and maintenance, not code.

Watchlist

On watchlist for the same reason as oh-my-pi: young (v0.6.3), single-maintainer, and structurally dependent on an upstream ecosystem it doesn't control. Worth re-checking whether it gains a second maintainer, whether the curated catalog stays fresh as packages come and go, and whether Pi's ecosystem keeps growing enough to justify a curation layer at all.

pi-coding-agent — the minimal upstream this installs and configures
oh-my-pi — the fork alternative; the installer-vs-fork contrast is the key distinction
botctl — a different agent-orchestration angle (multi-agent supervision rather than single-agent extension)
claude-code — the closest commercial analog to a bundled-skills coding agent; mcp-vs-skills on where the skill format ends and MCP begins

Repo: github.com/robzolkos/LazyPi — ~373 stars, MIT, npm @robzolkos/lazypi (v0.6.3). Site: lazypi.org. Pi is a product of Earendil / Mario Zechner.