feat(cursor): PostHog error → Cursor autofix automation - #2753
Conversation
Version-control the webhook automation prompt and setup checklist for PostHog Error Tracking → Cursor Cloud Agent → draft PR on easy fixes. Co-authored-by: Martin DONADIEU <martindonadieu@gmail.com>
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 41 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: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
Comment |
Merging this PR will not alter performance
Comparing Footnotes
|
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_59731813-8c76-479c-9464-e708c6281eed) |
There was a problem hiding this comment.
All reported issues were addressed across 1 file
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
Treat webhook fields as untrusted data only, and clarify PostHog Authorization Bearer header setup for the Cursor webhook API key. Co-authored-by: Martin DONADIEU <martindonadieu@gmail.com>
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_5a7e6d71-04aa-4c9d-be21-1d7d4f000346) |
|





Summary (AI generated)
.cursor/automations/posthog-error-autofix.mdwith:Motivation (AI generated)
Cursor has no native PostHog trigger (Sentry exists; PostHog must use webhooks). We want new production errors to spawn a cloud agent that attempts a safe autofix without burning budget on every
$exceptionevent or opening speculative PRs.Business Impact (AI generated)
Faster triage of new console/CLI/backend errors with less human toil. Easy bugs can land as draft PRs automatically; hard bugs stay investigation-only so agent spend stays bounded.
Test Plan (AI generated)
.cursor/automations/posthog-error-autofix.mdManual wiring (required after merge)
This PR only versions the prompt. Activate the loop in two UIs:
cap-go/capgo.app→ paste Agent prompt → enable PR toolDo not use a PostHog real-time destination on every
$exception.Generated with AI