nuclear vs pear-desktop

Desktop music players with different streaming approaches

nuclear is a cross-platform player that searches for music and streams it from available sources, while pear-desktop provides a desktop interface for YouTube Music. Both support plugins and appearance customization, but nuclear centers on music discovery and playback controls, whereas pear-desktop extends the YouTube Music experience.

nuclearpear-desktop
LanguageTypeScriptTypeScript
LicenseAGPL-3.0MIT
Stars18.6k33.8k
Forks1.3k2k
Last analyzedOct 11, 2026Oct 17, 2026

Key differences

  • nuclear searches for artists, albums, and tracks across available sources; pear-desktop is built around YouTube Music.
  • nuclear includes playlists, favorites, listening history, and queue controls; pear-desktop focuses on wrapping the YouTube Music service in a dedicated desktop window.
  • nuclear offers an MCP server for control by compatible AI clients; pear-desktop plugins can use Electron hooks, menus, configuration, and IPC.
  • nuclear is licensed under AGPL-3.0, while pear-desktop is licensed under MIT.
  • nuclear uses Tauri, while pear-desktop is Electron-based.
  • pear-desktop has more reported stars and forks in the provided data: 33.6k stars and 2k forks, compared with nuclear's 18.6k stars and 1.3k forks.

Choose nuclear if you…

  • need music search and playback features such as playlists, favorites, and queue controls.
  • want to stream from available sources and extend the app through its plugin system.
  • want compatible AI clients to control your player through an MCP server.
Read the nuclear analysis →

Choose pear-desktop if you…

  • want to use YouTube Music in a dedicated desktop app instead of a browser tab.
  • prefer CSS themes and plugins with Electron-specific hooks and IPC.
  • want an MIT-licensed project with installation options through platform package managers or GitHub releases.
Read the pear-desktop analysis →

Compare the numbers side by side, or add more projects

This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.