feat(usage): add subscription allowance reporting

[naveed949]

What Changed

Adds a Subscription view to Settings → Usage for current provider-reported allowance data, while keeping the existing Historical usage view independent.

• Adds snapshot-first, live-updating subscription allowance reporting for Codex and Claude.
• Adds additive RPC contracts, server lifecycle handling, refresh, staleness, compatibility, and privacy-safe provider identity behavior.
• Adds a shared web/mobile projection that keeps provider sources inspectable and never blends allowance windows across environments.
• Adds Subscription UI, manual refresh, and mobile pull-to-refresh alongside unchanged Historical controls.
• Documents user behavior, implementation boundaries, and release evidence requirements.
• Adds focused contract, provider-reader, server, runtime, web, and mobile tests.

Why

Historical usage is transcript-derived activity and API-equivalent cost; it does not show the current limits of a user’s Codex or Claude subscription. This adds a separate, provider-native allowance view without inferring quotas, account status, or billing information that a provider did not report.

UI Changes

Before/after screenshots for web and mobile still need to be attached before review. A short recording should also be included if refresh or live-update behavior is demonstrated.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

Model and harness: verify and fill from the implementation run before review.

Note

Add subscription allowance reporting for Claude and Codex providers

• Adds a new 'Subscription' usage view on web and mobile, showing per-provider allowance cards, progress bars, and metadata
• Implements backend SubscriptionAllowanceService to read, fold, and stream allowance snapshots with periodic refresh and live updates
• Introduces allowance readers for Claude and Codex providers to map native rate-limit data into a common SubscriptionAllowance shape
• Adds serverRefreshSubscriptionAllowance and subscribeSubscriptionAllowance WS RPC endpoints backed by AuthOrchestrationReadScope
• Behavioral Change: createEnvironmentRpcSubscriptionAtomFamily accepts failOnMethodNotFound; the new subscription stream terminates on older backends lacking the method

^{Macroscope summarized 40853ac.}

---

Note

High Risk
Touches provider drivers, runtime event tagging, new WS RPCs, and orchestration-read authorization. Incorrect folding or event-source checks could leak stale/wrong quota data or skip live updates.

Overview
Adds a Subscription tab on Usage (web and mobile, default view) that shows current Codex/Claude rate limits, resets, credits, and spend/extra-usage fields—without mixing them into transcript-based Historical usage.

Server: new SubscriptionAllowanceService demand-scopes reads, 5-minute refresh, reset-based staleness, and folds sparse account.rate-limits.updated events into the last complete snapshot. Claude/Codex drivers gain allowance readers (SDK get_usage / Codex account/rateLimits/read) with timeouts. New RPCs subscribeSubscriptionAllowance and server.refreshSubscriptionAllowance require orchestration:read. Codex rate-limit notifications now emit only validated rateLimits payloads; runtime events carry an internal adapter source so replaced instances cannot fold updates.

Clients: shared reconcileSubscriptionAllowances keeps environments/instances separate, groups only verified identities, and never blends windows. UI cards show progress, notices, and sources; switching away from Subscription unmounts the stream.

^{Reviewed by Cursor Bugbot for commit 40853ac. Bugbot is set up for automated code reviews on this repo. Configure here.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 92c669ec-4a0e-4bbf-9ac2-bae163641b8a

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Reviewed the new Effect service code (SubscriptionAllowanceService, ProviderAllowanceReader, the Codex/Claude allowance readers) against the service conventions. The service definition/layer layout and namespace imports look fine; three findings on dependency acquisition and error modelling are below.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

Approvability

Verdict: Skipped

Macroscope did not run approvability analysis for this PR. Macroscope could not determine whether this PR modifies its approvability configuration, so the PR was not approved automatically. A PR that may change the rules that govern approval is never approved automatically.

[macroscopeapp]

Reviewed the web usage surface for shared-primitive, Tailwind-ownership, and theming consistency. Five concrete issues in apps/web/src/components/usage/UsagePage.tsx, three of which break the build or the rendered UI.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

UI consistency review of the new web Usage surfaces. Two findings on apps/web/src/components/usage/UsagePage.tsx; the issues flagged on the previous revision (duplicate Button import, missing PROVIDER_LABEL/PROVIDER_COLOR, bare text-amber-600, mismatched refresh control, topbar header classes) are resolved.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Two consistency findings on the new Subscription view in apps/web/src/components/usage/UsagePage.tsx. The previously raised points about the hand-rolled UsageViewTabs segmented control and the duplicated page frame are unchanged and still stand; they are not repeated inline here.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One finding: the new Usage view switch is a raw-button reconstruction of the app's segmented ToggleGroup, which the same page already uses for the metric and period switches.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

UI consistency review of the changed web usage surface (apps/web/src/components/usage/UsagePage.tsx). The Subscription/Historical switch now goes through ToggleGroup variant="segmented", the card/notice surfaces match the page's existing square border border-border idiom, and the stale label uses the warning-foreground token, so those are consistent. Two issues remain on changed lines, both in the new Subscription view.

^{Posted via Macroscope — UI Consistency}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit f8723f3. Configure here.}

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

Closing this PR after an automated pass over open pull requests. Competes with Theo's existing provider-limit proposal in #5739.

