A Karpathy-style LLM wiki about the Pi coding agent ecosystem — extensions, skills, packages, themes, providers, grouped into categories.
Pi is minimal and stripped to its core. The extension ecosystem on the other hand is sprawling and hard to keep track of. This LLM wiki makes an attempt to map structure to this ecosystem: what extensions are out there, what they do, how they compare to other extensions. PRs to this repo are very welcome.
Main use case is querying it with Pi — this wiki is meant to be read and written by an LLM. Point Pi at this repo (using the skill developed by the author or another LLM-wiki skill) and ask things like "What different categories of subagent systems exist and which extension falls into which one? Please also specify the community sentiment and popularity for each extension."
This is not yet another awesome-extension list — it's a navigation
TOC with structure and comparisons. Awesome-lists like
qualisero/awesome-pi-agent,
awesome-pi.site, and
pi.dev/packages are referenced here in
references/catalogs.md.
| Goal | Go here |
|---|---|
| Search the web from Pi | Web Search Extensions — extensions and skills side-by-side |
| Customize how Pi looks (themes, status bar, tool output, busy spinner) | Themes · Footer / Powerline · Tool Rendering · Working / Thinking Indicators |
| Delegate tasks to child agents (subagents, parallel work) | Subagent Extensions — four execution patterns + team/swarm orchestration; how to get a full subagent view |
| Track what my agent is doing (TODO lists, task progress) | TODO List Extensions — idiomatic tool shapes, widget stack, picking guide |
| Keep long sessions coherent across compactions | Compaction Extensions — algorithmic vs observation-ledger vs agentic-VFS vs tool-output-pruning |
| Tame the prompt (floating editor, history search, templates, queues, cache) | Prompt Extensions — four layers (input UX, template authoring, queueing, provider cache) |
| Make Pi work autonomously (iterate until done, run overnight) | Loop and Ralph Extensions — 7 architectural variants compared |
| Connect Pi to other services (Google Workspace) | Google Workspace — gws CLI, OAuth, command shapes |
| Pick a provider or bring a Claude subscription | Providers and model access — third-party providers, the EU gap, Anthropic auth routes, Claude Pro/Max in Pi, and the Claude Code bridges |
Also: evaluate an extension before installing · browse everything by category · find what's not surveyed yet.
For the complete list of pages organized by category, see
index.md. The tables above cover the most common
entry points; index.md covers everything.
ecosystem/— one page per niche. Survey pages name the options, compare them, and end in a "how to pick" section; integration-reference pages document a single integration target.references/— methodology and catalogs (evaluation, catalogs).- No live numbers in prose. Stars, downloads, and commit dates go
stale in weeks, so pages carry stable
repo:/npm:identifiers in frontmatter instead and you query the current figures at read-time with the recipes in evaluation.md. Architectural comparisons (which are timeless) stay inline. - Conventions live in SCHEMA.md; every source is registered in raw-sources/index.md.
First gotos:
nicobailon/pi-web-access— web search + content fetch. Single tool, sensible defaults.nicobailon/pi-powerline-footer— at-a-glance status bar (model, cost, branch, dir). The footer you stop noticing because it's right.MasuRii/pi-tool-display— compact tool-call rendering. Stops tool output from burying the conversation.
Nice to have:
tintinweb/pi-manage-todo-list— the moment you need to track what Pi is doing across multiple turns, you want this. It mirrors the Copilotmanage_todo_listshape that LLMs already know.
Environment-dependent:
- GitHub skill from
mitsuhiko/agent-stuff—ghCLI workflows - Optional: Google Workspace skill — only if you live in Gmail/Docs/Calendar
- Optional: Jira skill — only if your tickets are in Jira
MIT.