ultraplan: 'Approve' in web UI is not clear that it triggers cloud execution (expected plan-only review)

Feedback

What happened

I ran /ultraplan from the CLI to generate a plan for a feature. When the plan was ready, the web session (claude.ai/code) asked me to review it. I clicked Approve, expecting that to mean "the plan looks good — hand it back to my CLI session so I can execute locally" (the CLI hint says to press ↓ to view results).

Instead, Approve immediately started executing the plan in the cloud session, with results set to land as a pull request. That was not what I wanted — my intent was to plan in the cloud but execute locally in my own environment (Docker stack, local DB).

Why it's confusing

• The approval dialog doesn't distinguish between "accept the plan" and "execute the plan remotely".
• The CLI-side flow (press ↓ to import results) and the web-side flow (Approve → cloud execution → PR) are two different handoffs, and nothing in the UI explains which one you're choosing.
• As a non-native English speaker the single word "Approve" gave no hint of the consequence.

Suggestion

Make the consequence explicit at the decision point, e.g. two buttons: "Approve & execute in cloud (opens a PR)" vs "Send plan back to CLI" — or a confirmation line under Approve stating where execution will happen.

Environment

• Claude Code CLI on macOS (darwin), ultraplan beta
• Also hit an unrelated ultraplan failure earlier the same day: a session died mid-run with Request failed with status code 404 from the claude.ai session endpoint — mentioning it in case it's useful signal for the beta.