[naveed949]

What Changed

Adds a Subscription view to Settings → Usage for current provider-reported allowance data, while keeping the existing Historical usage view independent.

• Adds snapshot-first, live-updating subscription allowance reporting for Codex and Claude.
• Adds additive RPC contracts, server lifecycle handling, refresh, staleness, compatibility, and privacy-safe provider identity behavior.
• Adds a shared web/mobile projection that keeps provider sources inspectable and never blends allowance windows across environments.
• Adds Subscription UI, manual refresh, and mobile pull-to-refresh alongside unchanged Historical controls.
• Documents user behavior, implementation boundaries, and release evidence requirements.
• Adds focused contract, provider-reader, server, runtime, web, and mobile tests.

Why

Historical usage is transcript-derived activity and API-equivalent cost; it does not show the current limits of a user’s Codex or Claude subscription. This adds a separate, provider-native allowance view without inferring quotas, account status, or billing information that a provider did not report.

UI Changes

Before/after screenshots for web and mobile still need to be attached before review. A short recording should also be included if refresh or live-update behavior is demonstrated.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

Model and harness: verify and fill from the implementation run before review.

Note

Add subscription allowance reporting for Claude and Codex providers

• Adds a new 'Subscription' usage view on web and mobile, showing per-provider allowance cards, progress bars, and metadata
• Implements backend SubscriptionAllowanceService to read, fold, and stream allowance snapshots with periodic refresh and live updates
• Introduces allowance readers for Claude and Codex providers to map native rate-limit data into a common SubscriptionAllowance shape
• Adds serverRefreshSubscriptionAllowance and subscribeSubscriptionAllowance WS RPC endpoints backed by AuthOrchestrationReadScope
• Behavioral Change: createEnvironmentRpcSubscriptionAtomFamily accepts failOnMethodNotFound; the new subscription stream terminates on older backends lacking the method

^{Macroscope summarized 40853ac.}

---

Note

High Risk
Touches provider drivers, runtime event tagging, new WS RPCs, and orchestration-read authorization. Incorrect folding or event-source checks could leak stale/wrong quota data or skip live updates.

Overview
Adds a Subscription tab on Usage (web and mobile, default view) that shows current Codex/Claude rate limits, resets, credits, and spend/extra-usage fields—without mixing them into transcript-based Historical usage.

Server: new SubscriptionAllowanceService demand-scopes reads, 5-minute refresh, reset-based staleness, and folds sparse account.rate-limits.updated events into the last complete snapshot. Claude/Codex drivers gain allowance readers (SDK get_usage / Codex account/rateLimits/read) with timeouts. New RPCs subscribeSubscriptionAllowance and server.refreshSubscriptionAllowance require orchestration:read. Codex rate-limit notifications now emit only validated rateLimits payloads; runtime events carry an internal adapter source so replaced instances cannot fold updates.

Clients: shared reconcileSubscriptionAllowances keeps environments/instances separate, groups only verified identities, and never blends windows. UI cards show progress, notices, and sources; switching away from Subscription unmounts the stream.

^{Reviewed by Cursor Bugbot for commit 40853ac. Bugbot is set up for automated code reviews on this repo. Configure here.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 92c669ec-4a0e-4bbf-9ac2-bae163641b8a

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Reviewed the new Effect service code (SubscriptionAllowanceService, ProviderAllowanceReader, the Codex/Claude allowance readers) against the service conventions. The service definition/layer layout and namespace imports look fine; three findings on dependency acquisition and error modelling are below.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

Approvability

Verdict: Skipped

Macroscope did not run approvability analysis for this PR. Macroscope could not determine whether this PR modifies its approvability configuration, so the PR was not approved automatically. A PR that may change the rules that govern approval is never approved automatically.

[macroscopeapp]

Reviewed the web usage surface for shared-primitive, Tailwind-ownership, and theming consistency. Five concrete issues in apps/web/src/components/usage/UsagePage.tsx, three of which break the build or the rendered UI.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

UI consistency review of the new web Usage surfaces. Two findings on apps/web/src/components/usage/UsagePage.tsx; the issues flagged on the previous revision (duplicate Button import, missing PROVIDER_LABEL/PROVIDER_COLOR, bare text-amber-600, mismatched refresh control, topbar header classes) are resolved.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Two consistency findings on the new Subscription view in apps/web/src/components/usage/UsagePage.tsx. The previously raised points about the hand-rolled UsageViewTabs segmented control and the duplicated page frame are unchanged and still stand; they are not repeated inline here.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One finding: the new Usage view switch is a raw-button reconstruction of the app's segmented ToggleGroup, which the same page already uses for the metric and period switches.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

UI consistency review of the changed web usage surface (apps/web/src/components/usage/UsagePage.tsx). The Subscription/Historical switch now goes through ToggleGroup variant="segmented", the card/notice surfaces match the page's existing square border border-border idiom, and the stale label uses the warning-foreground token, so those are consistent. Two issues remain on changed lines, both in the new Subscription view.

^{Posted via Macroscope — UI Consistency}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit f8723f3. Configure here.}

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

Closing this PR after an automated pass over open pull requests. Competes with Theo's existing provider-limit proposal in #5739.

