Repository navigation
feat(cli): Show account context after setup-code authentication - #2384
Merged
evanpurkhiser merged 1 commit intoNov 18, 2026
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
evanpurkhiser
force-pushed
the
git/feat-cli-show-account-context-in-handoff-setup
branch
from
November 18, 2026 17:53
5864dec to
7d47a05
Compare
evanpurkhiser
deleted the
git/feat-cli-show-account-context-in-handoff-setup
branch
November 18, 2026 18:36
7 tasks done
This branch was previously deployed
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
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.
Setup should show which Sentry account it authenticated so the user or agent can confirm the context before continuing.
Both standalone setup codes and agent handoffs show the account and Sentry host. Handoffs also show the organization name and slug directly above the backend’s verbatim flow instructions.