Why I Store Automation Logic in Claude’s Memory
I wanted to share something I got working that might inspire others.
I listen to Kyau & Albert’s monthly Euphonic Sessions podcast. The goal was simple: just say “play Kyau & Albert from November” and have it start playing on my kitchen speaker.
Claude tried fetching the podcast’s RSS feed but hit a robots.txt error. So I grabbed the XML myself from my browser and pasted it to Claude. Looking at the feed, we noticed the MP3 URLs follow a predictable pattern:
http://www.kyauandalbert.com/ES/EuphonicSessions-Kyau&Albert-November2025.mp3
Claude stored this URL pattern in its memory, along with my preferred volume setting (8% for the kitchen speaker).
I already had a Homey flow set up through AI Chat Control that accepts a stream URL and plays it on my Chromecast speaker. That’s all the infrastructure needed.
Now in any chat - even new ones - I can just say “play Kyau & Albert from October” and Claude:
- Builds the correct URL from the pattern it remembers
- Calls my Homey flow via AI Chat Control
- Sets the volume to my preference
No searching for links, no podcast apps. Just works.
The interesting bit:
The “flow” isn’t really in Homey - it’s in Claude’s memory. My Homey flow is dead simple: take a URL and play it. That’s it. All the logic (URL pattern, volume preference, month/year mapping) lives in Claude’s memory.
I could’ve built a complex Homey flow with all that logic hardcoded. But this approach is faster to set up and way more flexible. Want to add another podcast? Just tell Claude the URL pattern once. Want to change your volume preference? Update it in one sentence.
The AI remembers the patterns, the simple flow just executes. Works for any podcast or radio stream where you can spot the URL structure.
Curious what you’re building with AI Chat Control. Anyone else storing logic in Claude’s memory instead of building complex(er) flows in Homey?