[naveed949]

What Changed

Adds a Subscription view to Settings → Usage for current provider-reported allowance data, while keeping the existing Historical usage view independent.

• Adds snapshot-first, live-updating subscription allowance reporting for Codex and Claude.
• Adds additive RPC contracts, server lifecycle handling, refresh, staleness, compatibility, and privacy-safe provider identity behavior.
• Adds a shared web/mobile projection that keeps provider sources inspectable and never blends allowance windows across environments.
• Adds Subscription UI, manual refresh, and mobile pull-to-refresh alongside unchanged Historical controls.
• Documents user behavior, implementation boundaries, and release evidence requirements.
• Adds focused contract, provider-reader, server, runtime, web, and mobile tests.

Why

Historical usage is transcript-derived activity and API-equivalent cost; it does not show the current limits of a user’s Codex or Claude subscription. This adds a separate, provider-native allowance view without inferring quotas, account status, or billing information that a provider did not report.

UI Changes

Before/after screenshots for web and mobile still need to be attached before review. A short recording should also be included if refresh or live-update behavior is demonstrated.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

Model and harness: verify and fill from the implementation run before review.

Note

Add subscription allowance reporting for Claude and Codex providers

• Adds a new 'Subscription' usage view on web and mobile, showing per-provider allowance cards, progress bars, and metadata
• Implements backend SubscriptionAllowanceService to read, fold, and stream allowance snapshots with periodic refresh and live updates
• Introduces allowance readers for Claude and Codex providers to map native rate-limit data into a common SubscriptionAllowance shape
• Adds serverRefreshSubscriptionAllowance and subscribeSubscriptionAllowance WS RPC endpoints backed by AuthOrchestrationReadScope
• Behavioral Change: createEnvironmentRpcSubscriptionAtomFamily accepts failOnMethodNotFound; the new subscription stream terminates on older backends lacking the method

^{Macroscope summarized 40853ac.}

---

Note

High Risk
Touches provider drivers, runtime event tagging, new WS RPCs, and orchestration-read authorization. Incorrect folding or event-source checks could leak stale/wrong quota data or skip live updates.

Overview
Adds a Subscription tab on Usage (web and mobile, default view) that shows current Codex/Claude rate limits, resets, credits, and spend/extra-usage fields—without mixing them into transcript-based Historical usage.

Server: new SubscriptionAllowanceService demand-scopes reads, 5-minute refresh, reset-based staleness, and folds sparse account.rate-limits.updated events into the last complete snapshot. Claude/Codex drivers gain allowance readers (SDK get_usage / Codex account/rateLimits/read) with timeouts. New RPCs subscribeSubscriptionAllowance and server.refreshSubscriptionAllowance require orchestration:read. Codex rate-limit notifications now emit only validated rateLimits payloads; runtime events carry an internal adapter source so replaced instances cannot fold updates.

Clients: shared reconcileSubscriptionAllowances keeps environments/instances separate, groups only verified identities, and never blends windows. UI cards show progress, notices, and sources; switching away from Subscription unmounts the stream.

^{Reviewed by Cursor Bugbot for commit 40853ac. Bugbot is set up for automated code reviews on this repo. Configure here.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 92c669ec-4a0e-4bbf-9ac2-bae163641b8a

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Reviewed the new Effect service code (SubscriptionAllowanceService, ProviderAllowanceReader, the Codex/Claude allowance readers) against the service conventions. The service definition/layer layout and namespace imports look fine; three findings on dependency acquisition and error modelling are below.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

Approvability

Verdict: Skipped

Macroscope did not run approvability analysis for this PR. Macroscope could not determine whether this PR modifies its approvability configuration, so the PR was not approved automatically. A PR that may change the rules that govern approval is never approved automatically.

[macroscopeapp]

Reviewed the web usage surface for shared-primitive, Tailwind-ownership, and theming consistency. Five concrete issues in apps/web/src/components/usage/UsagePage.tsx, three of which break the build or the rendered UI.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

UI consistency review of the new web Usage surfaces. Two findings on apps/web/src/components/usage/UsagePage.tsx; the issues flagged on the previous revision (duplicate Button import, missing PROVIDER_LABEL/PROVIDER_COLOR, bare text-amber-600, mismatched refresh control, topbar header classes) are resolved.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Two consistency findings on the new Subscription view in apps/web/src/components/usage/UsagePage.tsx. The previously raised points about the hand-rolled UsageViewTabs segmented control and the duplicated page frame are unchanged and still stand; they are not repeated inline here.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One finding: the new Usage view switch is a raw-button reconstruction of the app's segmented ToggleGroup, which the same page already uses for the metric and period switches.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

UI consistency review of the changed web usage surface (apps/web/src/components/usage/UsagePage.tsx). The Subscription/Historical switch now goes through ToggleGroup variant="segmented", the card/notice surfaces match the page's existing square border border-border idiom, and the stale label uses the warning-foreground token, so those are consistent. Two issues remain on changed lines, both in the new Subscription view.

^{Posted via Macroscope — UI Consistency}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit f8723f3. Configure here.}

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

Closing this PR after an automated pass over open pull requests. Competes with Theo's existing provider-limit proposal in #5739.

