Today p0 runs on Windows. Here’s how that timeline actually looked.
The week, end-to-end
- Friday. Two customers — independently, within a few hours of each other — asked us when p0 was coming to Windows. We’d been hearing the question for a while. This was the second time it landed on the same day.
- Monday. We bought a Windows laptop at Best Buy. No procurement, no IT ticket, no plan beyond “we should probably have one in the office.”
- Tuesday + Wednesday. p0 built the Windows version of itself. On a Mac. The orchestrator ran the spec, fanned out senior-engineer agents across the cross-platform plumbing, the installer, the file-watcher quirks, the path normalization edge cases — the kind of work that historically takes a small team a quarter.
- Thursday (today). PRs merged. Homepage updated. Shipped. The first clients are already using it to ship Windows products.
Why this matters
Five days from “two customers asked again” to “it’s live and clients are shipping with it.” That’s not a story about how fast we type. We didn’t type much at all. It’s a story about what the workflow makes possible when the agents do the work and a small team focuses on judgment — what to ship, in what order, to what bar of quality.
The Windows build is genuinely complex. Cross-platform tooling, OS-level integrations, an installer pipeline, the long tail of “this works on macOS but not on Windows” footguns. p0 handled most of it. Where we had to step in, it was to make taste calls — not to debug missing semicolons.
What this means for our customers
If you’re a Purple customer and you’ve been waiting for something — a feature, a platform, an integration, a fix — the answer is probably “sooner than you think.” Tell us. We move at the speed our customers move. The Windows build is proof.
We didn’t write a Windows app. We let p0 do it. That’s the part that should land.
— Mario