The Pi coding agent is minimal by design. LazyPi is opinionated by design. Run one command and get a complete, curated Pi setup — everything selected by default, nothing to research, nothing to configure. Remove what you don't want later.
npx @robzolkos/lazypiLazyPi will:
- Install
pifor you if it isn't installed yet. - Ask if you want to install all the packages or choose which to install.
That setup includes agent tooling, memory, planning, terminal-native diff review, a Claude Code CLI provider, interactive shell overlays for long-running CLIs, usage tracking, and themes.
That's it. Once done - run pi and experience a feature rich coding agent experience.
Install is idempotent — LazyPi reads your Pi settings and skips any package that is already installed, so re-running is safe.
| Command | What it does |
|---|---|
npx @robzolkos/lazypi |
Install all or selected catalog (interactive picker by default) |
npx @robzolkos/lazypi remove <id> |
Remove a catalog package by id (or pass a raw pi source) |
npx @robzolkos/lazypi status |
Show which catalog packages are installed, missing, or extra |
npx @robzolkos/lazypi update |
Run pi update for installed Pi packages |
npx @robzolkos/lazypi doctor |
Check your environment for common problems |
npx @robzolkos/lazypi updatenpx @robzolkos/lazypi removeShows an interactive picker of installed packages. Or pass ids directly to skip the picker:
npx @robzolkos/lazypi remove subagents
npx @robzolkos/lazypi remove npm:pi-subagents@0.13.3 # raw pi source also worksThere is nothing to "uninstall" for LazyPi itself — npx doesn't leave it around.
Run the built-in health check with npx @robzolkos/lazypi doctor.
The site at lazypi.org lives in docs/ and is a Jekyll site compiled by GitHub Pages automatically on push to master.
To preview locally (requires Ruby + Bundler):
cd docs && bundle install # first time only
npm run docs:serve # serves at http://localhost:4000 with livereloadShared nav and footer are in docs/_includes/. Layouts are in docs/_layouts/. CSS variables and nav styles are in docs/assets/css/site.css.
LazyPi uses Release Please and npm trusted publishing.
To release a new version:
- Merge your normal PRs into
master - Merge the Release Please release PR when you are ready to publish
- GitHub creates the tag/release and publishes to npm automatically
For the full list of included packages and themes, see lazypi.org.