[naveed949]

What Changed

Adds a Subscription view to Settings → Usage for current provider-reported allowance data, while keeping the existing Historical usage view independent.

• Adds snapshot-first, live-updating subscription allowance reporting for Codex and Claude.
• Adds additive RPC contracts, server lifecycle handling, refresh, staleness, compatibility, and privacy-safe provider identity behavior.
• Adds a shared web/mobile projection that keeps provider sources inspectable and never blends allowance windows across environments.
• Adds Subscription UI, manual refresh, and mobile pull-to-refresh alongside unchanged Historical controls.
• Documents user behavior, implementation boundaries, and release evidence requirements.
• Adds focused contract, provider-reader, server, runtime, web, and mobile tests.

Why

Historical usage is transcript-derived activity and API-equivalent cost; it does not show the current limits of a user’s Codex or Claude subscription. This adds a separate, provider-native allowance view without inferring quotas, account status, or billing information that a provider did not report.

UI Changes

Before/after screenshots for web and mobile still need to be attached before review. A short recording should also be included if refresh or live-update behavior is demonstrated.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

Model and harness: verify and fill from the implementation run before review.

Note

Add subscription allowance reporting for Claude and Codex providers

• Adds a new 'Subscription' usage view on web and mobile, showing per-provider allowance cards, progress bars, and metadata
• Implements backend SubscriptionAllowanceService to read, fold, and stream allowance snapshots with periodic refresh and live updates
• Introduces allowance readers for Claude and Codex providers to map native rate-limit data into a common SubscriptionAllowance shape
• Adds serverRefreshSubscriptionAllowance and subscribeSubscriptionAllowance WS RPC endpoints backed by AuthOrchestrationReadScope
• Behavioral Change: createEnvironmentRpcSubscriptionAtomFamily accepts failOnMethodNotFound; the new subscription stream terminates on older backends lacking the method

^{Macroscope summarized 40853ac.}

---

Note

High Risk
Touches provider drivers, runtime event tagging, new WS RPCs, and orchestration-read authorization. Incorrect folding or event-source checks could leak stale/wrong quota data or skip live updates.

Overview
Adds a Subscription tab on Usage (web and mobile, default view) that shows current Codex/Claude rate limits, resets, credits, and spend/extra-usage fields—without mixing them into transcript-based Historical usage.

Server: new SubscriptionAllowanceService demand-scopes reads, 5-minute refresh, reset-based staleness, and folds sparse account.rate-limits.updated events into the last complete snapshot. Claude/Codex drivers gain allowance readers (SDK get_usage / Codex account/rateLimits/read) with timeouts. New RPCs subscribeSubscriptionAllowance and server.refreshSubscriptionAllowance require orchestration:read. Codex rate-limit notifications now emit only validated rateLimits payloads; runtime events carry an internal adapter source so replaced instances cannot fold updates.

Clients: shared reconcileSubscriptionAllowances keeps environments/instances separate, groups only verified identities, and never blends windows. UI cards show progress, notices, and sources; switching away from Subscription unmounts the stream.

^{Reviewed by Cursor Bugbot for commit 40853ac. Bugbot is set up for automated code reviews on this repo. Configure here.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 92c669ec-4a0e-4bbf-9ac2-bae163641b8a

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Reviewed the new Effect service code (SubscriptionAllowanceService, ProviderAllowanceReader, the Codex/Claude allowance readers) against the service conventions. The service definition/layer layout and namespace imports look fine; three findings on dependency acquisition and error modelling are below.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

Approvability

Verdict: Skipped

Macroscope did not run approvability analysis for this PR. Macroscope could not determine whether this PR modifies its approvability configuration, so the PR was not approved automatically. A PR that may change the rules that govern approval is never approved automatically.

[macroscopeapp]

Reviewed the web usage surface for shared-primitive, Tailwind-ownership, and theming consistency. Five concrete issues in apps/web/src/components/usage/UsagePage.tsx, three of which break the build or the rendered UI.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

UI consistency review of the new web Usage surfaces. Two findings on apps/web/src/components/usage/UsagePage.tsx; the issues flagged on the previous revision (duplicate Button import, missing PROVIDER_LABEL/PROVIDER_COLOR, bare text-amber-600, mismatched refresh control, topbar header classes) are resolved.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Two consistency findings on the new Subscription view in apps/web/src/components/usage/UsagePage.tsx. The previously raised points about the hand-rolled UsageViewTabs segmented control and the duplicated page frame are unchanged and still stand; they are not repeated inline here.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One finding: the new Usage view switch is a raw-button reconstruction of the app's segmented ToggleGroup, which the same page already uses for the metric and period switches.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

UI consistency review of the changed web usage surface (apps/web/src/components/usage/UsagePage.tsx). The Subscription/Historical switch now goes through ToggleGroup variant="segmented", the card/notice surfaces match the page's existing square border border-border idiom, and the stale label uses the warning-foreground token, so those are consistent. Two issues remain on changed lines, both in the new Subscription view.

^{Posted via Macroscope — UI Consistency}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit f8723f3. Configure here.}

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

Closing this PR after an automated pass over open pull requests. Competes with Theo's existing provider-limit proposal in #5739.

