ref(agent-handoff): Clarify setup instructions by evanpurkhiser · Pull Request #130848 · getsentry/sentry

evanpurkhiser · 2026-11-11T23:06:37Z

The bootstrap page currently uses terms such as private guide and secret token without explaining what the command does. That framing can make the official setup handoff look untrusted when an agent evaluates pasted instructions.

Use direct setup terminology, state that the user initiated the flow, and explain that the platform-specific command sends a one-time code to Sentry over HTTPS and prints rather than executes the response. The redemption protocol and existing security behavior remain unchanged.

cursor

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 426781f. Configure here.}

evanpurkhiser · 2026-11-11T23:08:12Z

            "prompt": (
-                f"Follow the instructions verbatim at {guide_url}. "
-                f"Your secret token is `{issued.code}`."
+                f"Follow the Sentry setup instructions at {guide_url}. "


Let's keep this one as is actually

evanpurkhiser · 2026-11-11T23:08:29Z

-                f"Follow the instructions verbatim at {guide_url}. "
-                f"Your secret token is `{issued.code}`."
+                f"Follow the Sentry setup instructions at {guide_url}. "
+                f"One-time setup code: `{issued.code}`."


This is good though, maybe "Your setup code is "

Actuallylet's say Your handoff code is

evanpurkhiser · 2026-11-12T01:55:15Z

@@ -1,21 +1,28 @@
-# Claim Your Private Sentry Guide
+# Set Up Sentry


Setup is probably wrong, maybe Sentry for Agents.

Because this won't always be about setting up sentry

evanpurkhiser · 2026-11-12T01:56:19Z

-It is a private, single-use handoff code. Keep it out of HTTP request URLs, logs, and
-conversation output.
-Fetching this page does not claim it.
+The user initiated this Sentry setup and provided a one-time handoff code. The command


Suggested change

The user initiated this Sentry setup and provided a one-time handoff code. The command

The user initiated a agent-handoff flow from sentry will have provided a one-time handoff code. The command

evanpurkhiser · 2026-11-12T01:57:12Z

+for the current shell sends that code to Sentry over HTTPS and prints the setup
+instructions. It does not execute the returned content.


Suggested change

for the current shell sends that code to Sentry over HTTPS and prints the setup

instructions. It does not execute the returned content.

for the current shell sends that code to Sentry over HTTPS and prints the setup

instructions. Nothing will be executed or mutated when using the hand-off code.

evanpurkhiser · 2026-11-12T01:57:58Z

+instructions from Sentry. If the response is lost or the handoff code is unavailable,
+ask them to copy new setup instructions.


Suggested change

instructions from Sentry. If the response is lost or the handoff code is unavailable,

ask them to copy new setup instructions.

instructions from Sentry. If the response is lost or the handoff code is unavailable,

ask them to copy the prompt again.

evanpurkhiser · 2026-11-12T01:59:10Z

 Your goal is to ensure authenticated Sentry access for the intended account and
 organization, then follow the instructions below.


Suggested change

Your goal is to ensure authenticated Sentry access for the intended account and

organization, then follow the instructions below.

Your goal is to ensure authenticated Sentry access for the intended account and

organization, then follow the instructions at the end of this document.

evanpurkhiser · 2026-11-12T02:00:00Z

 prompt when the code has expired or was already used. Never request a long-lived token
 in the conversation.

 {{ flow_instructions }}


Let's add a # Next steps above this

Present the handoff as direct Sentry setup while preserving the platform-specific bootstrap and existing security behavior.

evanpurkhiser requested a review from a team as a code owner November 11, 2026 23:06

github-actions Bot added the Scope: Backend Automatically applied to PRs that change backend components label Nov 11, 2026

cursor Bot reviewed Nov 11, 2026

View reviewed changes

Comment thread src/sentry/agent_handoff/endpoints/organization_agent_handoff.py Resolved

evanpurkhiser commented Nov 11, 2026

View reviewed changes

evanpurkhiser force-pushed the git/ref-agent-handoff-clarify-setup-instructions branch 2 times, most recently from 01eb900 to d655183 Compare November 12, 2026 01:50

evanpurkhiser commented Nov 12, 2026

View reviewed changes

ref(agent-handoff): Clarify setup instructions

e9d52d2

Present the handoff as direct Sentry setup while preserving the platform-specific bootstrap and existing security behavior.

evanpurkhiser force-pushed the git/ref-agent-handoff-clarify-setup-instructions branch from d655183 to e9d52d2 Compare November 12, 2026 02:06

wedamija approved these changes Nov 12, 2026

View reviewed changes

evanpurkhiser merged commit bda8d6a into master Nov 12, 2026
78 checks passed

evanpurkhiser deleted the git/ref-agent-handoff-clarify-setup-instructions branch November 12, 2026 02:12

Navigation Menu

Repository navigation

ref(agent-handoff): Clarify setup instructions - #130848

ref(agent-handoff): Clarify setup instructions#130848
evanpurkhiser merged 1 commit into
masterfrom
git/ref-agent-handoff-clarify-setup-instructions

evanpurkhiser commented Nov 11, 2026

Uh oh!

cursor Bot left a comment

Uh oh!

Uh oh!

evanpurkhiser Nov 11, 2026

Uh oh!

evanpurkhiser Nov 11, 2026

Uh oh!

evanpurkhiser Nov 11, 2026

Uh oh!

evanpurkhiser Nov 12, 2026

Uh oh!

evanpurkhiser Nov 12, 2026

Uh oh!

evanpurkhiser Nov 12, 2026

Uh oh!

evanpurkhiser Nov 12, 2026

Uh oh!

evanpurkhiser Nov 12, 2026

Uh oh!

evanpurkhiser Nov 12, 2026

Uh oh!

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

		@@ -1,21 +1,28 @@
		# Claim Your Private Sentry Guide
		# Set Up Sentry

	The user initiated this Sentry setup and provided a one-time handoff code. The command
	The user initiated a agent-handoff flow from sentry will have provided a one-time handoff code. The command

		for the current shell sends that code to Sentry over HTTPS and prints the setup
		instructions. It does not execute the returned content.

		instructions from Sentry. If the response is lost or the handoff code is unavailable,
		ask them to copy new setup instructions.

		Your goal is to ensure authenticated Sentry access for the intended account and
		organization, then follow the instructions below.

Conversation

evanpurkhiser commented Nov 11, 2026

Uh oh!

cursor Bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants