@pidotdev: Read the full blog post here
Summary
A blog post highlighting Pi, a minimal coding agent harness, arguing that its simplicity yields better performance and lower cost compared to more complex tools, supported by Databricks benchmark results and Shopify's Pi Autoresearch case study.
View Cached Full Text
Cached at: 08/05/26, 08:25 AM
Read the full blog post here
https://t.co/AEbmCZI1fE
Pi, Minimal and Performant | EARENDIL
Source: https://earendil.com/posts/pi-autoresearch-and-databricks/
Pi’s Minimalism Is Its Advantage
AI has made code cheap, and as a result many companies are building bigger tools in pursuit of better performance. Larger prompts, more orchestration, more layers, more complexity. This also makes these tools intrinsically more expensive to use. Pi takes the opposite approach.
Pi is the coding harness that chooses minimalism on purpose. It comes out of the box with only 4 tools, and itssystem promptand tool definitions come in below 1,000 tokens. The idea being that most work can be done with the basics, and if you want more, build it.
Evidence increasingly suggests that Pi’s design is not just cleaner; it’s cheaper and more performant. Users are finding that vanilla Pi produces industry leading results, even before adding on extensions to match user specific workflows and needs. As we’ll see in case studies of Databricks and Shopify, Pi produced ideal outcomes for both.
Case Studies
Databricks Study: Cost Per Task
Databricks recently shared their findings “Benchmarking Coding Agents on Databricks’ Multi-Million Line Codebase.” The goal of their research was to understand which coding agents offer the best performance on real-world coding tasks, and how task-performance varies with price.
To avoid bias from externalbenchmarks that have become oversaturated, they created their own based on tasks their team of engineers regularly performs. The results match what we would expect, but what many in the industry may have been surprised to learn. In their words, “...the harness a model is called from dramatically impacts cost and quality,” and, “in many cases, simple harnesses like Pi performed best on our workloads.”
Figure made by Databricks.When combined with Opus 4.8, xhigh, Pi had the highest overall pass-rate, at a significantly lower cost than both Claude Code and Codex.
Minimal harness, measurable effect
Pi shines because it doesn’t try to wrap the model in a bunch of defaults and instructions that get lost in theinstruction hierarchy. Instead, Pi stays out of the model’s way, and the team is able to add what they actually need for their workflow.
Databricks’ study is insightful because it separates model from harness.
They reported that when they ran the same model with the same thinking effort through different harnesses, “the cost per task differed significantly (more than 2x in some cases), while quality remained the same”. We call this Pi’s “context discipline”. “Pi sent about 3x less context per turn. It managed context better, keeping a tighter working set and finishing the tasks in fewer runs.”
We agree that one must take into account end-to-end engineering economics, and not just price per token. And this is also true at the model level; we have observed, for instance, that running complex workflows on Haiku 4.5 was often more expensive than Sonnet 4.6, especially when code execution was involved, simply because the agent required more turns to complete the task successfully.
Now we see this at the harness level too; stronger, more expensive models with a performant harness can be cheaper than the converse.
Shopify builds Pi Autoresearch: Extensible beats bloat
Minimalism is part of Pi’s core philosophy. What makes this work is that minimal does not mean inflexible. In fact, it is the first widely used agentic infrastructure created for extensibility and self-editability.
Another insightful external validation of Pi’s design comes from Shopify. In this post fromShopify Engineering, David Cortés describes buildingpi\-autoresearchdirectly as a Pi extension, by simply asking “Pi, [to] create an extension for Autoresearch...”. Pi reads its own extension documentation and starts building a new workflow from there.
Autoresearch is an autonomous loop for optimization with coding agents. When you ask for a change, it runs experiments to find out what works and what causes regressions. For as long as the target is measurable, it can throw out these regressions and keep self-improving.
For Shopifyand others, the Autoresearch extension quickly became a serious internal productivity tool. Shopify reported cases including unit tests running “300 times faster,” React component mounting “20% faster,” reduced build times across multiple projects, and even improvements to pnpm performance.
Image from Shopify’spi-autoresearch GitHub repository.The important point here is that Pi doesn’t ship any of these tools out of the box. Instead, it makes it ridiculously simple for you to build them. Instead of assuming the vendor knows your workflow and trying to ship every tool under the sun, Pi assumes you know best, and gifts you extensibility to wield and craft your own workflow.
Why minimal wins now
About a year ago, an argument could be made for native harnesses having a structural advantage over all others, because models were built around them. However, this argument has gotten weaker.
Frontier models are now generally very competent at understanding a terminal (or terminal-style) coding environment, and acting within it.Anthropic recently cutting down Claude Code’s system prompt by 80%is a clear sign of this. So the question is becoming less about how native the harness is, and more about how it handles context to avoid redundancy and act with clean primitives. Models need a clean interface to the environment, and a harness that does not waste context.
Pi provides this: less prompt overhead and repeated context, cheaper runs, fewer unnecessary abstractions. Because it is extensible, you do not lose power, but gain selectivity. You add complexity only when it “earns its keep”.
We are also seeing local models developing fast, and atEarendilwe find them very promising. Pi’s context discipline is especially an asset here. Local models usually have lower context windows, andprefillcan take a long time, so preserving a stable prompt prefix matters. Context discipline means we do not change the context without the user explicitly asking for it, avoiding minute-long re-prefilling. Combined with the minimal default system prompt and tool set, this makes pi an ideal harness for local models.
Pi is proving that it can manage it all. To be cheaper, minimal, and more performant.
Similar Articles
Pi's Minimalism Is Its Advantage
Earendil's Pi coding harness demonstrates that minimalist design outperforms complex alternatives in cost and performance, citing Databricks benchmarks and a Shopify case study as evidence.
@MaximeRivest: Pi coding agent is very often the best for its price. Pi's system prompt is very short and has only 4 tools. My Pi syst…
Maxime Rivest shares tips for optimizing Pi coding agent usage with custom system prompts, and Matei Zaharia discusses surprising results from benchmarking coding agents at Databricks.
@yibie: Databricks tested various coding tools with real tasks from their own team—conclusion: the same model called from different harnesses has a per-task cost difference of more than 2x, while quality is the same. "Pi: Minimalism and High Performance" Pi's minimalism is its advantage AI makes code cheaper, and as a result many companies build bigger...
Databricks' benchmark shows that the same model invoked through different harnesses has a cost difference of more than 2x, while Pi, as a minimalist coding harness, delivers high performance at low cost; Shopify also used Pi to extend Autoresearch and improve efficiency.
@_alejandroao: I just recorded a deep dive into Pi's architecture. It's a minimalist AI coding agent with a beautiful design. Here's h…
A deep dive into the architecture of Pi, a minimalist AI coding agent, explaining how it works.
@aehyok: I just started using Pi recently, and I really love its minimalism and high degree of freedom, which lets me assemble it however I like Since I'm just getting started, based on my initial experience and the docs I've gone through, I put together a quick overview of the most basic features Pi Agent provides 👇 1. First off, a complete Agent loop Calls the model, executes tools, hands results back to the model — looping until the task is done You can also chime in mid-loop to steer or correct, or just interrupt it 2. Only 4 tools enabled by default read: reads files and images bash: executes commands edit: makes precise file edits write: creates or overwrites files Don't let the small number fool you — it's more than enough, since grep, find, curl, etc. can all be run directly through bash 3. Plus 4 built-in tools, disabled by default grep, find, ls, and PowerShell on Windows You can turn them on with a single command: pi --tools +grep,+find,+ls You can also enable just read, grep, find, and ls to create a read-only Agent that only reads code and never modifies it 4. MCP is now built in No need to install any extra plugins — just use `pi mcp add` to add an MCP server and it works Note: Pi itself has no web search. If you want it to look things up online, you'll need to connect a search-type MCP or another tool yourself 5. Supports Skills Uses the same SKILL.md format as Claude Code — normally only the name and description are given to the model, and the full content is loaded only when needed, which saves a lot of context However, it doesn't read .claude/skills by default. You need to add a line in ~/.pi/agent/settings.json: "skills": ["~/.claude/skills"] 6. Can read CLAUDE.md It reads AGENTS.md or CLAUDE.md from the current directory and parent directories But if both exist in the same directory, only AGENTS.md is read It also doesn't read ~/.claude/CLAUDE.md — global instructions need to go under ~/.pi/agent/ I looked at the code, and CLAUDE.md isn't handled separately — it's just in the same filename list as AGENTS.md. So the @ references from Claude Code aren't supported either 7. Other basic capabilities are all there Switch models at any time Sessions can be forked and rolled back Context is automatically compressed when it's nearly full Supports CLI, RPC, and SDK invocation ⚠️ What's NOT included by default Sub-agents, plan mode, todo lists, permission confirmation — none of these are built in However, the official repo's examples directory has example extensions for each of these, so you can install them if you're interested, or just ask Pi to write one for you So I see Pi more as a clean Agent foundation — it has all the basics you need, and you build the rest on top to fit your own workflow That's exactly why I like it most: the more capable the model gets, the simpler I think the Harness should be — no need for all those flashy features
作者分享了刚上手 Pi Agent 的体验,梳理了它提供的基础功能:完整的 Agent 循环、read/bash/edit/write 四个默认工具、内置 grep/find/ls 等可选工具、内置 MCP 支持、兼容 Claude Code 的 SKILL.md 格式与 CLAUDE.md 读取,以及多模型切换、会话分叉、上下文压缩等能力,认为 Pi 是一个极简、高度自由的 Agent 底座。