[naveed949]

What Changed

Adds a Subscription view to Settings → Usage for current provider-reported allowance data, while keeping the existing Historical usage view independent.

• Adds snapshot-first, live-updating subscription allowance reporting for Codex and Claude.
• Adds additive RPC contracts, server lifecycle handling, refresh, staleness, compatibility, and privacy-safe provider identity behavior.
• Adds a shared web/mobile projection that keeps provider sources inspectable and never blends allowance windows across environments.
• Adds Subscription UI, manual refresh, and mobile pull-to-refresh alongside unchanged Historical controls.
• Documents user behavior, implementation boundaries, and release evidence requirements.
• Adds focused contract, provider-reader, server, runtime, web, and mobile tests.

Why

Historical usage is transcript-derived activity and API-equivalent cost; it does not show the current limits of a user’s Codex or Claude subscription. This adds a separate, provider-native allowance view without inferring quotas, account status, or billing information that a provider did not report.

UI Changes

Before/after screenshots for web and mobile still need to be attached before review. A short recording should also be included if refresh or live-update behavior is demonstrated.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

Model and harness: verify and fill from the implementation run before review.

Note

Add subscription allowance reporting for Claude and Codex providers

• Adds a new 'Subscription' usage view on web and mobile, showing per-provider allowance cards, progress bars, and metadata
• Implements backend SubscriptionAllowanceService to read, fold, and stream allowance snapshots with periodic refresh and live updates
• Introduces allowance readers for Claude and Codex providers to map native rate-limit data into a common SubscriptionAllowance shape
• Adds serverRefreshSubscriptionAllowance and subscribeSubscriptionAllowance WS RPC endpoints backed by AuthOrchestrationReadScope
• Behavioral Change: createEnvironmentRpcSubscriptionAtomFamily accepts failOnMethodNotFound; the new subscription stream terminates on older backends lacking the method

^{Macroscope summarized 40853ac.}

---

Note

High Risk
Touches provider drivers, runtime event tagging, new WS RPCs, and orchestration-read authorization. Incorrect folding or event-source checks could leak stale/wrong quota data or skip live updates.

Overview
Adds a Subscription tab on Usage (web and mobile, default view) that shows current Codex/Claude rate limits, resets, credits, and spend/extra-usage fields—without mixing them into transcript-based Historical usage.

Server: new SubscriptionAllowanceService demand-scopes reads, 5-minute refresh, reset-based staleness, and folds sparse account.rate-limits.updated events into the last complete snapshot. Claude/Codex drivers gain allowance readers (SDK get_usage / Codex account/rateLimits/read) with timeouts. New RPCs subscribeSubscriptionAllowance and server.refreshSubscriptionAllowance require orchestration:read. Codex rate-limit notifications now emit only validated rateLimits payloads; runtime events carry an internal adapter source so replaced instances cannot fold updates.

Clients: shared reconcileSubscriptionAllowances keeps environments/instances separate, groups only verified identities, and never blends windows. UI cards show progress, notices, and sources; switching away from Subscription unmounts the stream.

^{Reviewed by Cursor Bugbot for commit 40853ac. Bugbot is set up for automated code reviews on this repo. Configure here.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 92c669ec-4a0e-4bbf-9ac2-bae163641b8a

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Reviewed the new Effect service code (SubscriptionAllowanceService, ProviderAllowanceReader, the Codex/Claude allowance readers) against the service conventions. The service definition/layer layout and namespace imports look fine; three findings on dependency acquisition and error modelling are below.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

Approvability

Verdict: Skipped

Macroscope did not run approvability analysis for this PR. Macroscope could not determine whether this PR modifies its approvability configuration, so the PR was not approved automatically. A PR that may change the rules that govern approval is never approved automatically.

[macroscopeapp]

Reviewed the web usage surface for shared-primitive, Tailwind-ownership, and theming consistency. Five concrete issues in apps/web/src/components/usage/UsagePage.tsx, three of which break the build or the rendered UI.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

UI consistency review of the new web Usage surfaces. Two findings on apps/web/src/components/usage/UsagePage.tsx; the issues flagged on the previous revision (duplicate Button import, missing PROVIDER_LABEL/PROVIDER_COLOR, bare text-amber-600, mismatched refresh control, topbar header classes) are resolved.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Two consistency findings on the new Subscription view in apps/web/src/components/usage/UsagePage.tsx. The previously raised points about the hand-rolled UsageViewTabs segmented control and the duplicated page frame are unchanged and still stand; they are not repeated inline here.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One finding: the new Usage view switch is a raw-button reconstruction of the app's segmented ToggleGroup, which the same page already uses for the metric and period switches.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

UI consistency review of the changed web usage surface (apps/web/src/components/usage/UsagePage.tsx). The Subscription/Historical switch now goes through ToggleGroup variant="segmented", the card/notice surfaces match the page's existing square border border-border idiom, and the stale label uses the warning-foreground token, so those are consistent. Two issues remain on changed lines, both in the new Subscription view.

^{Posted via Macroscope — UI Consistency}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit f8723f3. Configure here.}

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

Closing this PR after an automated pass over open pull requests. Competes with Theo's existing provider-limit proposal in #5739.

