Plan before code.
wp blueprint
The plan, its scope and its acceptance criteria are checked into your repository before code is written. A plan moves forward after a recorded review.
What Webpresso does today, grouped by status: Live, Private alpha, Internal and Roadmap. Engineering help is described on the engineering help page.
Live ships in the current wp engine release.
wp blueprint
The plan, its scope and its acceptance criteria are checked into your repository before code is written. A plan moves forward after a recorded review.
wp worktree
Each task gets its own branch and git worktree, so parallel work does not collide. A worktree keeps work apart; it is not a security boundary.
wp qa
Tests, lint, typecheck and audits return compact results with the failing evidence, so your agent reads the failure instead of a full log.
wp review gate
A second agent, from another provider when you have one, reviews the plan and then the finished change. On macOS and Linux, reviewers run with confined file access. The verdict is recorded against the exact change.
wp pr upsert
Your agent opens or updates the pull request through wp, with a disclosure of the session, the models and the review behind it, or the recorded reason one was skipped. You see what was reviewed before you merge.
wp claude, wp codex, wp opencode and wp antigravity start your agent with your repository's settings. wp adds no permission bypass unless you run wp yolo on; your agent's own permission settings stay in charge.
Claude Code, Codex, OpenCode and Antigravity reach the same wp tools, so switching agents keeps your plans, checks and reviews the same.
Private alpha is built and signed but not publicly available.
Built for Apple silicon. Private alpha; not publicly downloadable.
Open your own shell in sessions side by side, for the agent CLIs you use. Desktop passes no provider keys into those sessions; each agent keeps its own login.
Each task's plan from the wp engine, grouped by stage, with work in progress first.
Search past sessions from an index kept on this Mac.
Internal runs only for Webpresso's own projects.
Authorize a GitHub repository and pick the ref and source root. GitHub keeps owning the source.
Each deployment is tied to one commit and its recorded checks.
Roadmap is planned and not available.
The revision, its checks and the deployment record stay reviewable together.
Your app on Webpresso infrastructure, with a custom domain and cost guardrails.
Desktop and the wp engine will ask for your Webpresso account and keep working offline for up to 72 hours between checks. Your agents' provider logins stay with each agent.
Plain-language rules, scoped to paths, that the cross-agent review applies to every change.
A coordinator watches your sessions, checks and pull requests while your Mac is awake and acts only within limits you grant. One list shows what is waiting on you.
An engineer takes your idea to a working app. You review it as a running product, not a spec.
Your app goes live on Webpresso-owned infrastructure with a recorded release.
The same engineer keeps shipping after launch: changes, releases, and the evidence behind them.
An engineer can join your project once paid delivery opens. Today this is interest, not a booking.
This page documents the deploy platform, which runs only for Webpresso's own projects today.
The deploy platform page documents each step.