Pi 1.0
- ID
- 30984
- Status
- summarized
- Published
- 02 Oct 2026, 3:33 AM
- Fetched
- 02 Oct 2026, 3:20 PM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://earendil.com/posts/pi-1-0/
- Source URL
- https://hnrss.org/best
Summary
- Score
- 7.5
- Created
- 02 Oct 2026, 3:21 PM
- Tags
- Audience
- developersai_agent_usersai_ml_learnerssaas_founders
What happened
Earendil shipped Pi 1.0, a self-described 'hardened, minimal, extensible agent harness,' adding Codemode (native MCP support plus non-LLM models like Jev and image models), virtual-model extensions, deferred tool loading, cache warming for Anthropic models, mid-conversation system messages, a new TUI theme, and full-screen mode by default. Alongside it, Earendil released Pi Durable, an experimental package for building long-running agentic applications that it says shares Pi's minimalism but targets longer conversations and tasks outside the terminal. The post claims hundreds of thousands of weekly Pi users and says features were only adopted after months of being 'thrown up against the wall,' with a longer list of rejected ideas. The HN thread drew 1108 points and 344 comments.
Why it matters
If you run coding agents against Anthropic models, cache warming and deferred tool loading are the two items here that touch your token spend and startup latency directly, and mid-conversation system messages change what you can do mid-transcript when swapping prompts or tool sets in a long session. Codemode adding native MCP support means an existing MCP server setup may work without a separate bridge, which is worth testing before writing glue code. Pi Durable is explicitly labelled experimental, so treat it as something to prototype on rather than to put a production long-running workload behind. Nothing in the text states any Malaysia- or Southeast Asia-specific pricing, hosting, or policy angle.
Discussion angle
Earendil's stated policy is to wait until a feature 'has proven itself' before adopting it, and this 1.0 is the payoff of that filter. Compare that with harnesses that ship weekly: which of these seven additions would you actually adopt today, and does the deferred-tool-loading plus cache-warming combo hold up when you measure it against your own agent's latency and token bill?