[codex] fix spotify redirect setup copy#4
Draft
Promansis wants to merge 1 commit into
Draft
Conversation
munimunigamer
added a commit
that referenced
this pull request
May 20, 2026
world-state: preserve pending tracker edits
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
1 participant
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.
What changed
Updated the Spotify agent setup copy so it no longer tells users to set
SPOTIFY_REDIRECT_URIto an HTTPS URL.Why
The native Spotify OAuth flow already uses a fixed loopback callback contract. The old copy advertised an override the app does not honor, which could send users down a dead end.
Impact
Users now see the supported loopback redirect URI and the paste-back fallback that actually works for remote or callback-blocked setups.
Verification
pnpm typecheckcargo check --manifest-path src-tauri/Cargo.toml