Guest briefs, transcripts, and fact-check notes
Muse · experimental illustrative use case
Aisha tests a durable research desk for her podcast
Aisha produces an interview podcast and is testing Muse as a research assistant.
Muse helps Aisha shape interview questions and connect research across documents. She uses DiskDrive as the owned archive for the source material and the editorial decisions she explicitly wants another session—or another AI—to retrieve.
The connection
How Aisha connects Muse
DiskDrive uses a browser authorization flow. The person signs in directly to DiskDrive, reviews permissions, and never gives the AI a DiskDrive password or pasted access token.
- 1
Aisha copies DiskDrive’s Muse setup message and pastes it into Muse so Muse can prepare a private connector.
- 2
When Muse presents the secure Connect card, she chooses Connect once, signs in to DiskDrive in the browser, and reviews the requested permissions.
- 3
She asks Muse to check the connection before working. If Muse later returns a 401 error, she reconnects once and does not enter a token or repeat the process in a loop.
The everyday benefit
What goes into DiskDrive
The AI helps with the conversation. DiskDrive holds the finished files and explicit Memories that should still exist afterward.
Editorial decisions and explicit guest preferences
Reusable research connected to its original sources
Later, when it matters
Aisha’s research can remain useful across episodes and, later, across a different authorized assistant. For now, she treats Muse as a short-session experiment and confirms important saves in DiskDrive rather than assuming a long Muse session will remain connected.
More examples
See how people could use DiskDrive with another AI
Your archive. Your permissions.