mirror of
https://github.com/aome510/spotify-player.git
synced 2026-04-26 01:15:55 +03:00
[GH-ISSUE #887] Open spotify player by URI / URL #1470
Labels
No labels
bug
documentation
enhancement
good first issue
help wanted
pull-request
question
third-party
third-party
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/spotify-player#1470
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @sand4rt on GitHub (Dec 17, 2025).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/887
Is your feature already implemented in the latest
master?Please go through the Features README page to make sure your request feature hasn't been implemented.
no
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
It would be nice if i could open a Spotify track directly in a new or existing Spotify player instance when clicking a
spotify:URI (e.g.,spotify:track:6rqhFgbbKwnb9MLmUQDhG6) or a link (e.g.,http://open.spotify.com/track/6rqhFgbbKwnb9MLmUQDhG6).Describe the solution you'd like
A clear and concise description of what you want to happen.
Not sure about the solution but, maybe with a new command like
spotify_player open {URI/URL}that opens the track in spotify player? This could allow users to configure a.desktopentry with:Maybe this functionality could be built directly into the Spotify client, so URI and URL's open automatically in a exsisting or new spotify player instance?
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
None
Additional context
Add any other context or screenshots about the feature request here.
https://developer.spotify.com/documentation/web-api/concepts/spotify-uris-ids
@RossSmyth commented on GitHub (Dec 29, 2025):
Would be relatively easy to add, just need to add a
*.desktopfile that adds something similar toMimeType=x-scheme-handler/spotify;@greqor commented on GitHub (Feb 12, 2026):
I have implemented this feature and opened a PR.
It adds a spotify_player open <URI_OR_URL> command that accepts both Spotify URIs and web URLs.
This also makes it simple to set up a .desktop handler for spotify: URIs:
Feedback welcome.
@sand4rt commented on GitHub (Feb 12, 2026):
Nice @greqor! Does it open the URL in an existing instance, or does it always launch a new one?
@greqor commented on GitHub (Feb 13, 2026):
It works the same way as the
playbackcommand. If an instance is already running, it uses that one. Otherwise it launches a temporary one to handle the request to Spotify's API and exits.@greqor commented on GitHub (Feb 13, 2026):
After thinking about it, since my current implementation is only controlling the playback, it might make sense to make it a subcommand of
playbackcommand.For example:
It never spawns a new instance of TUI interface, but only starts playing a track on connected device (it might be currently opened TUI interface or other spotify client as well, like spotify app on the phone).
To satisfy the original use case, we can add a new command
openwhich will spawn a new instance of TUI interface and start playing the track, or use existing TUI instance if it's already running. If there is another spotify client connected (like spotify app on the phone), it would stop playing it there and start new playback in TUI interface.Let me know please if that makes sense.
@sand4rt commented on GitHub (Feb 13, 2026):
Personally, i’d would only use the open command. I often want to preview a track someone sent me via a link before i start playing it.