[naveed949]

What Changed

Adds a Subscription view to Settings → Usage for current provider-reported allowance data, while keeping the existing Historical usage view independent.

• Adds snapshot-first, live-updating subscription allowance reporting for Codex and Claude.
• Adds additive RPC contracts, server lifecycle handling, refresh, staleness, compatibility, and privacy-safe provider identity behavior.
• Adds a shared web/mobile projection that keeps provider sources inspectable and never blends allowance windows across environments.
• Adds Subscription UI, manual refresh, and mobile pull-to-refresh alongside unchanged Historical controls.
• Documents user behavior, implementation boundaries, and release evidence requirements.
• Adds focused contract, provider-reader, server, runtime, web, and mobile tests.

Why

Historical usage is transcript-derived activity and API-equivalent cost; it does not show the current limits of a user’s Codex or Claude subscription. This adds a separate, provider-native allowance view without inferring quotas, account status, or billing information that a provider did not report.

UI Changes

Before/after screenshots for web and mobile still need to be attached before review. A short recording should also be included if refresh or live-update behavior is demonstrated.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

Model and harness: verify and fill from the implementation run before review.

Note

Add subscription allowance reporting for Claude and Codex providers

• Adds a new 'Subscription' usage view on web and mobile, showing per-provider allowance cards, progress bars, and metadata
• Implements backend SubscriptionAllowanceService to read, fold, and stream allowance snapshots with periodic refresh and live updates
• Introduces allowance readers for Claude and Codex providers to map native rate-limit data into a common SubscriptionAllowance shape
• Adds serverRefreshSubscriptionAllowance and subscribeSubscriptionAllowance WS RPC endpoints backed by AuthOrchestrationReadScope
• Behavioral Change: createEnvironmentRpcSubscriptionAtomFamily accepts failOnMethodNotFound; the new subscription stream terminates on older backends lacking the method

^{Macroscope summarized 40853ac.}

---

Note

High Risk
Touches provider drivers, runtime event tagging, new WS RPCs, and orchestration-read authorization. Incorrect folding or event-source checks could leak stale/wrong quota data or skip live updates.

Overview
Adds a Subscription tab on Usage (web and mobile, default view) that shows current Codex/Claude rate limits, resets, credits, and spend/extra-usage fields—without mixing them into transcript-based Historical usage.

Server: new SubscriptionAllowanceService demand-scopes reads, 5-minute refresh, reset-based staleness, and folds sparse account.rate-limits.updated events into the last complete snapshot. Claude/Codex drivers gain allowance readers (SDK get_usage / Codex account/rateLimits/read) with timeouts. New RPCs subscribeSubscriptionAllowance and server.refreshSubscriptionAllowance require orchestration:read. Codex rate-limit notifications now emit only validated rateLimits payloads; runtime events carry an internal adapter source so replaced instances cannot fold updates.

Clients: shared reconcileSubscriptionAllowances keeps environments/instances separate, groups only verified identities, and never blends windows. UI cards show progress, notices, and sources; switching away from Subscription unmounts the stream.

^{Reviewed by Cursor Bugbot for commit 40853ac. Bugbot is set up for automated code reviews on this repo. Configure here.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 92c669ec-4a0e-4bbf-9ac2-bae163641b8a

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Reviewed the new Effect service code (SubscriptionAllowanceService, ProviderAllowanceReader, the Codex/Claude allowance readers) against the service conventions. The service definition/layer layout and namespace imports look fine; three findings on dependency acquisition and error modelling are below.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

Approvability

Verdict: Skipped

Macroscope did not run approvability analysis for this PR. Macroscope could not determine whether this PR modifies its approvability configuration, so the PR was not approved automatically. A PR that may change the rules that govern approval is never approved automatically.

[macroscopeapp]

Reviewed the web usage surface for shared-primitive, Tailwind-ownership, and theming consistency. Five concrete issues in apps/web/src/components/usage/UsagePage.tsx, three of which break the build or the rendered UI.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

UI consistency review of the new web Usage surfaces. Two findings on apps/web/src/components/usage/UsagePage.tsx; the issues flagged on the previous revision (duplicate Button import, missing PROVIDER_LABEL/PROVIDER_COLOR, bare text-amber-600, mismatched refresh control, topbar header classes) are resolved.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Two consistency findings on the new Subscription view in apps/web/src/components/usage/UsagePage.tsx. The previously raised points about the hand-rolled UsageViewTabs segmented control and the duplicated page frame are unchanged and still stand; they are not repeated inline here.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One finding: the new Usage view switch is a raw-button reconstruction of the app's segmented ToggleGroup, which the same page already uses for the metric and period switches.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

UI consistency review of the changed web usage surface (apps/web/src/components/usage/UsagePage.tsx). The Subscription/Historical switch now goes through ToggleGroup variant="segmented", the card/notice surfaces match the page's existing square border border-border idiom, and the stale label uses the warning-foreground token, so those are consistent. Two issues remain on changed lines, both in the new Subscription view.

^{Posted via Macroscope — UI Consistency}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit f8723f3. Configure here.}

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

Closing this PR after an automated pass over open pull requests. Competes with Theo's existing provider-limit proposal in #5739.

[naveed949]

What Changed

Adds a Subscription view to Settings → Usage for current provider-reported allowance data, while keeping the existing Historical usage view independent.

• Adds snapshot-first, live-updating subscription allowance reporting for Codex and Claude.
• Adds additive RPC contracts, server lifecycle handling, refresh, staleness, compatibility, and privacy-safe provider identity behavior.
• Adds a shared web/mobile projection that keeps provider sources inspectable and never blends allowance windows across environments.
• Adds Subscription UI, manual refresh, and mobile pull-to-refresh alongside unchanged Historical controls.
• Documents user behavior, implementation boundaries, and release evidence requirements.
• Adds focused contract, provider-reader, server, runtime, web, and mobile tests.

Why

Historical usage is transcript-derived activity and API-equivalent cost; it does not show the current limits of a user’s Codex or Claude subscription. This adds a separate, provider-native allowance view without inferring quotas, account status, or billing information that a provider did not report.

UI Changes

Before/after screenshots for web and mobile still need to be attached before review. A short recording should also be included if refresh or live-update behavior is demonstrated.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

Model and harness: verify and fill from the implementation run before review.

Note

Add subscription allowance reporting for Claude and Codex providers

• Adds a new 'Subscription' usage view on web and mobile, showing per-provider allowance cards, progress bars, and metadata
• Implements backend SubscriptionAllowanceService to read, fold, and stream allowance snapshots with periodic refresh and live updates
• Introduces allowance readers for Claude and Codex providers to map native rate-limit data into a common SubscriptionAllowance shape
• Adds serverRefreshSubscriptionAllowance and subscribeSubscriptionAllowance WS RPC endpoints backed by AuthOrchestrationReadScope
• Behavioral Change: createEnvironmentRpcSubscriptionAtomFamily accepts failOnMethodNotFound; the new subscription stream terminates on older backends lacking the method

^{Macroscope summarized 40853ac.}

---

Note

High Risk
Touches provider drivers, runtime event tagging, new WS RPCs, and orchestration-read authorization. Incorrect folding or event-source checks could leak stale/wrong quota data or skip live updates.

Overview
Adds a Subscription tab on Usage (web and mobile, default view) that shows current Codex/Claude rate limits, resets, credits, and spend/extra-usage fields—without mixing them into transcript-based Historical usage.

Server: new SubscriptionAllowanceService demand-scopes reads, 5-minute refresh, reset-based staleness, and folds sparse account.rate-limits.updated events into the last complete snapshot. Claude/Codex drivers gain allowance readers (SDK get_usage / Codex account/rateLimits/read) with timeouts. New RPCs subscribeSubscriptionAllowance and server.refreshSubscriptionAllowance require orchestration:read. Codex rate-limit notifications now emit only validated rateLimits payloads; runtime events carry an internal adapter source so replaced instances cannot fold updates.

Clients: shared reconcileSubscriptionAllowances keeps environments/instances separate, groups only verified identities, and never blends windows. UI cards show progress, notices, and sources; switching away from Subscription unmounts the stream.

^{Reviewed by Cursor Bugbot for commit 40853ac. Bugbot is set up for automated code reviews on this repo. Configure here.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 92c669ec-4a0e-4bbf-9ac2-bae163641b8a

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Reviewed the new Effect service code (SubscriptionAllowanceService, ProviderAllowanceReader, the Codex/Claude allowance readers) against the service conventions. The service definition/layer layout and namespace imports look fine; three findings on dependency acquisition and error modelling are below.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

Approvability

Verdict: Skipped

Macroscope did not run approvability analysis for this PR. Macroscope could not determine whether this PR modifies its approvability configuration, so the PR was not approved automatically. A PR that may change the rules that govern approval is never approved automatically.

[macroscopeapp]

Reviewed the web usage surface for shared-primitive, Tailwind-ownership, and theming consistency. Five concrete issues in apps/web/src/components/usage/UsagePage.tsx, three of which break the build or the rendered UI.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

UI consistency review of the new web Usage surfaces. Two findings on apps/web/src/components/usage/UsagePage.tsx; the issues flagged on the previous revision (duplicate Button import, missing PROVIDER_LABEL/PROVIDER_COLOR, bare text-amber-600, mismatched refresh control, topbar header classes) are resolved.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Two consistency findings on the new Subscription view in apps/web/src/components/usage/UsagePage.tsx. The previously raised points about the hand-rolled UsageViewTabs segmented control and the duplicated page frame are unchanged and still stand; they are not repeated inline here.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One finding: the new Usage view switch is a raw-button reconstruction of the app's segmented ToggleGroup, which the same page already uses for the metric and period switches.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

UI consistency review of the changed web usage surface (apps/web/src/components/usage/UsagePage.tsx). The Subscription/Historical switch now goes through ToggleGroup variant="segmented", the card/notice surfaces match the page's existing square border border-border idiom, and the stale label uses the warning-foreground token, so those are consistent. Two issues remain on changed lines, both in the new Subscription view.

^{Posted via Macroscope — UI Consistency}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit f8723f3. Configure here.}

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

Closing this PR after an automated pass over open pull requests. Competes with Theo's existing provider-limit proposal in #5739.

