Max plans: include a recurring ultrareview allotment instead of 3 lifetime free runs

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

I'm a Max 20x subscriber ($200/month) using Claude Code to run a production e-commerce site solo. I have no test environment — code goes from Claude Code to production — so pre-merge review is my only safety layer, and ultrareview is genuinely the right tool for it: on a recent customer-auth/cart-cookie change, the cloud fleet independently verified the hardened code with zero findings. That's exactly the confidence I need, routinely.

The problem is the billing structure. Everything else in a Max plan is a renewing allotment — sessions reset every 5 hours, weekly limits reset weekly — but ultrareview alone is a one-time coupon: 3 free runs ever, then $5–$25 per run in usage credits on top of the subscription. That structure teaches the opposite of the habit the feature deserves: I'm now hoarding my last free run instead of reviewing every substantial change before it ships.

Proposed Solution

Include a recurring ultrareview allotment in Max plans — e.g. 1–2 runs per week on Max 20x (scaled down for Max 5x and Pro) — renewing on the same weekly cadence as the plan's other limits, with usage-credit billing only beyond the allotment.

The CLI launch header already reports free-run status ("Free ultrareview 2 of 3."); it would simply become "Weekly ultrareview: 1 of 2 used, resets Tuesday."

Alternative Solutions

• Rationing the 3 lifetime free runs: what I'm doing now — saving the last one for the "most important" change, which means routine changes ship with less scrutiny.
• Local /code-review at max effort in-session: I use it, and it catches real bugs, but it's explicitly the shallower instrument — no independent multi-agent cloud verification.
• Enabling usage credits at $5–$25/run: works, but on top of $200/month it prices routine review as a splurge and discourages exactly the habit the feature is built for.
• A monthly allotment or a discounted Max per-run rate would also address the problem.

Priority

Medium - Would be very helpful

Feature Category

Other

Use Case Example

1. I ship a feature slice touching customer sign-in and cart-cookie handling on my live store.
2. In-session local review catches several issues; I apply fixes and push.
3. I run claude ultrareview for an independent cloud pass before considering the slice closed. (Last run: zero findings on the hardened change — exactly the pre-merge confidence I wanted.)
4. I ship 1–2 such slices per week. With an included weekly allotment I'd run ultrareview on every one; under the 3-lifetime-runs structure I skip or hoard instead.

Additional Context

The docs describe ultrareview as a research preview whose "feature, pricing, and availability may change based on feedback" — this is that feedback, from the target customer: a Max 20x subscriber who wants to use the feature more, not less. A renewing allotment also showcases the feature far better than a lifetime cap, since a 3-and-done structure means most subscribers will experience it exactly three times.

Claude Code v2.1.215, Windows 11, Max 20x plan.