Community recipe · Tool workflows
Convert listening history into a portable playlist
Source-backed example. Practical decision guidance is proposed and untested; this is not a full implementation guide.
The problem
Listening history and track lists are less useful when they cannot be carried into the service where someone wants to listen.
Agent job
Match ListenBrainz history or a supplied track list to Tidal, supporting a dry run and playlist-transfer export.
Expected output
Playlist matches, a transfer export or a destination playlist.
Where this framing comes from
- Core problem: Editorial purpose framing
- Agent job: Editorial purpose framing
- Expected output: Editorial purpose framing
- Relevant job roles: Editorial purpose framing
- Benefit type: Editorial purpose framing
Editorial framing and outcome limits
Describes the task’s purpose and intended output; measured benefit, safe unsupervised operation and successful delivery are not established by this framing.
Editorial synthesis based on the linked source. This framing does not add evidence of successful delivery or results.
Case-specific decision guidance · untested
Case-specific decision guidance and first checks are original proposals. The linked source supports the attributed task; this added guidance has not been executed.
Read the attributed source evidence and original caveats below ↓
Why use this
A listener may have a useful history or track list that does not directly transfer to their preferred music service. Similar titles, alternate recordings and unavailable releases can make automatic matching produce a playlist that feels unexpectedly different.
This job could prepare a reviewable match list and portable export before touching a destination account. Showing version choices and unresolved tracks lets the listener decide which substitutions are acceptable.
Why an agent / simpler alternative
- Useful judgment
Compare title, artist and release/version evidence, distinguishing exact matches from plausible alternatives.
- Simpler alternative
Use a trusted transfer service or manual search when the playlist is short and unambiguous.
- Unsuitable when
The task needs unauthorized account access or silently substitutes recordings that matter to the listener.
Proposed inputs
- Name
Listening history or list
- Owner
Listener
- Minimum scope
Selected tracks with artist and available release metadata
- Quality check
Normalize duplicates while preserving intentional repeats
- Name
Matching preferences
- Owner
Listener
- Minimum scope
Rules for live, remastered, explicit and alternate versions
- Quality check
Specify acceptable substitutions rather than infer them
Access and setup — proposed or unknown
- Proposed minimum
Use a supplied list and fictional destination catalogue first; no music-service login, API token or playlist creation.
- Compatibility unknowns
Current catalogue availability, regional restrictions, API support and runtime compatibility are unknown.
- External actions requiring approval
Account connections, history disclosure, destination playlist writes and sharing exports require authorization.
Expected deliverable and review checks
- Proposed artifact
Dry-run track mapping with exact/uncertain/unavailable status and proposed transfer export fields.
- Critical checks
Check artist and version, not title alone; preserve order; keep unavailable tracks visible; avoid presenting candidates as created playlists.
- Missing output evidence
This overlay adds no new output inspection, execution or validation; consult the referenced canonical source outcome limits.
Failure signals and proposed responses
- Signal
A live recording replaces the studio track
- Why it matters
The match changes the intended listening experience
- Proposed response
Flag the version difference and request a substitution choice.
- Signal
Regional availability is assumed from a search result
- Why it matters
The destination may not play the selected recording
- Proposed response
Leave availability unverified until an authorized account check.
Effort and cost — unknown
- Setup work
Define matching tolerances and list-order rules.
- Ongoing review
Review uncertain matches and catalogue changes.
- Unknowns
Regional access, transfer limits, subscription needs and service costs are unknown.
First check — proposed, unexecuted
- Status
proposed_unexecuted
- Synthetic fixture
Invent five tracks with two same-title recordings, a remaster and one unavailable release; propose a match table.
- Acceptance checks
Identify version ambiguity; preserve unresolved entries; retain order; create no playlist.
- Stop conditions
Stop when a match requires guessing or credentials/account changes are requested.
Limits
A catalogue match does not guarantee playback availability, ownership rights or equivalence between recordings.
Editorial candidate. This is source-backed reporting or a documented workflow. BotCurrent has not independently tested this task. A proposed Canadian adaptation is not evidence of a Canadian deployment or compliance certification.
Original source
https://github.com/RegeneratusLabs/hermes-tidal-playlist-creator ↗Attributed to: RegeneratusLabs
Community recipe- Original action type
- tool_action
- What the source supports
- Documents importing ListenBrainz history or a specified track list into Tidal, with dry-run support and export for playlist-transfer services.
- Source outcome limits
- This community recipe describes a procedure; it does not prove successful execution or independently reproduced results.
- Evidence attribution caveat
- This community recipe describes a procedure; it does not prove successful execution or independently reproduced results.
- Source approval description
- Not specified
- Named tools
- Hermes Agent, ListenBrainz, Tidal, tidalapi, Python
- Model or version
- Unknown
- Publication date
- Unknown
- Source last checked
- 2026-10-14
- Demonstrated in Canada
- Unknown
- Canadian availability
- Unknown
- Proposed Canadian adaptation
- Proposed only: check Canadian catalogue matches, music service availability and export privacy; retain a local copy of unmatched tracks.
- Recommended approval boundaries
- Review dry-run matches and authorize destination playlist changes or transmission to transfer services.