Day 1 Experience - Music Producer
The Scenario
You make music in Ableton. Your sessions are a mess of bounced stems, sample packs, and half-finished ideas spread across three drives. You want your AI to help you get organized - and you don't want to explain your setup every time you open a new chat.
What Happens
fai is running. You open your AI tool in your music folder.
You:
"I want to sort out my project folders. I use Ableton, I bounce stems at
24-bit/48k, and I keep samples by pack name. Every track should have a
folder per version."
Your AI:
"Here's a structure that fits that:
Tracks/<Track>/<v01, v02, ...>/{Project, Stems, Bounces}
Samples/<Pack>/...
I can write a script that renames your existing stems to
<Track>_<Stem>_<BPM>_<Key>.wav and moves them into place. Want to try it
on one track first?"
You:
"Yes, start with 'Night Drive'. And never touch the Samples folder."
Your AI:
"Done for Night Drive: 14 stems renamed and moved into v03/Stems.
I left Samples alone."
What Just Happened
- You directed: how you work, what matters, what's off limits
- Your AI did the work: the folder plan, the script, the renaming
- fai was listening: it captured the conversation as it happened
The AI's skill came from the model you use. What fai adds is memory.
Why This Matters
This isn't a developer example. The same loop works for anyone who works with an AI tool:
- Musicians organizing sessions and sample libraries
- Writers keeping a story bible straight
- Designers tracking brand decisions
- Engineers designing systems
- Entrepreneurs running a business
Build anything. The domain doesn't matter. The pattern is the same: you direct, AI executes, fai makes sure the next session starts where this one ended.
See What fai Captured
After the session, open a second terminal:
$ fai --preview
🔍 fai MCP Preview
────────────────────────────────────
Preview: http://localhost:6274/?transport=streamable-http&serverUrl=http://localhost:4967/mcp
The inspector opens in your browser. From that one conversation, fai has noted:
- Decisions: folder per version; stems named
<Track>_<Stem>_<BPM>_<Key> - Patterns: try new scripts on one track first
- Context: Ableton, 24-bit/48k bounces, samples organized by pack
- Rules you set: never touch the Samples folder
fai doesn't hear your music. It remembers what you and your AI worked out.
Session 2: It Remembered
Next day, you run fai, continue your session, and open your AI tool:
You:
"Let's do the same for 'Low Tide'."
Your AI:
"Same as Night Drive: new version folder, stems renamed to
<Track>_<Stem>_<BPM>_<Key>, Samples untouched. Running it on Low Tide now."
No re-explaining your setup. It knew your DAW, your naming, and the one folder not to touch. That's compounding.