Extensions
pi-canvas
Repository: jyaunches/pi-canvas
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.
Pi is unusually explicit that TUI, print/json mode, RPC, SDK embedding, notifications, canvases, and browser-like overlays are alternate surfaces over the same programmable center.
Key artifacts
Best entry points in this layer
These projects explain this branch of the ecosystem fastest.
Extensions
pi-notify-pp
Pi Notify++ is a notification extension for the Pi Coding Agent.
Extensions
pi-gui
pi-remote-web-ui is a minimal, secure web GUI for the pi coding agent.
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
Harden the loop after it proves useful
The ecosystem often starts from speed and composability, then layers in notification, audit, sandboxing, policy, or redaction once the workflow becomes important enough to trust.
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.