Variant / Museum placard & gallery catalogBack to philosophy lab ↗

Awesome Pi Agent Ecosystem

In this framing, Pi is treated as an exhibited body of work rather than a live product surface. The emphasis shifts toward provenance, classification, and curatorial interpretation: what each layer represents, how artifacts relate, and why the ecosystem matters historically.

Accession 01 / Core

Minimal harness

The nucleus of Pi: modes, context, sessions, and a deliberate refusal to become a bloated suite.

Representative objects: pi-mono, pi.dev
Accession 02 / Packages

Behavior as distribution

Skills, prompts, extensions, and themes circulate as reusable artifacts rather than as one sanctioned workflow.

Representative objects: pi-skills, agent-stuff
Accession 03 / Automation

Scaling rituals

Queues, scripts, RPC, and swarms show how the ecosystem escalates from a local loop into operational throughput.

Representative objects: Task Factory, PiSwarm
Accession 04 / Interfaces

Surface experiments

TUI, canvas, notification, and browser surfaces demonstrate that interface is treated as an overlay, not the core identity.

Representative objects: pi-canvas, pi-notify-pp
Accession 05 / Safety

Containment practices

Redaction, boundaries, and auditability arrive as explicit disciplines once power and autonomy increase.

Representative objects: nono, toolwatch
Curatorial note

Why this treatment works

Pi already behaves like a collection more than a monolith. Catalog language makes that truth visible and gives each layer an archival dignity.

Best for source archives, artifact maps, and provenance-rich directories.