ultraplan.md +0 −84 deleted
File Deleted View Diff
1> ## Documentation Index
2> Fetch the complete documentation index at: https://code.claude.com/docs/llms.txt
3> Use this file to discover all available pages before exploring further.
4
5# Plan in the cloud with ultraplan
6
7> Start a plan from your CLI, draft it on Claude Code on the web, then execute it remotely or back in your terminal
8
9<Note>
10 Ultraplan is in research preview and requires Claude Code v2.1.91 or later. Behavior and capabilities may change based on feedback.
11</Note>
12
13Ultraplan hands a planning task from your local CLI to a [Claude Code on the web](/en/claude-code-on-the-web) session running in [plan mode](/en/permission-modes#analyze-before-you-edit-with-plan-mode). Claude drafts the plan in the cloud while you keep working in your terminal. When the plan is ready, you open it in your browser to comment on specific sections, ask for revisions, and choose where to execute it.
14
15This is useful when you want a richer review surface than the terminal offers:
16
17* **Targeted feedback**: comment on individual sections of the plan instead of replying to the whole thing
18* **Hands-off drafting**: the plan is generated remotely, so your terminal stays free for other work
19* **Flexible execution**: approve the plan to run on the web and open a pull request, or send it back to your terminal
20
21Ultraplan requires a [Claude Code on the web](/en/claude-code-on-the-web) account and a GitHub repository. Because it runs on Anthropic's cloud infrastructure, it is not available when using Amazon Bedrock, Google Cloud Vertex AI, or Microsoft Foundry. The cloud session runs in your account's default [cloud environment](/en/claude-code-on-the-web#the-cloud-environment). If you don't have a cloud environment yet, ultraplan creates one automatically when it first launches.
22
23## Launch ultraplan from the CLI
24
25From your local CLI session, you can launch ultraplan in three ways:
26
27* **Command**: run `/ultraplan` followed by your prompt
28* **Keyword**: include the word `ultraplan` anywhere in a normal prompt
29* **From a local plan**: 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 iteration
30
31For example, to plan a service migration with the command:
32
33```
34/ultraplan migrate the auth service from sessions to JWTs
35```
36
37The command and keyword paths open a confirmation dialog before launching. The local plan path skips this dialog because that selection already serves as confirmation. If [Remote Control](/en/remote-control) is active, it disconnects when ultraplan starts because both features occupy the claude.ai/code interface and only one can be connected at a time.
38
39After the cloud session launches, your CLI's prompt input shows a status indicator while the cloud session works:
40
41| Status | Meaning |
42| :----------------------------- | :----------------------------------------------------------------- |
43| `◇ ultraplan` | Claude is researching your codebase and drafting the plan |
44| `◇ ultraplan needs your input` | Claude has a clarifying question; open the session link to respond |
45| `◆ ultraplan ready` | The plan is ready to review in your browser |
46
47Run `/tasks` and select the ultraplan entry to open a detail view with the session link, agent activity, and a **Stop ultraplan** action. Stopping archives the cloud session and clears the indicator; nothing is saved to your terminal.
48
49## Review and revise the plan in your browser
50
51When the status changes to `◆ ultraplan ready`, open the session link to view the plan on claude.ai. The plan appears in a dedicated review view:
52
53* **Inline comments**: highlight any passage and leave a comment for Claude to address
54* **Emoji reactions**: react to a section to signal approval or concern without writing a full comment
55* **Outline sidebar**: jump between sections of the plan
56
57When you ask Claude to address your comments, it revises the plan and presents an updated draft. You can iterate as many times as needed before choosing where to execute.
58
59## Choose where to execute
60
61When the plan looks right, you choose from the browser whether Claude implements it in the same cloud session or sends it back to your waiting terminal.
62
63### Execute on the web
64
65Select **Approve Claude's plan and start coding** in your browser to have Claude implement it in the same Claude Code on the web session. Your terminal shows a confirmation, the status indicator clears, and the work continues in the cloud. When the implementation finishes, [review the diff](/en/claude-code-on-the-web#review-changes) and create a pull request from the web interface.
66
67### Send the plan back to your terminal
68
69Select **Approve plan and teleport back to terminal** in your browser to implement the plan locally with full access to your environment. This option appears when the session was launched from your CLI and the terminal is still polling. The web session is archived so it doesn't continue working in parallel.
70
71Your terminal shows the plan in a dialog titled **Ultraplan approved** with three options:
72
73* **Implement here**: inject the plan into your current conversation and continue from where you left off
74* **Start new session**: clear the current conversation and begin fresh with only the plan as context
75* **Cancel**: save the plan to a file without executing it; Claude prints the file path so you can return to it later
76
77If you start a new session, Claude prints a `claude --resume` command at the top so you can return to your previous conversation later.
78
79## Related resources
80
81* [Claude Code on the web](/en/claude-code-on-the-web): the cloud infrastructure ultraplan runs on
82* [Plan mode](/en/permission-modes#analyze-before-you-edit-with-plan-mode): how planning works in a local session
83* [Find bugs with ultrareview](/en/ultrareview): the code review counterpart to ultraplan for catching issues before merge
84* [Remote Control](/en/remote-control): use the claude.ai/code interface with a session running on your own machine