Pi

About

pi grew out of Mario Zechner's argument that coding agents had become opaque products, and its design publishes everything as inspectable, replaceable parts: a coding-agent CLI, a core runtime with tool calling and state management, a unified multi-provider LLM API, a terminal UI library, and telemetry contracts, each independently consumable. The agent is self-extensible by design — users add tools, skills, and extensions at runtime, and a large third-party ecosystem of memory systems, shells, GUIs, and Emacs/Neovim front ends has grown on those interfaces. Security posture is explicit rather than implicit: no built-in permission system, with documented paths for running inside a Gondolin micro-VM, Docker, or OpenShell sandbox, plus aggressive supply-chain hardening (pinned deps, min-release-age, --ignore-scripts). Maintained actively by earendil-works with public RFCs and a Discord community, pi serves developers who want a minimal, inspectable agent they can extend rather than a managed product.