Skip to content

Conversation

@jennmueng
Copy link
Member

Because you can install more than 1 cursor agent integration for an org, it kinda gets confusing. Turns out there's an endpoint to get the email and key name of the owner of the key. We set that in the name to make it clear in uses.

@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Nov 25, 2025
jennmueng added a commit that referenced this pull request Nov 26, 2025
…on (#104007)

People installed multiple cursor integrations and previously this caused
issues, this changes it on the UI so

1. You can configure which cursor integration to use for automation
handoff:
<img width="2916" height="458" alt="CleanShot 2025-11-26 at 03 39 24@2x"
src="https://github.com/user-attachments/assets/30376d56-b723-4d15-a7ae-712981fe7013"
/>

2. You can select which integration to manually call from the seer
drawer:
- Because existing integrations don't have unique names, there's no way
to distinguish between them except their IDs, so as a fallback I have it
show the ID in small text ONLY if at least 2 of the same integrations
have the same name, otherwise #103989 will fix this and give it unique
names)
<img width="906" height="562" alt="CleanShot 2025-11-26 at 03 26 41@2x"
src="https://github.com/user-attachments/assets/16a33cd0-953e-4f1a-a107-cd382f10b60a"
/>
@jennmueng jennmueng merged commit e5271c5 into master Nov 26, 2025
66 checks passed
@jennmueng jennmueng deleted the cursor-agent-include-metadata branch November 26, 2025 20:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants