Your IDE just hired a team
Wakii is an agentic IDE with a built-in superpowers team — plugin bundled, kit auto-installed to ~/.claude, enabled by default. Describe an idea and the pipeline runs: plan, parallel agents, verify gates, one clean PR.
Watch the team work
Every cell below is a live piece of the Superpowers panel, mid-flight on a real story. Hover to pick one up — this is what "agentic IDE" actually looks like.
Bundled plugin
Superpowers ships inside the app. No marketplace, no version juggling.
Kit auto-installs
Skills land in ~/.claude on first launch. You never touch a config file.
Enabled by default
The team is on when you open Wakii. Opt out per-project — not opt in.
cat workflow.md
One pipeline from spoken idea to merged PR — visible end to end in the Superpowers panel.
Nine role-gated agents run every story. Analysts frame the problem, critics attack the spec and the plan, an executor builds in an isolated worktree, a designer prototypes the UI before code — and an independent reviewer plus a verifier check everything the executor claims. No agent approves its own work.
Every sub-feature passes the Story Ops gates before it counts. Gates are tool-enforced — a gate that could self-approve would not be a gate.
A real three-tier walkthrough — DOM, screenshots, click-through flow — before anything is called done.
Implementation complete, tests green on the touched surface. No green, no gate.
Every plan step ticked off with evidence — nothing silently skipped.
An independent reviewer attacks the diff: bugs, security, scope creep.
Merge into the story destination branch, audit trail recorded.
The issue closes only after verification is clean — tracking truth matches the repo.
Eight pillars, one pipeline
The mechanics are public — the reasons they are built this way matter more. Condensed from the full story workflow; each pillar has a deeper write-up in the docs.
Deep analysis is expensive, so it runs exactly once at the epic level — every sub-feature inherits the results through a context pack.
The PM specs but never codes; the developer builds but never approves its own work; the tester hunts failures but never fixes them.
Tool-enforced gates plus a real browser walkthrough demand evidence — "the agent says it works" is not a verdict.
Architecture decisions and the merge to your branch are human gates — nothing irreversible happens without a person saying yes.
Dependencies are explicit tiers; every tier merges into one story branch, so parallelism never means divergent histories.
A silent agent might be running a long build — the watchdog checks three layers before resuming a stall from its last good state.
Every task ends with a ritual — what broke, what fixed it — so the next story starts smarter instead of rediscovering the same trap.
The workflow assumes it will be the one making the mistake — so mistakes are cheap, visible, and revertable by default.
get wakii
Installers for macOS and Windows, or build from source — and a mobile companion for your agent team.
Wakii is a desktop app built from an open repo. Three commands from clone to the Superpowers panel — no configuration along the way.
read the guideA companion app for iOS and Android — check on your agents, approve gates, and send tasks from anywhere.
Prefer an installer? Grab Wakii for macOS or Windows straight from the download page.
frequently asked
Is Wakii really zero-setup?
How is this different from an AI plugin in my editor?
What does "one PR per story" mean?
What is Wakii's relationship to Orca?
only the short version — the full FAQ