A developer shares why Pi, a minimal coding agent built on four primitives (read, write, edit, bash), resonates with them over more opinionated alternatives like Claude Code. The post argues that small, composable primitives with visible behavior and honest extension points make for more durable, adaptable tooling. The author draws parallels to Unix and Emacs philosophy, explains how Pi integrates naturally with Nix and Emacs workflows, and describes building their own minimal Rust coding agent (OneLoop) to internalize the same design principles. Key insight: the hard parts of a minimal agent are infrastructure problems (context truncation, output formatting, session persistence), not agent design problems.
Table of contents
Small primitives, visible behaviorWhere Pi fits in the way I already workExtensibility I can actually useThe honest trade-offsPutting my money where my mouth isWhy this matters beyond PiFootnotes:Sort: