Ultraplan For Cloud-First Implementation Planning
Plan complex changes with Claude Code ultraplan: launch /ultraplan from the CLI, review cloud drafts on claude.ai, comment inline, and choose web or terminal execution.
Open the source and read safety notes before installing.
Safety notes
- Cloud execution runs autonomously—treat approved plans like production-impacting work.
- Remote Control disconnects when ultraplan starts; only one claude.ai/code session control path is active.
Privacy notes
- Cloud planning sessions may include repository paths and design notes in claude.ai history.
- Plan comments and reactions are stored in the web session until archived.
Prerequisites
- Claude Code v2.1.91+ with claude.ai subscription login (not API-key-only auth).
- GitHub repository connected for Claude Code on the web.
- Maintainer review before merging cloud-generated pull requests.
Schema details
- Install type
- copy
- Reading time
- 8 min
- Difficulty score
- 52
- Troubleshooting
- Yes
- Breaking changes
- No
Full copyable content
Run /ultraplan with a self-contained prompt, monitor status in the CLI, review the plan in the browser, then approve execution on the web or teleport back to terminal.About this resource
TL;DR
Ultraplan sends a planning task from your local CLI to Claude Code on the web in plan mode. Review the draft in a browser with inline comments, then execute on the web or teleport the approved plan back to your terminal.
Prerequisites & Requirements
- {"task": "Version", "description": "Claude Code v2.1.91 or later"}
- {"task": "Login", "description": "claude.ai subscription login; Bedrock, Vertex, and Foundry are not supported"}
- {"task": "GitHub repo", "description": "Connected repository for cloud sessions"}
- {"task": "Review owner", "description": "Human approves cloud-opened PRs"}
Step-by-Step Workflow
- Launch with
/ultraplan <prompt>, include the keywordultraplanin a prompt, or choose refine with Ultraplan on Claude Code on the web after a local plan. - Confirm the launch dialog (skipped when promoting a local plan).
- Watch CLI status:
◇ ultraplan,◇ ultraplan needs your input, or◆ ultraplan ready. - Open the session link when ready; leave inline comments or emoji reactions on sections.
- Choose Approve Claude's plan and start coding in your browser or Approve plan and teleport back to terminal.
- If teleported back, pick Implement here, Start new session, or Cancel (save plan to file).
Source Verification Notes
Verified against official ultraplan documentation on 2026-06-16:
/ultraplanlaunches cloud plan mode; the keywordultraplanalso triggers it.- Requires Claude Code on the web and a GitHub repository; unavailable on Bedrock, Vertex, or Foundry.
- Status indicators document researching, input needed, and plan ready states.
/tasksopens detail view with session link and Stop ultraplan action.- Browser review supports inline comments, emoji reactions, and an outline sidebar.
- Teleport-back options: Implement here, Start new session, or Cancel with saved plan file path.
Duplicate Check
Complements claude-code-on-the-web-for-repository-planning (general web planning).
This guide focuses on the /ultraplan command workflow and teleport-back execution choices.
Troubleshooting
Issue: Ultraplan unavailable Fix: Confirm claude.ai login, GitHub connection, and CLI version at least v2.1.91 per official docs.
Source citations
Add this badge to your README
Show that Ultraplan For Cloud-First Implementation Planning is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/guides/ultraplan-for-cloud-first-implementation-planning)How it compares
Ultraplan For Cloud-First Implementation Planning side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | Ultraplan For Cloud-First Implementation Planning Plan complex changes with Claude Code ultraplan: launch /ultraplan from the CLI, review cloud drafts on claude.ai, comment inline, and choose web or terminal execution. Open dossier | Claude Code On The Web For Repository Planning Use Claude Code on the web to plan repository changes remotely: connect a repo, run plan-mode sessions in the browser, capture session URLs, and hand plans to local Claude Code for implementation. Open dossier | Zero Data Retention Planning for Claude Code Enterprise Enterprise guide to zero data retention planning for Claude Code: contractual ZDR scope, logging boundaries, MCP data paths, and verification checkpoints. Open dossier | Adding Plugin Install Hints to Developer CLIs A practical walkthrough of the claude-code-hint protocol. When CLAUDECODE is set, have your CLI write a self-closing tag to stderr; Claude Code strips the line before it reaches the model and shows a one-time prompt to install your plugin — but only for plugins in the official Anthropic marketplace. Open dossier |
|---|---|---|---|---|
| Trust | ||||
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Category | guides | guides | guides | guides |
| Source | source-backed | source-backed | source-backed | source-backed |
| Author | kiannidev | kiannidev | kiannidev | JPette1783 |
| Added | 2026-06-16 | 2026-06-15 | 2026-06-14 | 2026-06-05 |
| Platforms | Claude Code | Claude Code | Claude Code | Claude Code |
| Source repo | — | — | — | — |
| Safety notes | ✓Cloud execution runs autonomously—treat approved plans like production-impacting work. Remote Control disconnects when ultraplan starts; only one claude.ai/code session control path is active. | ✓Remote planning processes repository context on cloud infrastructure—confirm compliance for restricted codebases. Planning sessions are not implementations; scope local execution sessions separately with tests and review. Store session URLs in access-controlled notes, not public tickets with secrets. | ✓ZDR policy does not eliminate local repository risk—developers can still commit secrets; pair ZDR with secret scanning and MCP review. Third-party MCP servers may retain data outside Claude Code ZDR guarantees; block or review them explicitly. Do not assume analytics dashboards are ZDR-compatible without verifying their data collection scope. | ✓The hint never auto-installs anything; Claude Code only shows a one-time prompt and the user always confirms. Gate emission on the CLAUDECODE environment variable so the marker never appears in a human user's terminal or in normal pipelines. Hints are only acted on for plugins in an official Anthropic marketplace; pointers to other marketplaces are silently dropped. |
| Privacy notes | ✓Cloud planning sessions may include repository paths and design notes in claude.ai history. Plan comments and reactions are stored in the web session until archived. | ✓Remote planning may include architecture details, customer requirements, and unreleased feature names. Session transcripts may persist in cloud history—follow vendor retention policies. Do not paste credentials, tokens, or customer PII into planning prompts. | ✓Document which subsystems may temporarily process prompts for abuse prevention versus training exclusions under ZDR. Map cross-border data flows if developers connect from multiple regions. Maintain records of ZDR verification dates and responsible owners for audits. | ✓Claude Code strips the hint line before output reaches the model, so it is not counted toward token usage and does not enter the conversation. Write the tag to stderr to keep it out of shell pipelines like `your-cli deploy | jq`; do not embed it mid-line in logs. The hint carries only your plugin identifier; do not append user data or secrets to the marker line. |
| Prerequisites |
|
|
|
|
| Install | — | | — | — |
| Config | — | — | — | — |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Signals
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.