/ultrareview: billed cloud action triggered by default Return key with no cost confirmation

Summary

The /ultrareview slash-menu entry surfaces a paid, billed cloud action with the same affordance as every free local command, and it is launched by Claude Code's most-used keystroke — Return. The first-time user experience has two specific failure modes:

1. Visual confusion — On first appearance in the slash menu the entry reads like a promotional/ad item rather than a tool the user opted into. There is no label indicating it is a separate billed product distinct from normal Claude Code usage.
2. Accidental opt-in via Return — Because Return is the default accept gesture used constantly across the CLI, a user scrolling or recovering from a stray keypress can launch a billed run with no "this will charge you" confirmation step. There is no per-command cost disclosure, no first-run acknowledgment, and no dry-run preview.

This is the kind of UX where the accident path leads to a charge. That should not be possible without an explicit confirmation.

Steps to reproduce

1. Open Claude Code in any project.
2. Type / to open the slash-command menu.
3. Navigate to or land on /ultrareview and press Return.
4. Observe: a remote, billed multi-agent review begins (or attempts to begin) with no cost prompt.

Expected behavior

• The slash menu visually labels billed commands distinctly (e.g., a $ glyph, a "paid" tag, or a separate "Paid services" submenu).
• The first time a user invokes a billed command in a given install, Claude Code shows a confirmation modal that explicitly states: this action is billed, here is the approximate cost, do you want to proceed?
• Subsequent invocations could be silent if the user opts to suppress the warning, but the suppression should be a deliberate choice, not the default.

Actual behavior

• No visual distinction in the slash menu between free local commands and paid cloud commands.
• No cost prompt before the billed action runs.
• Return — the universal accept key — is sufficient to opt in.

Suggested fixes (in priority order)

1. Hard-gate first run. Require an explicit "I understand this is a paid service" confirmation the first time any billed command is invoked per install.
2. Label billed commands in the slash menu. A $ prefix, a colored tag, or a separate menu section so users can distinguish them at a glance.
3. Add an opt-out / disable flag. Allow users who never want paid commands to hide them entirely from the slash menu via settings.json.
4. Show estimated cost in the confirmation. Even a rough "typically \$X–\$Y per run" string would let users make an informed choice.

Environment

• Claude Code (CLI), macOS (Darwin 24.6.0)
• Model: Claude Opus 4.7

Additional context

The error returned on the failed attempt was a server-side seed bundle import: file not found from the review backend — unrelated to the UX concern, but worth noting that the failure mode also did not produce a clear "this would have been a billed run that did not complete" message to the user.

---

Drafted in collaboration with Claude Code (Opus 4.7) at the user's request, after the user encountered this exact issue in a working session.