Claude Code /ultraplan: Cloud Planning Without Setup
Claude Code v2.1.101 eliminates the manual web setup prerequisite for /ultraplan and other remote-session features by automatically provisioning a default cloud environment on first use. The /ultraplan command offloads the planning phase of a coding task to a cloud-hosted Opus 4.6 session running in Anthropic's Cloud Container Runtime, where the model can work for up to 30 minutes while the local terminal remains completely free. Developers review, comment on, and approve the resulting plan in a browser interface, then choose whether to execute it in the cloud or send it back to the terminal.
Key Takeaways
- Auto-provisioning removes the setup barrier β /ultraplan now creates a default cloud environment on first use, so developers no longer need to visit the web dashboard before invoking the feature from the CLI.
- Opus 4.6 runs in the cloud for up to 30 minutes, enabling deep planning for complex refactors and architectural decisions that would be impractical to run locally or interactively.
- The local terminal stays fully free while the cloud session works, allowing parallel tasks, additional planning jobs, or unrelated development work to continue without interruption.
- A browser-based review interface with inline comments and emoji reactions replaces terminal scrollback, giving developers pull-request-style annotation tools to iterate on specific sections of the plan before a single line of code changes.
- Flexible execution at plan approval β developers choose whether to implement the plan in the cloud (opening a PR automatically) or teleport it back to the local terminal for execution in the native environment.
- The feature is incompatible with Bedrock, Vertex AI, and Foundry because it requires Anthropic's Cloud Container Runtime; teams using third-party cloud providers cannot use /ultraplan regardless of plan tier.
Sources & Mentions
3 external resources covering this update
/ultraplan: Cloud-Hosted Planning, Now Without the Setup Overhead
Automatic Environment Provisioning Removes the Barrier to Entry
Prior to v2.1.101, using /ultraplan required developers to navigate to the Claude Code web interface and manually configure a default cloud environment before the command would work from the CLI. That prerequisite has been eliminated. /ultraplan and all other remote-session features now auto-create a default cloud environment on first use, allowing developers to invoke cloud planning immediately β directly from the terminal, without any prior web configuration.
This change closes the gap between reading about the feature and actually using it. There is no longer a "first you need to go to the web dashboard" step; the infrastructure is provisioned transparently the first time it is needed.
What /ultraplan Does
/ultraplan is a research-preview feature (available since v2.1.91) that hands the planning phase of a coding task off to a Claude Code session running in plan mode on Anthropic's cloud infrastructure. Rather than generating a plan in the local terminal β where review means scrolling through text with no way to annotate individual sections β the plan is drafted remotely and presented in a rich browser interface.
The cloud session runs Opus 4.6 inside Anthropic's Cloud Container Runtime (CCR) and can work for up to 30 minutes on complex tasks. During that time, the local terminal remains fully available; developers can continue other work, run tests, or launch a second planning session in parallel. The CLI displays a live status indicator that polls the remote session every few seconds:
- β ultraplan β Claude is actively researching the codebase and drafting
- β ultraplan needs your input β a clarifying question is waiting in the browser
- β ultraplan ready β the plan is available to review
Three Ways to Invoke It
/ultraplan can be launched in three ways from the CLI:
- Command: run /ultraplan followed by a prompt β e.g., /ultraplan migrate the auth service from sessions to JWTs
- Keyword: include the word ultraplan anywhere in a regular prompt
- From a local plan: when Claude finishes drafting a local plan and shows the approval dialog, selecting "No, refine with Ultraplan on Claude Code on the web" escalates the draft to the cloud for further iteration
A Richer Review Surface
When the plan is ready, it opens in a dedicated browser review view. Developers can highlight any passage and leave inline comments for Claude to address, use emoji reactions to signal approval or concern on specific sections, and navigate a structured outline sidebar to jump between parts of the plan. This is a meaningfully different review experience from scrolling through terminal output β closer to reviewing a pull request than reading a chat message.
After revisions, the developer chooses where to execute: approve the plan and run it in the same cloud session (which then opens a pull request), or select "Approve plan and teleport back to terminal" to implement it locally with full access to the local environment.
Requirements and Constraints
/ultraplan requires a Claude Code on the web account (Pro, Max, Team, or Enterprise) and a connected GitHub repository β the cloud environment clones the repository using a secure GitHub proxy. The feature is not available when Claude Code is configured to use Amazon Bedrock, Google Cloud Vertex AI, or Microsoft Foundry, as those bypass Anthropic's cloud infrastructure. Ultraplan and the Remote Control feature cannot run simultaneously, since both occupy the claude.ai/code interface; launching Ultraplan disconnects any active Remote Control session.