docs: document ctx.launch availability contract for the AI builder#68
Conversation
Add explicit guidance on when ctx.launch is populated (host-owned view refreshes, declarative triggers, startup/wake/login) vs undefined (manual palette opens, ctx.actions.run(), non-triggered ctx.views.refresh()), along with a hard prohibition against hasRenderedCache-style workarounds. Updates the builder system prompt (ai.ts), the API type TSDoc (nevermind-extension-api.d.ts), and the builder skill checklist (SKILL.md).
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Review limit reached
More reviews will be available in 15 minutes and 17 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?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 credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. 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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
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. Comment |
1 participant
The AI builder didn't know when
ctx.launchis populated vsundefined, leading to fragilehasRenderedCache-style workarounds in generated extensions (~30 lines of state tracking in the screenshots extension alone).What's changed
ctx.launchand which leave it undefinedExtensionContext.launchTSDoc expanded with the full availability contract and the canonicalctx.launch?.refreshcheck idiomWhy
Prompt + documentation-only. No host code changes — the host already populates
ctx.launchcorrectly. The builder just didn't know the contract.Closes #63