Cloud Workflows: Ultraplan, Ultrareview & Artifacts
Use Claude Code on the web for cloud planning, deep remote review, and shareable artifacts.
Why Cloud Workflows Matter
Some Claude Code work is better outside the terminal. Claude Code on the web can run planning and review work remotely, use richer review surfaces, and publish shareable artifacts.
This page covers three high-leverage cloud capabilities:
- Ultraplan: draft a plan in the cloud, review it in the browser, then execute locally or remotely.
- Ultrareview: run deep multi-agent code review in a remote sandbox.
- Artifacts: publish a live, interactive page from a session for internal sharing.
Ultraplan
Ultraplan is for plan quality and review ergonomics. Launch it from the CLI:
/ultraplan migrate the auth service from sessions to JWTsYou can also include the keyword ultraplan in a normal prompt, or send a local plan to the web from the plan approval dialog.
Use ultraplan when:
- The plan is large enough to deserve section-level comments.
- You want your terminal free while planning happens remotely.
- You want to approve execution on the web or send the plan back to the terminal.
Ultraplan requires Claude Code on the web and a GitHub repository. It is not available through Bedrock, Vertex AI, or Microsoft Foundry.
Ultrareview
Ultrareview is invoked as:
/code-review ultra
/code-review ultra 1234It launches a remote multi-agent review to find and verify bugs before merging. Compared with a local review, it is broader, runs off your machine, and attempts to independently reproduce findings before reporting them.
Use it before important merges, risky migrations, or large PRs where a single-pass review is not enough.
For CI or scripts, use the non-interactive subcommand:
claude ultrareview 1234 --jsonArtifacts
Artifacts publish Claude Code output as a private interactive page for your organization. They are beta and require a Team or Enterprise plan plus a session signed in with /login. Ask for one when terminal text is the wrong medium:
Make an artifact that walks through this PR with annotated diffs and severity labels.Artifacts are useful for:
- PR walkthroughs.
- Investigation timelines.
- Dashboards from data Claude pulled.
- Comparing design or implementation options.
- Sharing a work-in-progress status page with teammates.
Artifacts are not full applications. They are self-contained pages with no backend, external network calls, or multi-route app behavior.
When to Use Each
| Need | Use |
|---|---|
| Rich plan review before implementation | Ultraplan |
| Deep verified bug review | Ultrareview |
| Share a visual or interactive result | Artifact |
| Run recurring cloud automation | Routine |
| Continue local work from another device | Remote Control |
Availability Notes
Cloud features depend on account, organization, provider, and policy settings. Many require Claude.ai authentication and Claude Code on the web. Ultraplan and Ultrareview are unavailable with Bedrock, Vertex AI, or Microsoft Foundry; Ultrareview is also unavailable for Zero Data Retention organizations.
Treat each feature's official page as the source of truth before relying on it in a team rollout.
Official References
Continue with practice
You have finished the core ideas of Cloud Workflows: Ultraplan, Ultrareview & Artifacts.
If you want to turn the idea into something reusable, continue practicing on AgentWay.