feat(cursor): Make agent display name editable and drop email from default#117559
Merged
Conversation
github-actions
Bot
added
the
Scope: Backend
JoshFerge
force-pushed
the
feat/cursor-editable-display-name
branch
2 times, most recently
from
70523c7 to
c2f62b7
Compare
The Cursor integration's stored display name was auto-generated as
"Cursor Cloud Agent - {email}/{api_key_name}", which surfaced the
key owner's email directly in the coding-agent dropdown when launching
agents. Drop the email so the default is just
"Cursor Cloud Agent - {api_key_name}" (it still lives in metadata and
the configurations list).
Also add an editable "Display Name" field to the integration settings
form. When left blank the auto-generated default is used and stays in
sync with the API key name; when set, the custom name is stored in
metadata and preserved across API key rotations.
Co-Authored-By: Claude <noreply@anthropic.com>
Agent transcript: https://claudescope.sentry.dev/share/ULdM-4nib_15Fd7l-07F8dWVSc6nuGgL1GXZ5n6oV5c
JoshFerge
force-pushed
the
feat/cursor-editable-display-name
branch
from
c2f62b7 to
3cd17b5
Compare
trevor-e
approved these changes
Jun 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Cursor integration's stored display name was auto-generated as
Cursor Cloud Agent - {email}/{api_key_name}, so the API key owner's email showed up directly in the coding-agent dropdown when launching agents from an issue. This drops the email from the default, leavingCursor Cloud Agent - {api_key_name}(the email is still kept in metadata and shown in the configurations list, which is a more appropriate place for it).It also adds an editable Display Name field to the integration settings form. Leaving it blank uses the auto-generated default and keeps it in sync with the API key name; setting a custom value stores it in metadata and preserves it across API key rotations. The settings form renders automatically from
get_organization_config(), so no frontend changes are needed.Existing integrations keep their current (email-bearing) name until the API key is re-saved or a custom name is set — there's no backfill in this PR.
Agent transcript: https://claudescope.sentry.dev/share/xlvzrXTtALmGrxF_vF14RbRl5aIG3nj3MyOOBHR1j4c