Repository navigation
Conversation
Fixes #767
|
Warning Review limit reached
Next review available in: 34 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (9)
Comment |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 260efcfc2a
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
[shipping-github] Merge-ready CI green on \ix/767-desktop-native-models\ (Cross-platform CI, enforce-target, react-doctor). No open review threads. Targets \dev\ for #767. |
Keep Grok candidate natives on visibleNativeSlugs and filter Anthropic Desktop discovery through desktopVisibleNativeSlugs.
Verdict: approve-comment
|
|
Landed on
What made this reviewable was applying the gate at every Desktop surface that emits the list — discovery and profile export both — rather than only the one the report happened to name. Keeping Grok natives is also the right call: they are reachable through Desktop, so hiding them would have removed working models. The regression test fails without the change by finding #767 closed alongside. |
Summary
Fixes #767
Opts Claude Desktop model list out of
native/*entries.Test plan
bun run typecheckbun run test