Claude Cowork + Obsidian: The Under 1-Minute Setup (and What It Unlocks)

Forget what older tutorials told you. Cowork connecting to Obsidian is not a plugin, an MCP server, or an API integration. Both apps just read and write the same folder of plain markdown files. That's the whole trick, and it's why nothing here breaks when either app updates.

Prerequisites:

• A paid Claude plan — Pro, Max, Team, or Enterprise. Cowork does not exist on the free tier. Source: Anthropic Cowork getting started.
• The Claude desktop app on macOS 11+ or Windows 10 (1903+) / Windows 11. There is no browser-based Cowork interface and no Linux build as of April 2026.
• Obsidian, free, from obsidian.md. No account required.

Things you do not need, despite what older tutorials say:

• No MCP filesystem server install. The filesystem connector is built into Cowork.
• No claude_desktop_config.json editing. That was the pre-GA pattern.
• No Obsidian community plugin. The integration is folder-level, not Obsidian-aware.

This is the literal sequence, derived from Anthropic's official Cowork onboarding flow. Source: Anthropic — Get started with Claude Cowork. The whole thing takes about 45 seconds on a warm machine.

1. Open Obsidian. On the welcome screen, click Create new vault (or Open folder as vault if you already have a notes folder you want to mount). Pick a clear path — ~/Documents/Brain or C:\Users\you\Documents\Brain.
2. Open Claude desktop. Sign in with your paid account.
3. Switch to Cowork. The desktop app shows a mode selector with Chat and Cowork tabs at the top of the window. Click Cowork (Anthropic's documentation describes this as Tasks mode).
4. Mount the vault folder. Inside Cowork, click the folder icon and select the same directory you just pointed Obsidian at. On macOS the system permission dialog appears; on Windows it is in-app. Anthropic states explicitly: "Claude can only read and write files in folders you've connected."
5. Click Always Allow. Choosing "Allow Once" forces re-authorisation every session and is the single biggest source of "why does Claude not see my notes anymore" complaints.
6. Verify. Type into Cowork: "List the files at the root of this folder." If it returns your vault contents, you are connected.

That is it. Steps 1–6 are reproducible in under sixty seconds once you have done it once. Supplementary walkthrough with screenshots: Marketing Agent — Connect Obsidian to Claude Cowork.

A connected vault is not the same as a working vault. Run two checks before you trust it:

Cowork → Obsidian: Ask Cowork to "create a file called test.md with the content 'connection works'." Switch to Obsidian. The file should appear in the file tree within a second or two. If it does not, the most likely cause is that Obsidian and Cowork are looking at slightly different paths — for example one points at ~/Documents/Brain and the other at a symlink that resolves elsewhere. Obsidian → Cowork: Create a file in Obsidian called today.md with a single line of text. Ask Cowork to "read today.md and tell me what it says." The reverse direction confirms the read path is wired and that file system permissions stuck.

Once both directions work, delete test.md. You are ready for the next module.

---

A connected vault gives Cowork raw filesystem access: read, write, list. What it does not give Cowork is any sense of how you organise that vault. A request like "save this idea to my second brain" with no map is a coin flip: Cowork might create idea.md in the vault root, or in Untitled Folder/, or in a directory that looks plausible but is not where you actually keep ideas.

A CLAUDE.md file at the vault root solves this. Anthropic's own Cowork onboarding documents this capability as folder instructions — per-folder context files that Cowork reads automatically and applies as standing directives whenever the folder is connected. (Anthropic also exposes a separate Settings → Cowork → global instructions surface for workspace-wide behaviour.) The convention of naming the file CLAUDE.md matches Anthropic's broader Claude Code pattern and is the de facto community standard for Cowork vaults. Think of it as the table of contents you would hand to a new research assistant on their first day.

Sources: Anthropic — Get started with Claude Cowork (folder instructions and global instructions). Supplementary community walkthrough: aclas.io — Claude + Obsidian Second Brain Guide.

Drop this at the vault root as CLAUDE.md. Edit the folder list to match yours. The structure mirrors what active Cowork users have settled on after several months of iteration:

# Vault Routing Map

## Folders and what goes in them

- `daily/` — One file per day, named YYYY-MM-DD.md. Logs, scratch thoughts, ad-hoc notes.
- `projects/` — One file per active project. Status, next actions, relevant links.
- `meetings/` — Meeting notes, named YYYY-MM-DD-attendees.md.
- `references/` — Long-lived reference material — frameworks, playbooks, learning notes.
- `inbox/` — Unsorted captures. Process and move out within a week.
- `archive/` — Anything no longer active but worth keeping searchable.

## Routing rules

- "Remember this" or "save this" with no destination → `inbox/` with today's date as a prefix.
- Daily-log entries → append to `daily/YYYY-MM-DD.md`, create the file if missing.
- Anything mentioning a project name → match to a file in `projects/` if one exists.
- Meeting summaries → `meetings/` with the meeting date and primary attendee.
- Never write to `archive/` unless I explicitly say "archive this".

## Behaviour

- Use ATX-style markdown headings (#, ##, ###).
- Add a YAML frontmatter block with `created:` and `tags:` to any new file.
- Wikilinks with [[double brackets]] are how Obsidian connects notes — preserve them on edits.
- Never delete a file. To "remove" something, move it to `archive/` and note the reason at the top.

Once this file exists, Cowork instructions become drastically more reliable. "Save the gist of this conversation" lands in inbox/. "Update the Project Atlas notes with the new milestone" finds projects/atlas.md and edits it in place.

The single workflow that pays for the setup time, and then some:

"Read every file in daily/ from the last seven days. Pull out anything tagged #decision or #followup. Summarise the decisions, and create a new note in meetings/ called weekly-review-YYYY-MM-DD.md with the summary, then add a ## Open follow-ups section listing every #followup with which file it came from."

This is one prompt. It would take a human ten to fifteen minutes of skimming and copy-pasting. Cowork executes it in under a minute and produces a markdown file that integrates back into the vault you already use. Repeat this every Friday and the vault becomes self-summarising.

The reason it works: Cowork is reading text files, not interpreting an opaque database. There is no schema to learn, no API surface that can break, no version that can drift out of compatibility.

---

Tasks Cowork handles cleanly because they are mostly text manipulation across many files:

• Bulk reorganisation — "move every file in the vault root that mentions 'Project Mercury' into projects/mercury/".
• YAML frontmatter backfill — "add a tags: line to every file in references/ that does not have one, inferring tags from the file content".
• Cross-file synthesis — "compile every meeting note that mentions 'pricing' into one summary".
• Recurring weekly summaries from the daily log.
• Tagging and re-tagging at scale.

The common pattern: read many files, transform text, write many files. This is exactly the kind of "peripheral knowledge work" Anthropic has positioned Cowork for. Source: our own Claude Cowork Enterprise GA guide.

Three failure modes worth knowing in advance:

Wikilinks and graph view are invisible to it. Cowork sees [[Project Atlas]] as the literal characters [ [ P r o j e c t A t l a s ] ]. It does not understand that this is a typed reference to projects/atlas.md. If you ask it to "follow the wikilink and update the linked note", it might find the file by name, but only by string-matching, not by resolving the link. The graph view, backlinks panel, and Dataview queries are entirely outside its model. Source: haihai.ai — Obsidian + MCP + Claude. Frontmatter is treated as text, not schema. Cowork can read and write the --- block at the top of a note, but it has no awareness that tags: should be a YAML list rather than a comma-separated string. If you have Dataview queries that depend on rigorous frontmatter, audit Cowork's edits before you trust them. Token cost is higher than you would guess. Cowork's execution model includes screenshotting parts of its own UI when it browses or interacts with web content. For pure file work this is fine, but the moment a task drifts into "look up this on the web and add it to the note", token consumption rises sharply compared with text-only Claude Code calls. Heavy vault automation is a Max plan workload, not a Pro plan one. Source: Naturally Stupid — Cowork organising an Obsidian vault.

Most people keep their vault in OneDrive, iCloud, or Dropbox. Cross-machine sync is the whole reason cloud drives exist. That convenience is also where Cowork trips: during a heavy edit session, Cowork and the sync client fight over file locks.

The symptom: files briefly appear duplicated as note 1.md and note 2.md, or Obsidian shows a "merge conflict" banner. The cause: Cowork writes to a file, the sync client picks up the change and uploads, Cowork writes again before the upload finishes, and the cloud service decides those are competing edits.

The fix is mechanical: pause cloud sync for the duration of any large Cowork operation. On OneDrive that is one click in the system tray menu. Resume sync when Cowork reports the task complete. For day-to-day single-file edits this is not a problem; for vault-wide reorganisations it is essential.

---

Running Cowork against an Obsidian vault is bundled into a Claude subscription, not metered separately:

| Plan | Monthly | Cowork access | Realistic vault use |

|---|---|---|---|

| Pro | ~$20 | ✅ Included | Light — daily summaries, ad-hoc edits, one or two batch jobs per week |

| Max | $100–$200 | ✅ Higher usage limits | Heavy — vault-wide reorganisations, automated weekly digests, frontmatter backfills |

| Team | $20–$25/seat | ✅ | Per-user vaults, no shared vault model out of the box |

| Enterprise | Custom + API rates | ✅ Plus admin controls | Required if you need SSO, audit, or a centrally-managed deployment |

Source: Anthropic plans.

The honest read: if you are a single user with one vault and you run a couple of summary jobs a week, Pro is enough. If you start running daily automated tasks across a five-thousand-file vault, you will hit Pro limits within a week and Max is the realistic floor.

Cowork is the right tool when the work is text-in / text-out across many files in a folder you control. It is the wrong tool when:

• The work involves running tests, building code, or executing scripts → use Claude Code, which is purpose-built for that. Source: our Claude Code vs OpenCode/Cline/Aider comparison.
• You need versioned, reviewable diffs before changes hit the vault → Cowork edits in place; pair with git or use Claude Code with a worktree if the audit trail matters.
• The vault has any HIPAA, FedRAMP, or FSI workload in it → Cowork is explicitly not approved for those today. Audit Logs and the Compliance API do not yet cover Cowork at GA.

The setup is genuinely one minute. The decision of whether to use Cowork against a particular vault is not. A useful rule of thumb:

If you would let a junior research assistant read every file in this vault, Cowork is a reasonable fit. If you would not, do not connect it.

Cowork has filesystem access, no row-level security, no per-folder ACLs inside the vault. Permission is binary: a connected folder is fully readable and writable. Treat the folder selection in step 4 of the setup as the most important decision in this guide.

---

| Symptom | Cause | Fix |

|---|---|---|

| Cowork "cannot find" a file you can see in Obsidian | The Obsidian vault path resolves through a symlink that the OS permission dialog did not include | Re-mount using the canonical absolute path; do not use ~ or shortcuts |

| Cowork creates files in the wrong folder | No CLAUDE.md at the vault root, or the routing rules do not cover the case | Add a CLAUDE.md (Module 2 Lesson 2 has a working template) and restart Cowork |

| Files mysteriously duplicated as note 1.md | Cloud sync conflict during a large Cowork run | Pause OneDrive/iCloud, re-run, resume sync |

| Permission dialog re-appears every session | "Allow Once" was clicked instead of "Always Allow" | Re-mount the folder and pick Always Allow |

A free check: ask Cowork to "count the markdown files in the vault root and report the number, but do not read their contents". The response confirms permissions and folder mapping in roughly two thousand tokens, instead of the fifty-thousand-plus a content-scan would consume.

Run this check after any system update, after re-mounting the vault, or whenever Cowork seems to misbehave. Cheap, fast, definitive.

If the basic setup works and the CLAUDE.md routing is reliable, the natural next step is a small set of saved Cowork prompts you re-run on a schedule. Three that pay back the setup time:

1. Weekly review. Every Friday: summarise daily/ from the past week and write a meetings/weekly-review-YYYY-MM-DD.md.
2. Inbox processor. Every morning: read every file in inbox/, suggest a destination folder for each, and ask for confirmation before moving.
3. Stale-project sweep. Monthly: list every file in projects/ whose updated: frontmatter is older than 30 days and propose archive moves.

Each of these is one prompt, runs in under a minute, and produces concrete output. Together they turn a vault from a static archive into a system that actually maintains itself.

---

Additional Resources

• Anthropic — Get started with Claude Cowork
• Anthropic — Cowork product page
• Obsidian download
• Marketing Agent — Tutorial: Connect Obsidian to Claude Cowork
• aclas.io — Claude + Obsidian Second Brain Guide
• haihai.ai — Writing 2,000 words with Obsidian + MCP + Claude
• Naturally Stupid — Letting Claude Cowork organise an Obsidian vault
• vybecoding.ai — Claude Cowork Enterprise GA