Claude Code Ultraplan and Ultrareview: Cloud Power Tools

Ultraplan and ultrareview are Claude Code's two cloud power tools: /ultraplan drafts a plan for a big change in a Claude Code on the web session while your terminal stays free, and /code-review ultra launches a fleet of reviewer agents in a cloud sandbox to find verified bugs before you merge. One plans the work, the other checks it.

I'm Evgeny, and I'll be honest: these two features sound like they're for engineering teams, but they solve a very non-programmer problem — "I can't tell if the AI's plan is good, and I can't tell if its code is safe." Ultraplan gives you a plan you can read and comment on in a browser like a Google Doc. Ultrareview gives you a bug report where every finding was independently reproduced. Both are training wheels for judgment you don't have yet.

What is ultraplan in Claude Code?

Ultraplan hands a planning task from your local CLI to a Claude Code on the web session running in plan mode. Claude researches your codebase and drafts the plan in the cloud while you keep working in the terminal. It's a research preview, needs Claude Code v2.1.91 or later, a Claude Code on the web account and a GitHub repository, and it doesn't work on Bedrock, Vertex, or Foundry. If you don't have a cloud environment yet, ultraplan quietly creates one on first launch.

How do I use ultraplan?

Three ways in: run the /ultraplan command with your prompt, simply include the word "ultraplan" anywhere in a normal message, or — my favorite — when Claude finishes a local plan and shows the approval dialog, choose "No, refine with Ultraplan on Claude Code on the web" to send the draft to the cloud for further polishing. While the cloud works, your prompt input shows a status indicator: ◇ ultraplan means drafting, ◇ ultraplan needs your input means Claude has a clarifying question, ◆ ultraplan ready means go open your browser.

/ultraplan migrate the auth service from sessions to JWTs

What happens in the browser — and where does the plan execute?

When the status flips to ◆ ultraplan ready, open the session link. The plan appears in a review view where you can highlight any passage and leave an inline comment, react with emoji to signal approval or concern, and jump around via an outline sidebar. Ask Claude to address your comments and it presents a revised draft — iterate as long as you like. Then choose: "Approve Claude's plan and start coding" runs the implementation in the same cloud session, ending in a diff you can review and turn into a pull request. Or "Approve plan and teleport back to terminal" archives the web session and shows an Ultraplan approved dialog in your terminal with three options: implement here, start a new session with only the plan as context, or cancel — which saves the plan to a file and prints the path.

What is ultrareview, and how is it different from a normal review?

Ultrareview is a deep code review that runs on Claude Code on the web infrastructure: a fleet of reviewer agents explores your change in parallel inside a remote sandbox, and every reported finding is independently reproduced and verified — so you get real bugs, not style nagging. Compare that to the local /review: seconds to minutes, single pass, counts toward normal usage. Ultrareview takes roughly 5 to 10 minutes, runs in the background while you keep working, and is built for pre-merge confidence on substantial changes.

/code-review ultra

How much do ultraplan and ultrareview cost?

Ultrareview is the one with a price tag: Pro and Max subscribers get 3 free runs as a one-time allotment that does not refresh, and after that each review bills to usage credits — typically $5 to $20 depending on the size of the change. Team and Enterprise plans get no free runs. A run counts once the cloud session starts, so a review you stop early still spends a free run. Before launching, Claude Code shows a confirmation with the scope, your remaining free runs, and the estimated cost — no surprise charges. Ultrareview also requires signing in with a Claude.ai account; an API key alone won't do.

The kicker: the next change you're nervous about, run the full loop — plan in the cloud, comment like an editor, execute locally, then spend one free ultrareview run before you ship. That loop is the closest a non-programmer gets to having a senior team on call.