Spotify CLI for headless Linux servers. Control Spotify playback via terminal using cookie auth (no OAuth callback needed). Perfect for remote servers withou...
Real data. Real impact.
Growing
Developers
Per week
Open source
Skills give you superpowers. Install in 30 seconds.
Control Spotify from headless Linux servers using cookie-based auth. No OAuth callback needed - perfect for remote servers.
The original
spotify-playersteipetespogo auth import --browser chromeThis skill documents the cookie-based workaround - copy 2 browser cookies and you're done. No OAuth, no localhost needed.
# Ubuntu/Debian sudo apt update && sudo apt install -y golang-goOr download latest from https://go.dev/dl/
wget https://go.dev/dl/go1.23.4.linux-amd64.tar.gz sudo tar -C /usr/local -xzf go1.23.4.linux-amd64.tar.gz echo 'export PATH=$PATH:/usr/local/go/bin:~/go/bin' >> ~/.bashrc source ~/.bashrc
go install github.com/steipete/spogo/cmd/spogo@latest
This installs to
~/go/bin/spogoecho 'export PATH=$PATH:~/go/bin' >> ~/.bashrc source ~/.bashrc
spogo --version # spogo v0.2.0
Since OAuth requires localhost callback (impossible on remote servers), we use cookie auth instead.
Have the user open DevTools → Application → Cookies →
open.spotify.comsp_dcsp_tCreate
~/.config/spogo/config.tomldefault_profile = "default"[profile.default] cookie_path = "~/.config/spogo/cookies/default.json" market = "IL" language = "en"
Create
~/.config/spogo/cookies/default.json[ { "name": "sp_dc", "value": "USER_SP_DC_VALUE", "domain": ".spotify.com", "path": "/", "expires": "2027-01-01T00:00:00Z", "secure": true, "http_only": true }, { "name": "sp_t", "value": "USER_SP_T_VALUE", "domain": ".spotify.com", "path": "/", "expires": "2027-01-01T00:00:00Z", "secure": false, "http_only": false } ]
spogo auth status # → "Cookies: 2 (file)"
# Search spogo search track "query" spogo search track "query" --json --limit 5Play
spogo play spotify:track:ID spogo play # Resume spogo pause spogo next / spogo prev
Devices
spogo device list --json spogo device set "DEVICE_ID"
Status
spogo status spogo status --json
spogo needs an active Spotify session. If no device played recently, you can start one via the browser.
Note: This is optional and only needed when
returns no active devices. It opensspogo device listin the agent's isolated browser profile (not the user's personal browser). The agent only navigates to Spotify and clicks Play — no other browser state is accessed.open.spotify.com
browser open https://open.spotify.com/track/TRACK_ID profile=openclaw
Click Play via browser automation
Transfer to target device:
spogo device set "DEVICE_ID"
The Spotify session stays active for hours after playback.
--engine webNo active Spotify session. Use browser fallback (see above) to start playback first.
Cookies expired. Get fresh cookies from browser and update the JSON file.
Check
spogo device listspogo device set "DEVICE_ID"sp_dcsp_t~/.config/spogo/cookies/api.spotify.comopen.spotify.comopen.spotify.comgo installmarketNo automatic installation available. Please visit the source repository for installation instructions.
View Installation Instructions
1,500+ AI skills, agents & workflows. Install in 30 seconds. Part of the Torly.ai family.
© 2026 Torly.ai. All rights reserved.