docs: update setup for Feb 2026 Spotify API changes#1
Open
workingpleasewait wants to merge 1 commit intoddrayne:mainfrom
Open
docs: update setup for Feb 2026 Spotify API changes#1workingpleasewait wants to merge 1 commit intoddrayne:mainfrom
workingpleasewait wants to merge 1 commit intoddrayne:mainfrom
Conversation
- Replace localhost with 127.0.0.1 in redirect URI (localhost no longer allowed) - Add Feb 2026 API restrictions note (Premium required, 403 quirk on playback) - Add manual auth flow guide for VPS/VM setups without browser access - Document auth-profiles.json field names (access/refresh/expires not camelCase) Tested with Clawdbot running in OrbStack VM on macOS, Feb 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
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 this fixes
Spotify made breaking changes to their Developer Platform in February 2026 that affect new installations of clawdify. This PR updates the README with:
Changes
Redirect URI:
localhostis now blocked — Spotify no longer acceptslocalhostas a redirect URI as of April 2025 enforcement (November 2025 migration deadline). Usehttp://127.0.0.1:8888/callbackinstead. UsinglocalhostreturnsINVALID_CLIENT: Invalid redirect URI.Feb 2026 API restrictions — New Development Mode apps now require the owner to have an active Spotify Premium subscription. Playback control endpoints (play/pause) may return HTTP 403 "Restriction violated" even when the command executes successfully — this is a known quirk, not a failure. Added a note and link to the Spotify migration guide.
Manual auth flow for VPS/VM setups — Added a step-by-step guide for users running Clawdbot on a remote server without direct browser access. Includes a self-contained Node.js listener that exchanges the auth code locally, plus a zsh compatibility note.
Auth profile field names — Documented that
auth-profiles.jsonmust useaccess/refresh/expires(notaccessToken/refreshToken/expiresAt). This mismatch causes silent token refresh failures.Tested on