Creative · Community report
Build a music playlist from your listening history
Build a music playlist from your listening history. Build, and optionally keep updating, a playlist from your own listening history.
What you can get
What it is
Playlist
A playlist built from your own streaming history, optionally kept current with new tracks on a recurring basis.
It came back right when
- The playlist draws from tracks that are genuinely in your listening history.
- Credentials were entered through the Secure Store, not shared in a regular chat message.
- If you asked for daily updates, new tracks are actually being added over time.
- The playlist's style or theme matches what you intended, not a generic mix.
The checks are editorial, not from the source.
- Connect via Secure StoreStops for your approval
Enter streaming credentials through settings, not chat.
- Review listening history
Let the agent read your history on the connected account.
- Build and review the playlistStops for your approval
Check the actual tracklist before relying on it.
- Decide on updatesStops for your approval
One-time playlist, or ask for recurring updates with periodic check-ins.
Editorial, not from the source
Works when
- You use a streaming service with enough listening history for a playlist to be built from it.
- You're comfortable storing credentials in Muse's Secure Store to allow this access.
- You want either a one-time playlist or an ongoing, regularly refreshed one.
Does not work when
- You'd rather not connect account credentials at all, even through a secure-store mechanism.
- Your streaming service isn't SoundCloud, and you need confirmation it's supported the same way.
- You want full control over every track added; the daily-update version adds tracks on a recurring basis without describing a review step.
Build a music playlist from your history: review template
| Item | What it's based on | Status |
|---|---|---|
| [Connected account] | [Secure Store credentials] | [Confirmed secure] |
| [Initial playlist] | [Reviewed listening history] | [Checked against your taste] |
| [Recurring updates] | [Daily/weekly, if requested] | [Spot-checked periodically] |
The source case
On X, @JJEnglert reports giving their Muse agent, which they've named Carl, access to their SoundCloud account, having it review their listening history, and build a playlist from it. Here's how to do it securely yourself: They also describe asking the agent to keep the playlist updated with new tracks daily, and give a five-step walkthrough for connecting credentials through Muse's Secure Store rather than sharing them directly. This is one report, checked on 2026-10-09; it does not state how the playlist was judged to be good, or how daily updates are tracked over time.
A public report by someone outside this library. Not independently reproduced here.
From the source
Source excerpt
I gave my @Muse agent "Carl" access to my @SoundCloud account, and it reviewed my history and built this playlist for me.
Source excerpt
1) Go to settings 2) Go to Secure Store 3) Enter your Soundcloud credentials (really any credentials you want to save) 4) Then tell your agent to create a playlist you'd like. 5) Then tell your agent to update the playlist with new tracks daily.
Quoted from the original posts. Not written by this guide, and not a result produced here.
Suggested prompt
Bring A streaming service account with listening history (the report uses SoundCloud). Acts Reads your listening history from a connected streaming account. Creates and updates a playlist on that account. Source community report, checked 2026-10-09.
Written by this guide as a starting point, not quoted from the source. Your edits stay in this browser.
Other ways to ask
Editorial rewrites of the brief above, for a different emphasis. Copy them separately.
What you need
Editorial, not from the source
You supply
- A streaming service account with listening history (the report uses SoundCloud)
Connected
- Your streaming service account, connected via Muse's Secure Store
Approved by you
- Credentials stored in Secure Store rather than shared directly in chat
- Approval for the playlist to be created and, if wanted, updated on a recurring schedule
How to try it
Editorial, not from the source
- Go to Muse's settings and open the Secure Store to add your streaming service credentials, rather than sharing them in chat.
- Ask your agent to review your listening history on the connected account.
- Ask for a playlist built from that history, and review it before treating it as finished.
- If you want it to stay current, ask the agent to update the playlist with new tracks on a recurring basis (the report says daily).
Credentials go through the Secure Store, not the chat
The report is specific about this: the author's walkthrough has you go to settings, then a Secure Store, to enter your streaming service credentials, explicitly framing this as the secure way to do it, as opposed to typing credentials directly into a regular message. This is a reasonable habit to carry over to any task that needs account access, not just this one. If a workflow asks you to type a password or token directly into chat instead of through a dedicated storage mechanism, that's worth treating as a sign to check whether the service actually has a Secure Store equivalent before proceeding, and to hold off until you've confirmed one exists.
A one-time playlist and a daily-updating one are different asks
The report describes two distinct steps: first asking the agent to build a playlist from your existing history, then separately asking it to keep updating that playlist with new tracks daily. These aren't the same task. A one-time playlist is a single, reviewable result; a daily-updating one runs on its own afterward, adding tracks without you necessarily checking each addition. If you only want a snapshot of your current taste, stop after the first ask. If you want something that evolves, be clear that's what you're asking for, and plan to check in on it periodically rather than assuming it stays well-curated without any oversight.
"A personal DJ" is an impression, not a measurement
The author's closing line, calling the result a personal DJ, is a genuine expression of satisfaction, but it's one person's reaction to one playlist built from their own specific listening history. It doesn't tell you how the agent weighted recency versus frequency of listens, how it handled genres you listen to rarely versus often, or what happens if your taste is unusually varied. Build your own playlist and listen through it critically before deciding it matches the enthusiasm in the report; a mismatch is easy to fix with feedback, but only if you actually review the tracks rather than taking the result on faith, which is the same habit worth keeping for anything an agent hands back unprompted.
Open Muse to try it. That is the product's own site; this guide is not part of it.
Limits and confirmation points
Limits to confirm
- One report; it doesn't say how long the history review covered, or how the agent decided which tracks to include.
- No detail on how good the playlist turned out, beyond the author's own enthusiasm.
- Ongoing daily updates aren't described in terms of how new tracks are chosen or how often the playlist is checked afterward.
- The report names SoundCloud specifically; it doesn't say whether other streaming services work the same way.
Stop and check
Editorial, not from the source
- Before connecting: use the Secure Store rather than sharing credentials directly in chat.
- After the first playlist is built: review the actual tracks before relying on it.
- If daily updates are turned on: check in periodically rather than assuming it stays well-curated indefinitely.
If it goes wrong
Editorial, not from the source
- You're unsure how to connect your account safely
- Use Muse's Secure Store (settings, then Secure Store) to enter credentials, rather than typing them into a regular chat message, as the report describes.
- The playlist doesn't reflect your actual taste
- Review the specific tracks included and give feedback; the report doesn't describe how closely the agent's selection matched the author's expectations beyond their own enthusiasm.
- You're not sure the daily updates are actually happening
- Check the playlist periodically yourself; the report doesn't describe any confirmation step for ongoing daily updates.
Common questions
Is it safe to connect my streaming account?
The reported method uses Muse's Secure Store to hold credentials, rather than sharing them directly in chat. Use that same route rather than typing credentials into a regular message.
Does this work with any streaming service?
The report specifically describes SoundCloud. It doesn't confirm whether other services connect and behave the same way.
Will the playlist update itself over time?
Only if you ask for that separately. The report describes requesting daily updates as a distinct step after the initial playlist was built.
How does it decide which songs to include?
The report doesn't say. It states that listening history was reviewed and a playlist was built from it, without describing the selection method.
What if I don't like the playlist it builds?
Review the actual tracks and give specific feedback. The report doesn't describe a feedback or refinement step, so you may need to ask explicitly for changes.
Next
Related to this task
More in Creative
Similar tasks
Get recurring task recommendations — ask your own agent to check for relevant updates.