Primary project
pi (pi-mono)
Repository: badlogic/pi-mono
Layer thesis
How to read this part of the ecosystem
This is the shortest explanation of what this layer is for and why it matters.
The official Pi surfaces keep pointing back to a small core: terminal-first interaction, multiple run modes, controllable context, and extension points instead of a long baked-in feature list.
Key artifacts
Best entry points in this layer
These projects explain this branch of the ecosystem fastest.
Work patterns
What people actually do here
These workflow slices connect the layer to real usage patterns.
Workflow pattern
Learn the core loop interactively, then branch out
Most users should start in the TUI and only move into JSON mode, RPC, or SDK embedding once they understand how Pi sessions, context, and extensions actually behave.
Workflow pattern
Script the agent through JSON, RPC, or SDK
A big part of Pi's distinctiveness is that it can stop being a chat app and become infrastructure for bots, scripts, or embedded tooling.
Guardrails
What to remember while exploring
The layer-specific best-practice reminders that keep this branch legible.
Best practice
Start with the four Pi modes before shopping for add-ons
Pi already spans interactive TUI, print/JSON, RPC, and SDK embedding. A lot of ecosystem confusion comes from treating everything as “more features” instead of choosing the right mode first.