[naveed949]

What Changed

Adds a Subscription view to Settings → Usage for current provider-reported allowance data, while keeping the existing Historical usage view independent.

• Adds snapshot-first, live-updating subscription allowance reporting for Codex and Claude.
• Adds additive RPC contracts, server lifecycle handling, refresh, staleness, compatibility, and privacy-safe provider identity behavior.
• Adds a shared web/mobile projection that keeps provider sources inspectable and never blends allowance windows across environments.
• Adds Subscription UI, manual refresh, and mobile pull-to-refresh alongside unchanged Historical controls.
• Documents user behavior, implementation boundaries, and release evidence requirements.
• Adds focused contract, provider-reader, server, runtime, web, and mobile tests.

Why

Historical usage is transcript-derived activity and API-equivalent cost; it does not show the current limits of a user’s Codex or Claude subscription. This adds a separate, provider-native allowance view without inferring quotas, account status, or billing information that a provider did not report.

UI Changes

Before/after screenshots for web and mobile still need to be attached before review. A short recording should also be included if refresh or live-update behavior is demonstrated.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

Model and harness: verify and fill from the implementation run before review.

Note

Add subscription allowance reporting for Claude and Codex providers

• Adds a new 'Subscription' usage view on web and mobile, showing per-provider allowance cards, progress bars, and metadata
• Implements backend SubscriptionAllowanceService to read, fold, and stream allowance snapshots with periodic refresh and live updates
• Introduces allowance readers for Claude and Codex providers to map native rate-limit data into a common SubscriptionAllowance shape
• Adds serverRefreshSubscriptionAllowance and subscribeSubscriptionAllowance WS RPC endpoints backed by AuthOrchestrationReadScope
• Behavioral Change: createEnvironmentRpcSubscriptionAtomFamily accepts failOnMethodNotFound; the new subscription stream terminates on older backends lacking the method

^{Macroscope summarized 40853ac.}

---

Note

High Risk
Touches provider drivers, runtime event tagging, new WS RPCs, and orchestration-read authorization. Incorrect folding or event-source checks could leak stale/wrong quota data or skip live updates.

Overview
Adds a Subscription tab on Usage (web and mobile, default view) that shows current Codex/Claude rate limits, resets, credits, and spend/extra-usage fields—without mixing them into transcript-based Historical usage.

Server: new SubscriptionAllowanceService demand-scopes reads, 5-minute refresh, reset-based staleness, and folds sparse account.rate-limits.updated events into the last complete snapshot. Claude/Codex drivers gain allowance readers (SDK get_usage / Codex account/rateLimits/read) with timeouts. New RPCs subscribeSubscriptionAllowance and server.refreshSubscriptionAllowance require orchestration:read. Codex rate-limit notifications now emit only validated rateLimits payloads; runtime events carry an internal adapter source so replaced instances cannot fold updates.

Clients: shared reconcileSubscriptionAllowances keeps environments/instances separate, groups only verified identities, and never blends windows. UI cards show progress, notices, and sources; switching away from Subscription unmounts the stream.

^{Reviewed by Cursor Bugbot for commit 40853ac. Bugbot is set up for automated code reviews on this repo. Configure here.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 92c669ec-4a0e-4bbf-9ac2-bae163641b8a

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Reviewed the new Effect service code (SubscriptionAllowanceService, ProviderAllowanceReader, the Codex/Claude allowance readers) against the service conventions. The service definition/layer layout and namespace imports look fine; three findings on dependency acquisition and error modelling are below.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

Approvability

Verdict: Skipped

Macroscope did not run approvability analysis for this PR. Macroscope could not determine whether this PR modifies its approvability configuration, so the PR was not approved automatically. A PR that may change the rules that govern approval is never approved automatically.

[macroscopeapp]

Reviewed the web usage surface for shared-primitive, Tailwind-ownership, and theming consistency. Five concrete issues in apps/web/src/components/usage/UsagePage.tsx, three of which break the build or the rendered UI.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

UI consistency review of the new web Usage surfaces. Two findings on apps/web/src/components/usage/UsagePage.tsx; the issues flagged on the previous revision (duplicate Button import, missing PROVIDER_LABEL/PROVIDER_COLOR, bare text-amber-600, mismatched refresh control, topbar header classes) are resolved.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Two consistency findings on the new Subscription view in apps/web/src/components/usage/UsagePage.tsx. The previously raised points about the hand-rolled UsageViewTabs segmented control and the duplicated page frame are unchanged and still stand; they are not repeated inline here.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One finding: the new Usage view switch is a raw-button reconstruction of the app's segmented ToggleGroup, which the same page already uses for the metric and period switches.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

UI consistency review of the changed web usage surface (apps/web/src/components/usage/UsagePage.tsx). The Subscription/Historical switch now goes through ToggleGroup variant="segmented", the card/notice surfaces match the page's existing square border border-border idiom, and the stale label uses the warning-foreground token, so those are consistent. Two issues remain on changed lines, both in the new Subscription view.

^{Posted via Macroscope — UI Consistency}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit f8723f3. Configure here.}

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

Closing this PR after an automated pass over open pull requests. Competes with Theo's existing provider-limit proposal in #5739.