You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Persist the issuing OAuth client ID for CLI token refresh #2383
The CLI stores OAuth access and refresh tokens with their issuing Sentry host. When it refreshes the token, it resolves the client ID again from the environment or build defaults. Sentry looks up the refresh token under the requesting OAuth application, so refresh fails with invalid_grant if the client ID differs from the one used at login.
This can happen when SENTRY_CLIENT_ID changes after login or when an agent handoff provides a different OAuth client ID. Initial authentication succeeds, then the session fails when the access token expires.
Store the issuing client ID with each OAuth credential and use it for refresh. Keep the existing client ID resolution as a fallback for credentials saved before the change. Add regression coverage for refreshing a credential whose client ID differs from the current default.
Activity
linear-code commentedon Nov 18, 2026
MCP-1256