A standalone music player whose AI assistant never sees your key

A standalone player that treats LX Music import as optional

This is a Windows desktop music player and visualiser, an unofficial derivative maintained on top of an existing open-source project and released under the GPL. The description is specific about a structural choice: it runs independently on local music, and importing playlists from LX Music, plus local device linkage with it, is an optional extension rather than a dependency.

That framing is worth taking at face value, because it changes what the software actually is. A standalone local player with its own library, queue, lyrics and visualisation is a self-contained thing whose value does not depend on any external service or companion app. Bolting on an optional import path for another tool's playlists is a convenience layered on top, not the core of the product, and the README's own use restrictions later in the document reinforce that this is meant to be a local-library player with import conveniences, not a streaming-access tool.

The feature list backs that framing: local file and folder import, custom and folder-based playlists, artist and album browsing, a queue, and a substantial audio and visualisation stack, all of which work on your own files regardless of whether the optional LX Music linkage is ever touched.

An in-app assistant that keeps your API key out of its hands

The most distinctive feature is an in-app agent, invoked by a floating button or a keyboard shortcut, that controls the player through natural-language commands: play a named song, pause, skip, set the volume to a percentage, jump to a timestamp, switch lossless quality, open the library, switch the lyric animation style, create a themed playlist, or hide itself.

The detail that matters most is how the model behind it is configured. Aside from local services such as Ollama, the README states the user must obtain and enter their own API key for whichever model provider they choose, and that the project does not bundle, collect, or hold any key on the user's behalf; requests go directly from the user's machine to the provider they selected, who governs their own terms and privacy policy.

That is the correct architecture for a feature like this, and it is worth contrasting with the alternative most such features quietly choose. A player that bundles a shared key, routes every user's commands through the maintainer's own account, or proxies traffic through a server it controls, has taken on a genuine liability, and put itself in the position of reading and forwarding whatever conversational commands the user types. Requiring users to bring their own key and connect directly to their own chosen provider avoids the maintainer becoming a party to that traffic at all, and it means the natural-language convenience does not come with a new place your commands are collected or stored.

Naming the platforms it is not, in the license section itself

The section on the original project, licensing and usage carries a set of statements that most forks of a popular tool would rather leave unsaid. It states plainly that this project does not represent an official release from the original author, from either of the two major Chinese streaming platforms named, or from any other third-party platform.

That kind of explicit disclaimer matters specifically because this is a derivative work built on someone else's project and distributed under a licence that already requires attribution and source availability. Naming, in the licence section itself, the platforms whose branding or association a casual reader might otherwise infer, closes a gap that a lot of unofficial forks leave open, whether deliberately or through simple omission. It is a small piece of text that does real work in setting expectations correctly before installation.

The same section states the derivative continues to be released under the GPL-3.0-only licence, and that the published source should correspond to what ships in the release installer, which is the correct posture for a GPL derivative and gives anyone suspicious of the binary a stated basis for checking the two against each other.

A prohibition list that names the exact behaviours it forbids

Immediately following the platform disclaimer, the README states four specific things the project must not be used for: pirated music, unauthorised scraping, bypassing platform restrictions, or distributing infringing content, and requires that any locally imported files, source scripts or third-party links the user brings in be things they actually hold legitimate rights to use.

Naming a scraping and platform-bypass prohibition this explicitly, rather than leaving usage boundaries implicit, is the right call for a tool whose category has a genuine history of controversy over exactly those behaviours. It is also the statement a reader should weigh directly against what is visible in the repository's own file tree, which includes modules referencing decryption and authentication tied to a specific Chinese streaming service by name. Nothing in the README states what those specific modules do or whether their function is consistent with the stated prohibition, and that gap is exactly the kind of thing a careful user should resolve for themselves by reading the relevant source files before relying on the software, rather than assuming either the best or the worst from the module names alone.

The installer's own contents claim to be more conservative than the repository as a whole, stating explicitly that it does not include the LX Music program itself, any built-in music sources, platform account login capability, or any copyrighted songs, lyrics, covers or wallpapers.

Build and install steps that leave a signed trail

Development and packaging are ordinary Node tooling:

npm install
npm start

Producing the Windows installer is a single command that the README describes as also downloading and verifying pinned versions of FFmpeg and RePKG, then running a release validation step, before producing the installer alongside its block map, an update manifest and a published SHA-256 checksum file:

npm run build:win

Publishing a checksum alongside the installer, rather than only the installer itself, is a genuinely useful practice for exactly this category of software: an unofficial derivative of a popular tool, distributed as a Windows executable, is precisely the kind of artefact someone might try to imitate with a modified copy carrying something unwanted bundled in. A user who bothers to verify the published hash against their download has a real, independent check rather than only trusting that the release page itself was not tampered with.

The installer is also described as closing any running instance before overwriting its files during an upgrade, and as preserving playlists, settings and user data in the application's data folder across that process, which is the ordinary and correct behaviour for an update that should not cost a user their library.

What to weigh before installing it

This is Windows-only for the packaged release, supporting Windows 10 and 11 on 64-bit systems, with a macOS build available only by building from source on a Mac. It reports 317 stars, 18 forks and 17 open issues, with the last push and its most recent release both landing on 2026-09-10 and 2026-09-11 respectively, so it is under active, recent development.

An optional support page exists for users who want to contribute toward continued maintenance, and the README is careful to state that support is entirely voluntary and does not open up features, grant exclusive resources or priority service, and does not constitute a paid service contract, which is the honest framing for a donation mechanism attached to free, GPL-licensed software.

Before installing, three steps in order. Decide whether you actually want the AI assistant feature, since using it means acquiring and entering your own API key for a provider you choose and sending your commands directly to them, which is a reasonable trade but one worth making deliberately rather than by default. If you plan to use the optional LX Music import or any bundled source scripts, read the repository's own usage restrictions and, if you have any doubt about a specific module's purpose, look at its source before relying on it. And if you are verifying the installer, use the published SHA-256 checksum against your download rather than trusting the file alone.

Editorial conclusion

This player fits a Windows user who wants a full-featured local music player, complete with lyrics staging, an equalizer, spatial audio and 3D visualization, and who is intrigued by controlling it through natural language without handing an API key to the maintainer, since that key is entered by the user and requests go directly to their chosen model provider. Its licence section is unusually direct about what it is not, naming the platforms it carries no official relationship with and stating explicit prohibitions on piracy and platform bypass, which is the correct posture for a category of software with a real history of controversy. Read those usage restrictions against the repository's own file tree before relying on any optional import or source-script feature, verify the published SHA-256 checksum against your installer download, and decide deliberately whether you want the AI assistant enabled, since using it means sending your commands directly to whichever provider you configure.

Frequently asked questions

Official sources

1. Issues
2. License: GPL-3.0
3. README
4. Releases
5. ww085213/Mineradio-LX-Music on GitHub