Winamp energy, terminal habits
cliamp is a terminal music player with a much wider reach than its retro styling suggests. Point it at a directory or a set of files and it behaves like a local player. It can also open a stream, search a directory of more than 30,000 radio stations, follow podcasts, and connect to services including YouTube, SoundCloud, Spotify, Navidrome, Plex, Jellyfin, Emby, and NetEase Cloud Music. The interface adds playlists, lyrics, a spectrum visualizer, and a parametric equalizer.
That breadth is the main reason to choose it. Many terminal players excel at a carefully indexed local library or act as a client for a separate music daemon. cliamp aims to make the terminal itself the meeting place for files, self-hosted libraries, and web sources. The result feels less austere than a classic Unix player and more like an enthusiastic desktop app squeezed into text cells.
The tradeoff is that these sources do not all have the same reliability or installation story. Local playback is the foundation. Remote providers bring credentials, helper programs, service changes, and platform-specific gaps. Buyers should judge cliamp as a promising multi-source player, not as a single binary that makes every music service equally dependable.
Local playback is the easy win
The shortest path is credible. Homebrew users install a tap formula, Arch users have an AUR package, and the release page provides Linux, macOS, and Windows builds. Starting the player with a music directory or file pattern is enough to get sound, and Ctrl+K reveals the keybindings. Linux release binaries statically include FLAC, Vorbis, and Ogg support.
There are platform details behind that simplicity. Downloaded macOS binaries dynamically link against Homebrew versions of those codec libraries, so the one-line install script still requires flac, libvorbis, and libogg. Homebrew's formula installs them automatically and is the more sensible route. Linux users building from source need Go 1.25.5 or newer and ALSA development headers. PipeWire and PulseAudio systems can also need an ALSA bridge when the application appears to play but produces silence.
Extra formats and web sources expand the dependency list. AAC, ALAC, Opus, and WMA use ffmpeg. YouTube, YouTube Music, SoundCloud, Bandcamp, Bilibili, and NetEase Cloud Music rely on yt-dlp. These are common tools with good package availability, but they turn provider support into a chain: cliamp, its configuration, the helper, and the remote service must all keep agreeing.
The provider list is useful, with real boundaries
The interactive cliamp setup command is a thoughtful response to configuration sprawl. It prompts for remote-provider details, tests the connection, and writes the appropriate TOML block. Dedicated documentation exists for major services, playlists, themes, plugins, headless operation, remote control, SSH streaming, and media keys. That is much better than asking users to reverse-engineer a large example file.
Personal media servers are a particularly good fit. A developer already running Navidrome, Plex, Jellyfin, or Emby can browse that collection without keeping a browser open. Internet radio is similarly natural in a terminal, with built-in search and a separate file for personal stations. Local files, personal servers, and radio are the parts least exposed to consumer-site breakage.
YouTube illustrates the riskier side. A detailed open report says restarting or repeating a track can encounter transient 403 responses from yt-dlp, and cliamp does not retry the failed pipe. The reporter reproduced the upstream failures outside cliamp, so this is not simply a defect in the player. It still means a listener can lose playback because one dependency had a bad request and the player did not recover. Treat video-site support as convenient, not guaranteed.
Windows has firmer limitations. The README says Spotify is unavailable in Windows builds. An open request seeking a workaround remained active in August 2026. Other reports describe the built-in upgrader failing because Windows will not replace the running executable, FLAC playback returning an error despite standalone ffmpeg working, and a radio stream unexpectedly moving to another station. These reports affect different versions and may not reproduce for everyone, but together they justify choosing Linux or macOS for the first trial.
A fast-moving project, not a finished appliance
cliamp was created in February 2026 and had already reached release v1.63.2 by August 13. The last push was August 16, and issues and pull requests were still being updated on August 17. That is exceptional momentum. The latest release increased the radio playback buffer and updated a security dependency, evidence that maintenance covers both daily use and underlying packages.
The repository's open count includes issues and pull requests, so 48 should not be presented as 48 confirmed bugs. The queue includes enhancements such as cover art and custom equalizer settings alongside concrete defects and contributed features. Recent pull requests for dynamic directory playlists and richer file metadata also show that development is not confined to the original author.
Fast release numbering should not be confused with long operational history. Six months is too little time to see how well every provider survives repeated API, authentication, and media-delivery changes. The plugin system, remote controls, headless mode, and wide provider roster all increase the surface that maintainers must keep working. The project is already useful, but its breadth currently outruns its maturity.
Who should install it
Choose cliamp if your music life is split between a local folder, internet radio, and one or more supported servers or web sources, and you want to control it without leaving the terminal. The interface has personality, installation is reasonable on its strongest platforms, and the documentation is unusually attentive for such a young project.
Choose cmus for a mature local-library player, Termusic for another self-contained TUI approach, or ncmpcpp when an MPD server already owns playback. Those tools accept narrower jobs and gain predictability from that focus. cliamp wins when variety is the point. Install it on Linux or macOS, start with local files, then add providers one at a time so a broken credential or helper does not turn setup into guesswork.