spogo

Why it's ranked here

Its unusually broad command surface makes it useful beyond basic play and pause controls. Device transfer, library edits, playlist management, listening data, and structured output support real automation. The reliance on browser cookies and internal Spotify endpoints is the central caution.

What's good

Three output styles separate terminal readability from machine consumption. Search covers music, podcasts, artists, albums, and playlists. Playback can target a named device or identifier. Multiple profiles, configurable timeouts, shell completions, color controls, and distinct exit codes make scripts easier to operate and diagnose.

Tradeoffs

Authentication depends on Spotify browser cookies, including a required cookie copied from the web player when automatic import fails. WSL may require manual cookie entry. Some operations cross internal Connect and GraphQL endpoints. Queue clearing is exposed but explicitly unsupported by Spotify's API. Users must consider Spotify's terms.

How to use it well

It suits shell users, automation scripts, and assistants that need repeatable Spotify actions without app registration. Import cookies into a dedicated profile, select the appropriate engine and device, then consume JSON for structured workflows or plain output for pipelines. It does not provide queue clearing or a registered-app authentication flow.

Observed

License

MIT

Primary language

Go

Interface

Command-line application with human, plain, and JSON output

Installation

Homebrew tap or Go install from the module command package

Authentication

Browser cookie import or manual cookie paste, stored per profile

Browser import support

Chrome, Brave, Edge, Firefox, and Safari

Shell integration

Completion generation for Bash, Zsh, and Fish

Platform note

AppleScript engine is macOS-only; manual cookie paste is documented as a WSL fallback