01 / Core
Minimal harness
Start with the terminal-first center: modes, context, sessions, and the small-core philosophy. Pi makes more sense as a harness than as a finished product.
pi-mono / pi.dev
open layer ↗
PI
Focus.AI Labs / Swiss redesign
May 02, 2026
Pi is a harness, not a finished palace.
This is what the Awesome Pi Agent Ecosystem looks like when you strip away the busier product-shell styling and let the thesis breathe: terminal-first, package-driven, sovereignty over convenience.
Artifacts
108
Seed items
106
Deep profiles
12
Layers
5
Flavor
The Pi ecosystem is less a product family than a culture of composition.
The original Awesome Pi Agent Ecosystem reads Pi correctly: not as a polished, monolithic IDE, but as a minimal harness with just enough primitives to let power users build their own methods.
Seen through a Swiss system, that becomes even clearer. The visual noise drops, the hierarchy sharpens, and the core pitch lands harder: modes, packages, orchestration, interfaces, containment.
So this version is not a replacement for the full ecosystem site. It is an editorial reframe of the same architecture.
Jump to section
Brand diagnosis
Sovereignty over convenience.
That is the cleanest reading of the Pi brand. It flatters terminal-native tinkerers, package authors, and orchestration-minded builders who would rather assemble a sharp workflow than inherit a thick product layer full of hidden defaults.
Promise
Adapt Pi to your workflows, not the other way around.
Aesthetic
Minimal, dry, anti-bloat, builder-first.
Core tension
Power first, safety later.
Closest analogy
Unix-style agent composition, not a finished IDE palace.
Five-layer model
02 / Packages
Reusable behavior as distribution
The real distribution layer is not a single app surface but packages: skills, prompt bundles, themes, extensions, and inspectable patterns you can remix.
pi-skills / agent-stuff / mitsupi
open layer ↗
03 / Automation
Terminal-native scaling
Once the core loop clicks, the ecosystem branches into queues, worktree swarms, JSON mode scripting, bots, and orchestration surfaces.
Task Factory / PiSwarm / pi-mom
open layer ↗
04 / Interfaces
Optional veneers over one programmable center
TUI, print/JSON, RPC, canvases, web overlays, notifications, and GUI wrappers all act like alternate skins over the same machine room.
pi-canvas / pi-notify-pp / pi-gui
open layer ↗
05 / Safety
Containment added deliberately
Pi culture tends to add redaction, approval, sandboxing, and auditability as explicit capabilities once the workflows get serious.
nono / toolwatch / pi-share-hf
open layer ↗
Major projects
Project
pi-mono
The official small-core center of gravity.
Open ↗Project
pi-skills
Shows how reusable behavior actually spreads.
Open ↗Project
PiSwarm
Explains the automation and queue-first branch.
Open ↗Project
pi-canvas
Makes the interface layer legible.
Open ↗Project
nono
Represents the containment instinct once power rises.
Open ↗Where to go next
Use this page like a poster, then drop back into the full directory when you need the inventory.
What this proves
Pi actually benefits from a Swiss treatment because the ecosystem already has a strong thesis. The redesign makes the brand sharper, the layer model cleaner, and the distinction between manifesto and directory easier to feel.
If you wanted, the next step would be a full Swiss port of the multi-page ecosystem — not just this overview, but artifacts, compare, workflows, and best-practices too.