Compared to Claude Code directly, which we also use heavily, p0 keeps very strong coherence from user story, spec planning, architecting, engineering and QA - across many several agents and subagents. Breaking down the work into sequential and parallel task. With Claude Code alone this would be usually requiring lots of hand holding, or be be only partially focussed, rest lost in the woods. Also, we attempted to replicate some of p0 ideas with home grown software dev personas and workflows which fell apart. I think the strong point of p0 is that they really nailed the decomposition and software dev cycle with agents.
Really recommend to try, and at the very minimum you get to make your codebase agent ready if you haven't already.
The standards are synced across the team but you need to use p0 to make full use of them, or at least re-import them into a custom harness.
Slightly disagree on the orchestration. It's not unusual for AI native solo devs to have some self-made harness, but most teams don't have that, and don't have the time to make one. Claude Code etc. only ships the primitives. With p0 you get one out of the box that we have been and keep tweaking.
Only: > We offer a subscription model per team. Token costs for AI models (Claude, etc.) are paid directly via your own Claude subscription or API keys. Reach out for specific pricing based on your team size.
Is it "free" for single developer workflows ?
If the implementation is successful, I'll get paid. Wish me luck! :)
You can use any skill you’d normally add to Claude Code locally, so /counselors should work as well.
In practice this means, you spend much more time defining coding standards and writing product and technical specs (our agents help you with both of course, but you bring the brainpower), and then you hit the button and let p0 build even some seriously large features.
A single markdown file will definitely reach its limits very quickly. We also try our best to provide templates for the standards for the agent to follow in the initial code review and interview with you to make those cover all the basics. Obviously this isn't proprietary to us, just works really well in our opinion.
Curious to give this a spin!
2 - Conceptually stronger starting point leads to better (and larger) feature PRs. Because we help you generate a really strong spec (prod/tech) upfront, grounded across your repos, that changes the process from "build-and-fix-and-build-and-fix" to "define-and-ship".
And we also help you generate strong standards definitions (teach agents how to build things, how to test things) that foundation helps as well.
Our thinking is that you wouldn't use p0 if you are vibe coding a side project, our focus is on folks who need to ship meaty features in existing codebases where the value we generate far outweighs the $100/month.
We debated offering a free tier, but that would have meant offering it with limited functionality, and that would take away from the experience in too fundamental of a way. We want people to have the whole thing.
You can try it for free for 14 days, and we are not locking anything in. Everything lives on your machine and you could move it into your own harness or workflow.
Think of the specs more as feature-specific documents. Like a very well-defined epic or ticket. But the "standards" codebase documentation is kept fresh at all times automatically and agents always reference that.
Does this only work on existing codebases?
We include a couple of templates to make that easier - NextJs + Convex + ShadCn/ui, NextJs + Supabase + ShadCn/ui, etc.
What would you like to see? Other other subs like Codex? Self-hosted?
We've been building p0 because we kept hitting the same wall: AI coding tools are great at generating code from scratch, but can fall flat when shipping complex features into multi-repo codebases with real architecture, real standards, and real constraints. We'd get impressive results at first glance, then spend hours fixing the output to match our actual patterns.
p0 bundles two things: a Mac desktop app and a purpose-built harness that treats feature development as a structured pipeline, not an open-ended chat.
How it works:
You start with a product spec (markdown) or an idea and end up with a set of PRs for all the repos that were touched.
p0 runs through a 5-phase pipeline in isolated Git worktrees:
1. Import your spec, and/or brainstorm with AI to refine it, grounded in your codebase and standards
2. A specialized agent breaks it into phased tickets with technical contracts (acceptance criteria, architecture prescriptions, dependencies)
3. Engineering agents implement tickets in parallel while you watch a live ticket tree and agent activity in real-time... or grab a coffee
4. QA agents run through verification loops to enforce the contracts
5. Refine and create PRs in your repos
Why not just use Claude Code Plan mode / [name your tool]
We actually use Claude Code under the hood. What makes p0 different from Claude Code CLI / Conductor / etc. is our focus on shipping complex features autonomously, across all your existing repos.
Spec first -- Puts humans in control of as much product and technical details as you can imagine, and we help you create/refine with agents grounded in your codebase.
Contracts and QA loops -- We generate clear acceptance criteria and boundaries for each task. QA loops make sure they were adhered to.
Ticketing -- The architect breaks every feature into phased tickets with dependency ordering. This isn't just a simple plan, it allows us to break complex problems into smaller, context-fitting tickets, and bring them back together into one cohesive implementation.
Subagents -- Nothing fancy here, just a set of roles we've fine-tuned for months, so you don't have to start from scratch.
Standards -- Typical coding agent behavior is to get a cursory (haha) understanding by reading code. But that clogs up context quickly, and rarely rises to the architecture understanding level. When you first launch p0, we'll help you generate a better AI-targeted documentation.
Multi repo -- The whole harness is multi-repo aware. It maintains cross-repo context (imports, API contracts, shared types) and creates coordinated worktrees across all your repos in a single session.
Local-first, team features through the cloud:
All code stays on your machine on isolated worktrees. We do sync codebase documentation and workspace setup through our cloud so your teams can share those for convenience. And of course the prompts go to Anthropic's API.
Limitations:
- The spec-driven workflow has a learning curve. If you're used to the "chat away as you go" flow, the structured planning is a new thing to get used to. - macOS only right now, Linux/Windows are on the roadmap. - Works best for substantial features -- for small features, you're better off using Claude's plan mode. - Requires a Claude subscription or API key and works best with high limits / the 20x plan. Everything is finetuned for Claude 4.6 Opus right now. We plan on supporting other providers, but Claude is where the quality bar is.
What we'd love for you to try:
Is the spec-driven workflow helpful in building larger features? Did we miss anything? What integrations matter most? (We support GitHub, Gitlab, Linear right now)
You can download p0 at https://www.bepurple.ai. Happy to answer any questions about the architecture or approach.
