If you've spent any time building a second brain in Obsidian — tuning your Dataview queries, wiring up Smart Connections, writing skills for Copilot, maybe plugging in a local LLM — you've probably noticed the same gap we have.

Your vault has everything except what happened in your meetings.

You can feed it your reading highlights, your journals, your project notes, your code snippets. But the richest source of daily context — the hour-long call where your co-founder just redefined the Q3 roadmap, or the customer interview where the real objection finally surfaced — lives in some other app's cloud, behind a "View transcript" link, in a format your vault cannot index.

This article is about closing that gap.

"Meeting notes were updated."

This is the notification you actually want.

Not "your recording is ready." Not "your summary is processing." Not a Slack DM with a link to a SaaS dashboard. Just: the file in your vault got written, your backlinks updated themselves, your Dataview inbox showed a new row, and your agent has fresh context the next time you ask it anything.

That's the end state. The question is how to get there.

How do I sync meeting context?

The honest short answer: you need an AI meeting assistant that writes real Markdown files into a folder of your choice, ideally without any manual step in the middle.

Most assistants don't do this. They hold your notes in their own web app and offer an "Export to Markdown" button you have to remember to click — or worse, a one-way Obsidian plugin that dumps a blob of text and breaks your folder conventions.

The workflow that actually keeps a second brain in sync looks like this:

1. Capture happens automatically. The meeting starts, the assistant starts. No "record" button. No joining the call as a bot. 2. The meeting ends. The assistant knows. It runs a post-meeting action — in Shadow's world, a "skill." 3. A Markdown file lands in your vault. Named how you want it named. Placed in the folder you picked. With frontmatter your Dataview queries already understand. 4. Your graph updates. Your agents update. Your brain updates. Because the vault is the source of truth.

Nothing in that list is exotic. It just requires the assistant to respect that your vault — not their dashboard — is where the notes belong.

Context for Obsidian: what Shadow actually does

Shadow is a Mac-only AI meeting assistant built for people whose notes, agents, and skills already live somewhere — usually Obsidian. Here's the relevant surface area:

Auto-detection at the system level

Most "automatic" note-takers are actually calendar-driven. They only know a meeting is starting if it was on your Google or Outlook calendar. That breaks for half of what a founder or operator actually does: ad-hoc Slack calls, Discord huddles, calendar-less Meet/Zoom links someone DM'd you five minutes ago.

Shadow detects the meeting at the system level — the audio streams tell it a call started, regardless of whether a calendar told it first. So the capture just happens, for every meeting.

This matters for Obsidian specifically because the second-brain promise falls apart the moment there's a gap. A vault that's comprehensive except for ad-hoc calls is a vault your agents will silently reason over with holes in it.

Markdown-first export, directly to your vault folder

Shadow lets you configure post-meeting skills that write Markdown to any folder you choose. The two that matter most for Obsidian users are typically:

  • An outline export — a structured summary with action items, decisions, and open questions.
  • A transcript export — the full transcript with speaker labels.
Both write .md files to a folder of your choice. Point them at ~/Obsidian/MyVault/Meetings/ and you're done. Configure the skill's template to include frontmatter, and your existing Dataview queries (TABLE date, attendees FROM "Meetings") just work.

Captures what's shown, not just what's said

Here's the differentiator that compounds in a second-brain context: Shadow takes screenshots of what's on screen during the call, so the visual half of the conversation doesn't get lost. When you later ask your agent "what did Alex show in Tuesday's review?", the context is actually there. Most assistants can tell you Alex talked; Shadow can also tell you what Alex showed.

Autopilot Mode

You can configure Shadow so every meeting automatically runs a set of skills after it ends: export the outline, export the transcript, fire a webhook to Zapier, draft a follow-up email. You don't open the app. You just see "Meeting notes were updated." in your file system, and your vault is fresh.

Bot-free

Shadow captures system audio from outside the meeting. It never joins as a visible participant. For anyone who has sat through a user interview where the customer paused mid-sentence to squint at "Otter.ai" in the attendee list — this is the feature you didn't know you were negotiating for.

A concrete Obsidian workflow

Here's how this plugs together end-to-end. This is roughly the setup many Shadow + Obsidian users converge on:

1. One Shadow skill per output type, all targeting MyVault/Meetings/.

  • An outline skill that writes {date}-{title}-outline.md
  • A transcript skill that writes {date}-{title}-transcript.md
2. A consistent frontmatter shape in the skill template so Dataview can aggregate. ``yaml --- date: 2026-04-22 type: meeting-outline attendees: [Jay, Alex, Customer] tags: [meeting, customer-interview] --- `

3. A Dataview "Meetings This Week" inbox note — an auto-generated rollup of the week's outlines, sorted by date, with action items linked back.

4. Your agent (Copilot, Smart Connections, or a local model) indexes the folder. Now when you ask "what did this customer say about pricing last month?" the answer comes from the actual transcript, not your fuzzy memory of it.

5. Weekly review just works. Because the vault is the source of truth, your weekly note template can pull FROM "Meetings"` and summarize itself.

The key insight is that none of these Obsidian-side pieces are new. People have been building exactly this kind of second brain for years. What was missing was a reliable, no-friction way to make meetings part of it. That's the gap Shadow closes.

Why this matters for agents and skills

If you're running anything agent-shaped on top of Obsidian — Copilot skills, Smart Connections queries, a local model pointed at your vault, a custom MCP server that reads your notes — the quality of the output is bounded by the quality of the input.

A vault without meeting context is like an engineer without access to Slack. Technically functional; missing half the signal.

Giving your second brain fresh, structured, searchable meeting context — automatically, as Markdown, without a bot in the call — is one of the highest-leverage things you can do for it. And it's a one-time setup.

Getting started

1. Install Shadow on your Mac. 2. Set the export destination on your outline and transcript skills to a folder inside your Obsidian vault. 3. Turn on Autopilot Mode. 4. Have a meeting. 5. Open your vault. Watch the file land.

That's the whole setup. From there, everything your second brain already does — graph, Dataview, agents, skills — just starts including meetings too.

The notification you wanted was "Meeting notes were updated." Now it's a file system event, not a SaaS email.

---

This article was written by Chad Oh, Shadow's AI writer. While we strive for accuracy, AI-generated content may contain errors. If you spot something off, let us know.