Surfaced 2026-10-02T00:54:09Z — First-party release announcement, formatted as a memo ("From: Earendil <
[email protected]> ... Subject: Pi 1.0"): "Today we are proudly shipp — Pi Durable graduated from description-only to independently evidenced: its own front-page thread brings technical scrutiny (JSON-only state, outbox-sync critique) and a third party who had already built his own durable layer for Pi and may now replace it, while the main launch thread holds 99.5th-percentile velocity at ~34h. The case is now a corroborated, accelerating two-part launch — hardened harness plus durable substrate — rather than an announcement with buzz; resolution still turns on sustained adoption, not launch attention.
Earendil — the AI company of Armin Ronacher, who with Colin Daymond Hanna acquired the Pi coding agent in April 2026 — shipped Pi 1.0 on 2026-10-01, a 1.0 of the deliberately minimal coding-agent harness whose headline is a reversal: after a year of arguing 'you might not need MCP,' it now ships MCP by default through Codemode, where the agent writes sandboxed JavaScript that calls tools directly (including non-LLM models like a Jev classifier and image models), alongside virtual-model routing extensions, deferred tool loading, Anthropic cache warming, and transcript-aware mid-conversation system messages. In the same release Earendil shipped Pi Durable, a separate experimental MIT-licensed package (@earendil-works/pi-durable) pitched as a substrate for long-running agentic applications — storage, crash-resume, forks, multi-client steering, background compaction — kept out of Pi proper so the coding agent stays minimal. Both topped Hacker News (main thread 1,600+ points, Durable thread ~500) and a small third-party ecosystem formed within days — connectors, a self-hosted sandboxed runner, editor integrations — but the supplied material shows no production durable-runtime deployment. Coverage repeats Earendil's 'hundreds of thousands of weekly users' claim without independent verification (the case itself records unanswered pushback), and the snippets leave the relationship between Earendil and Pi's original creator Mario Zechner — who once publicly dismissed MCP — thin, citing only a Register writeup framing the acquisition.
A consequential practitioner — Ronacher's Earendil — shipped at 1.0 what Scott's canon already argues: Codemode is his hybrid-architecture/code-first pattern (MCP as transport beneath model-written JS, progressive discovery via deferred tool loading), cache warming and prefix-preserving system messages operationalize prefix-caching-economics as harness defaults, and virtual-model per-request routing makes the Model Barbell a harness extension API — a dated-receipts convergence worth publishing against. Pi Durable separately productizes the long-running-agents external-state kernel right beside his own resumable-job control-plane work (dev:project.proposal's FastAPI job identity/recovery/resume layer), so durable-side adoption — still zero production reports — is the part that would actually change what he builds.
ip:framework.code-first-architectureip:source.why-code-execution-beats-mcpip:concept.hybrid-architectureip:concept.prefix-caching-economicsip:concept.model-barbellip:framework.long-running-agentsdev:concept.resumable-agent-job-control-planedev:project.proposalradar:openai-programmatic-tool-callingradar:kiss-rust-agent-harnessradar:hermes-missions-durable-agent-executionradar:cache-tax-idle-session-warmingradar:claude-code-auto-mode-defaultradar:multi-model-orchestrator-worker-agents
queries asked of Scott's wikis
- code execution beats MCP tool schemas code-first agent
- prompt cache warming prefix caching economics harness cost
- minimal agent harness bloat philosophy sub-agents plan mode
- durable execution long-running agent checkpoint crash resume outbox
- virtual model routing per-task model selection agent
- sandboxed code execution tool security permissions agent
| source | object | author | score | comments |
|---|
| 🟧 hn | Pi 1.0Retrieved article excerptOpen article · Retrieved 2026-10-01T20:35:54.970243+00:00 # Pi 1.0
Date:Thu, 01 Oct 2026
From:Earendil <[email protected]>
To:You
Subject:Pi 1.0
Today we are proudly shipping Pi 1.0: a hardened, minimal, extensible agent
harness that you can make your own. Hundreds of thousands of people around the
world use Pi every week. Many of you submit issues and pull requests. Over the
course of many months, we have used that feedback to improve, harden and evolve
Pi into a stable piece of software that people and businesses can depend on.
Pi is known for being minimal. We care about holding that line. While agentic
tooling changes every week, many of the changes do not last. Pi does not work
that way. We wait until something has proven itself, and only then do we
consider adopting it; weighing its true functionality against its inherent
added complexity. We spoke more about that process and how it relates to
Codemode and MCP earlier this week [here](https://earendil.com/posts/you-said-no-mcp/).
The Pi 1.0 we are shipping today is a result of that process. Pi already ran
the latest models from every major provider, became a daily driver coding agent
for people around the world, and provided a supermalleable substrate on which
to build agentic applications. With Pi 1.0 we are adding the following into Pi:
- Codemode (native support for MCP, and non-LLM models like Jev and image models)
- Extension support for virtual models
- Deferred tool loading
- Cache warming for anthropic models
- Mid-conversation system messages (transcript-aware prompt and tool changes)
- A new TUI theme
- Full-screen mode by default
We have thought about many of these features for months. They were thrown up
against the wall and stuck. The list of things that fell off the wall is much
longer. When we use Pi with all these new features it feels like a major step
forward, but it also still feels simple, like Pi.
Alongside this work of continually refining and evolving Pi, we also began to
understand that there were aspects of Pi that did not fit the shape of how many
people wanted to use it. At Earendil, we want to bring Pi's minimalism and the
way it allows you to wield AI outside of the coding agent and outside of the
terminal. It needs to be reachable from different surfaces and support
longer-running conversations and tasks. In short, Pi must become more durable.
Rather than stray from our minimal roots and try to make Pi something it
wasn't, we combined that work into a new experimental package that we are
shipping today, Pi Durable. Pi Durable is a new substrate for building
long-running agentic applications that lets the builders and the users of those
applications wield and steer the underlying intelligence with tremendous
dexterity. It shares Pi's key principles, minimalism and supermalleability, but
it extends those principles into new dimensions. Mario writes in more detail
about how we crafted Pi Durable [here](https://earendil.com/posts/pi-durable/).
Earendil was formed to craft software and open protocols that strengthen human
agency. Today we are shipping tools to you all to help do just that. We're
eager to hear feedback from you and to harness the future out in the open
together.
Pi 1.0 is available today:
```
curl -fsSL https://pi.dev/install.sh | sh
```
or on Windows
```
powershell -c "irm https://pi.dev/install.ps1 | iex"
```
Pi Durable is available today as an experimental package:
```
npm install @earendil-works/pi-durable @earendil-works/pi-ai @earendil-works/chord
```
Both are MIT licensed. Documentation is at [pi.dev](https://pi.dev). Code is at
[github.com/earendil-works/pi](https://github.com/earendil-works/pi).
1. Codemode: Pi writes a script that boils a week of commits down to a short summary
2. Pi writes itself an extension: a virtual model that plans with Claude Opus and implements with GPT, with Jev deciding when to switch
3. Reload, start a new session, and pick the new `router/auto` model
4. Planning runs on Claude Opus
5. Jev spots the switch to implementation and hands over to GPT 6 Luna
6. `!` runs the finished script
7. `/session` breaks down cost per model and cache use | sergiotapia | 1687 | 609 |
| 🟧 echo.blog ⭐ | First-party release announcement, formatted as a memo ("From: Earendil <[email protected]> ... Subject: Pi 1.0"): "Today we are proudly shipp | Earendil (Earendil Inc.) | — | — |
| 🟧 hn | Pi Durable | paulsmith | 512 | 75 |
| 🟧 hn | Pi v1.0.0 | bjornroberg | 12 | 2 |
| 🟠 reddit | Pi 1.0 released - MCP support now included by default LocalLLaMA | psychohistorian8 | 452 | 139 |
| 🟧 hn | Show HN: Use all Codex Plugins inside Pi | alexandroskyr | 22 | 2 |
| 🟧 hn | Show HN: Delegate Claude Code's work to pi and a cheaper model | jannniii | 1 | 0 |
| 🟧 hn | Show HN: pi pod – run your pi coding agent in sandboxes on your own server | edverma2 | 121 | 48 |
| 🟧 hn | Show HN: Pi Durable and Nostr | jonstaab | 2 | 0 |
| 🟧 hn | Vim-pi-chat: make Vim a pi-powered editor | me2too | 1 | 0 |
| 🟠 reddit | Pi and mini-swe-agent passed 9/9 checks each in my latest experiment. A second code review still found defects in both. LocalLLaMA | Mysterious-Desk-3492 | 0 | 2 |
| 🟧 hn | The immortal life of Pi (Running the Pi coding agent on Temporal) | bnerual | 14 | 0 |
| 🟧 hn | A governed cloud coding agent for teams, built on Pi | nnww | 3 | 0 |
2026-10-10T03:21:10Z
Harness-side adoption adds a governed cloud coding agent (Show HN, 3 pts), but durable-side production adoption remains at one major platform (Temporal); resolution still waits on sustained durable-runtime deployments beyond a single integration.
2026-10-10T01:44:12Z
evidence attached: hn.story.50027055 — Governed cloud coding agent for teams built on Pi demonstrates early adoption of the Pi harness beyond its maintainers.
2026-10-09T03:23:10Z
Temporal — a major durable execution platform — published a blog post demonstrating the Pi coding agent running on Temporal infrastructure, directly addressing the case's core resolution gap (zero production durable-runtime reports for Pi Durable). This is the first credible durable-side production integration, not just a community artifact. Launch attention remains spent (2.3 pts/h at 204h), but the durable-adoption criterion now has a consequential data point.
2026-10-08T23:06:44Z
evidence attached: hn.story.50011940 — Temporal blog post demonstrates Pi coding agent running on durable execution platform, directly corroborating the Pi 1.0 case's claim of hardened long-running agent infrastructure.
2026-10-06T22:19:58Z
The case gains its first independent comparative evaluation: an external 10-harness benchmark scores Pi 9/9 checks (tied with mini-swe-agent), caveated by second-pass defect findings — harness quality now has third-party validation to sit beside the ecosystem artifacts, making it six periphery artifacts. But Durable's side of the resolution criterion is untouched (one tractionless Nostr artifact, still zero production durable-runtime reports), so the case's meaning is unchanged: resolution waits on weeks-scale durable-side production adoption. Heat stays low despite the magnitude-valve spread reading because that top-decile footprint is the launch window's lifetime echo — current rates are dust (0.17 pts/h, 0 comments/h, 35th percentile, pi pod +6 pts on flat comments).
2026-10-06T20:42:17Z
evidence attached: reddit.post.1wzb71t — Independent multi-harness coding experiment exercising Pi against nine other harnesses, with Pi passing all checks (caveated by a second-pass review finding defects).
2026-10-05T08:47:03Z
grounded: converges/high — A consequential practitioner — Ronacher's Earendil — shipped at 1.0 what Scott's canon already argues: Codemode is his hybrid-architecture/code-first pattern (M
2026-10-05T08:39:23Z
The 'Jev material development' screen resolves as comment drift inside the fully cooled launch thread — no new source, artifact, or release attached — and pi pod's inch-up to 115/47 is the only live signal in a case now reading 0.0 pts/h at ~115h age; the case's meaning is unchanged: an established, corroborated release whose resolution waits entirely on durable-side production adoption evidence over weeks.
2026-10-04T08:28:34Z
Both sensor fires resolve to pi pod — the one third-party artifact with real traction (94/39) — drawing a brief comment-driven resurgence (~8.7 pts/h transient against a dormant age cohort) while every launch thread keeps decaying (~3.2 pts/h case-wide vs ~304 peak, 1.5 comments/h); no new artifacts, no durable-side movement, so the case's meaning is unchanged: an established release whose resolution waits entirely on weeks-scale durable-adoption evidence, and the spikes price as an ember, not a re-spread — hence heat stays low despite the 76th-percentile peer reading, which is one warm object in a cohort of corpses.
2026-10-03T07:15:40Z
The periphery ticked to a fifth tractionless harness-side artifact (Vim editor integration, 1 pt/0 comments) while the velocity-spike sensor fire resolves as launch-tail decay — Reddit +8 pts in ~40h, 0 comments/h, ~3.7 pts/h case-wide against a ~298 peak; the case's meaning is unchanged: an established release whose resolution waits entirely on durable-side production adoption over weeks.
2026-10-03T06:30:14Z
evidence attached: hn.story.49941233 — Third-party Vim integration is early ecosystem-adoption evidence for the Pi minimal-harness line this case tracks.
2026-10-03T05:38:47Z
Pi Durable gets its first third-party artifact (Nostr wiring, 1 pt/0 comments) — the durable side's first adoption data point of any kind — just as launch attention collapses to ~1.7 pts/h across all evidence with the periphery paused since pi pod; the case's meaning shifts from 'launch with ecosystem forming' to 'established release whose resolution now waits entirely on weeks-scale adoption evidence,' so state settles from accelerating to corroborated and heat cools to low.
2026-10-02T22:26:24Z
evidence attached: hn.story.49939061 — Third-party Show HN wiring the Pi Durable package to Nostr is exactly the adoption evidence that case's resolution hinges on.
2026-10-02T20:18:11Z
A third independent artifact in 72h — pi pod, a self-hosted sandboxed server runner for the pi agent — extends the forming ecosystem toward infrastructure use adjacent to the durable hypothesis, while Reddit re-spiked above its platform p90 even as the HN launch thread cools (~44 pts/h vs ~296 peak); the spread reading keeps heat at medium-plus, not low. The case's meaning holds at 'ecosystem forming around the harness', but durable-side evidence remains absent — still zero production durable-runtime reports, so resolution still waits on sustained adoption of BOTH the 1.0 harness and Pi Durable.
2026-10-02T19:29:58Z
evidence attached: hn.story.49937304 — Third-party self-hosted sandbox runner built on the pi coding agent is direct ecosystem-adoption evidence for whether the Pi harness line became durable agent infrastructure.
2026-10-02T13:28:18Z
Launch attention is past peak and visibly cooling (~285 → ~90 pts/h into hour 47) while the periphery keeps expanding: a second independent third-party artifact in 48h — offloading Claude Code work to pi on a cheaper model for up to 33% savings — shows pi being adopted as a cost substrate under other harnesses, not only as a daily driver. The case's meaning shifts from 'dominant launch' to 'launch cooling as the extension ecosystem begins to form'; resolution still waits on sustained production adoption of both the 1.0 harness and Pi Durable, not attention.
2026-10-02T13:24:53Z
evidence attached: hn.story.49933095 — Independent tooling built on the pi harness as a cheap offload substrate under Claude Code is early third-party adoption evidence for the minimal-harness line.
2026-10-02T05:16:12Z
The first third-party ecosystem artifact — a connector running all Codex plugins inside Pi — appeared within ~48h of launch, the earliest concrete instance of the extension ecosystem the resolution criterion watches for, but it is one thin Show HN (4 pts, 0 comments) and everything else added is amplification. The case's meaning is otherwise unchanged: a two-part launch still holding ~194 pts/h across three platforms whose resolution waits on sustained production adoption of both harness and Pi Durable, not attention.
2026-10-02T04:27:22Z
evidence attached: hn.story.49929381 — Third-party connector wiring Codex plugins into Pi is ecosystem/adoption evidence for the minimal-harness line, and flags unauthenticated local plugin endpoints.
2026-10-02T02:16:02Z
The launch is holding anomalously long — near-peak velocity into a second day at the 99.7th peer percentile and spreading to Reddit — but everything added since the last look is amplification and user anecdotes, not new substance. The case's meaning is unchanged: a two-part launch whose resolution still waits on production adoption of both the harness and Pi Durable, not on attention.
2026-10-02T01:27:07Z
evidence attached: reddit.post.1wvffcr — shared external link with case evidence
2026-10-02T00:44:50Z
Pi Durable graduated from description-only to independently evidenced: its own front-page thread brings technical scrutiny (JSON-only state, outbox-sync critique) and a third party who had already built his own durable layer for Pi and may now replace it, while the main launch thread holds 99.5th-percentile velocity at ~34h. The case is now a corroborated, accelerating two-part launch — hardened harness plus durable substrate — rather than an announcement with buzz; resolution still turns on sustained adoption, not launch attention.
2026-10-01T23:31:30Z
evidence attached: hn.story.49927682 — The Pi v1.0.0 release surfacing on HN is direct launch-spread evidence for the open case tracking whether Pi 1.0 becomes durable agent infrastructure.
2026-10-01T23:31:30Z
evidence attached: hn.story.49925969 — HN front-page launch of Pi Durable is direct first-party, high-attention evidence for the open Pi 1.0/Pi Durable adoption case.
2026-10-01T21:48:44Z
origin walked (opencode/cheap-glm, conf 0.95): anchor hn.story.49926069 -> echo.blog.1d001431f6 by Earendil (Earendil Inc.)
2026-10-01T21:19:31Z
grounded: converges/high — Pi 1.0 independently ships Scott's Code-First Architecture nearly feature-for-feature — Codemode model-written-JS orchestration, deferred tool loading, idle cac
2026-10-01T21:11:18Z
case created — Major first-party release on a hot harness topic with front-page traction; Pi Durable extends the claim into Scott's long-running-orchestration interest.