Use Daisy as a local meeting memory inside Obsidian

Daisy can write every new recording into an Obsidian vault as plain Markdown. Obsidian indexes the notes; Daisy keeps the audio, transcript, summary and MCP access tied to the same local session. No export job or integration account is required.

Connect the vault

In Obsidian, open the vault you want Daisy to use. If meeting notes need a different privacy or sync policy from your main vault, create a separate vault first.
In Daisy, open Settings → General. Under Storage, find Recordings folderand click Choose folder….
Select the root of the Obsidian vault. Daisy creates its ownDaisy/Sessionssubfolder; it does not scatter files across the rest of the vault.
Finish a short test recording. Open Obsidian and confirm that the new session appears under Daisy → Sessions.

Existing recordings are not moved. Changing the folder affects new sessions only. Daisy continues to read older sessions from their original location.

What lands in the vault

Each recording gets a timestamped directory. Its main note is alwaystranscript.md:

Your vault/
└── Daisy/
    └── Sessions/
        └── 2026-08-18T09-30-00/
            ├── transcript.md
            ├── microphone.caf
            ├── system_audio.caf
            └── …optional screenshots and sidecars

The Markdown note contains YAML properties followed by the meeting title, recording time, summary, action items, follow-up draft and transcript when those sections are available. Daisy writes properties such assource: Daisy,started,duration_sec,daisy_folder and the tagsmeeting,transcript anddaisy.

Find meetings without a plugin

Obsidian indexes the Markdown body and its properties automatically. Use the daisy tag to collect every Daisy session, search for a client or decision across transcript text, or filter notes by the started and daisy_folder properties. The on-disk note remains readable in any editor even if you stop using either app.

Daisy’s own Library and local MCP server continue to read the same session. That means an AI client can search the meeting through MCP while you browse and link the Markdown in Obsidian. See the MCP setup guide for Claude, Cursor and other clients.

Optional: build a Dataview meeting index

If your vault already uses the community Dataview plugin, this query makes a simple newest-first meeting table. Dataview is not required by Daisy.

```dataview
TABLE started AS "Recorded", duration_sec AS "Seconds", daisy_folder AS "Daisy folder"
FROM #daisy
WHERE source = "Daisy"
SORT started DESC
```

The privacy boundary changes if the vault syncs

Daisy itself does not upload the vault. But if the selected folder is covered by Obsidian Sync, iCloud Drive, Dropbox, a backup agent or another sync service, that service may upload the files Daisy places there. Those files can include full transcripts, summaries, audio and screenshots.

Review the vault’s sync and exclusion settings before connecting it, especially for client calls or regulated work. A separate unsynced vault is the simplest boundary when meetings must remain only on the Mac. Read the full privacy explanation and security model.

Keep the Daisy folder Daisy-managed

You can edit and link the Markdown in Obsidian, but avoid moving or renaming the timestamped session directories while Daisy still needs to show them in its Library or expose them through MCP. If you want a curated note elsewhere in the vault, link to the session or copy the parts you need instead of restructuring the underlying session folder.