-
-
Couldn't load subscription status.
- Fork 1.6k
feat(cursor-bg-agent): docs page for cursor agents #15307
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
Bundle ReportChanges will increase total bundle size by 420 bytes (0.0%) ⬆️. This is within the configured threshold ✅ Detailed changes
Affected Assets, Files, and Routes:view changes for bundle: sentry-docs-server-cjsAssets Changed:
view changes for bundle: sentry-docs-client-array-pushAssets Changed:
|
| description: "The Cursor Background Agent integration allows you to launch Cursor background agents directly from Seer to help debug, fix issues, and create pull requests for you." | ||
| --- | ||
|
|
||
| You can trigger Cursor Background Agents from your [Seer Issue Fix](/product/ai-in-sentry/seer/issue-fix/) tab. The background Agents will be provided with Seer's Root Cause Analysis alongside the issue context. Seer's Root Cause Analysis will provide much needed context for the background agent to understand the issue and generate a solution. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| You can trigger Cursor Background Agents from your [Seer Issue Fix](/product/ai-in-sentry/seer/issue-fix/) tab. The background Agents will be provided with Seer's Root Cause Analysis alongside the issue context. Seer's Root Cause Analysis will provide much needed context for the background agent to understand the issue and generate a solution. | |
| You can trigger Cursor Background Agents from your [Seer Issue Fix](/product/ai-in-sentry/seer/issue-fix/) tab. The background Agents will be provided with Seer's Root Cause Analysis alongside the issue context to help the background agent understand the issue and generate a solution. |
|
|
||
| </Alert> | ||
|
|
||
| 1. Navigate to **Settings > Integrations > Cursor Background Agent** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this in Sentry? Our flow doesn't seem to work like this today, and I don't see this config on Cursor either.
|
|
||
| ## Using the Integration | ||
|
|
||
| Once installed, you can trigger Cursor background agents from the Seer Root Cause Analysis card on any issue. Click the dropdown next to **Find Solution** to launch a Cursor Background Agent. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be nice to see a visual of what it looks like to have Cursor background agent on the Root Cause Analysis card.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This directory seems like unnecessary nesting. I suggest removing it and sticking with just the cursor index file nested under integrations.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we can improve this a little bit.
- Remove "coding agents" directory until we have multiple agents to point to - it seems like a wasteful home page when we can get to the point
- Clarify the proper instructions for installing background agent (maybe link directly to the product if it is in Sentry -
https://sentry.io/settings/integrations/
DESCRIBE YOUR PR
Docs page for the cursor background agent integration.
IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes: