Amicore

Claude Cowork Folder Best Practices

Structuring the folders you mount — the layout, exclusions, and anti-patterns that keep Cowork fast and accurate on legal work

Last updated: April 24, 2026 Guide

Folder structure is the most under-discussed variable in Claude Cowork performance. When you point Cowork at a folder, it reads the contents before answering your first prompt — the bigger and messier the mount, the more tokens are burned and the more attention is wasted before work begins. In documented cases, mounting a folder too large or too unfocused triggers what users call a 'compaction death spiral' — system context alone consuming 86% of the token window, forcing repeated auto-compactions within minutes of session start [5]. This article is the physical-layer companion to the overview in our Claude Cowork Cheat Sheet [/research/claude-cowork-cheat-sheet] and closes the three-part deep-dive series alongside the CLAUDE.md guide [/research/claude-md-files-guide] and the MCP article [/research/claude-mcp-explained]. It covers how to lay out folders for legal work, what to exclude, and the current limitations Cowork still imposes as of April 2026.

Why Folder Structure Determines Cowork Quality

  • +Cowork reads before it works. Every session burns tokens on folder listing and selective content reads before you type a prompt. A well-organized mount gives Claude a cheap, accurate first view. A bloated mount gives Claude a noisy, slow first view.
  • +Context rot is real. More context available is not more context useful. Model attention degrades across long contexts in ways that are hard to predict [9]. The firm that gives Cowork a 50-matter archive folder doesn't get 'smarter' responses — it gets worse ones.
  • +Performance failures are documented. Anthropic's own GitHub tracker includes an issue titled 'Compaction death spiral in Cowork: 6 compactions in 3.5min due to system context consuming 86.5% of window' — not theoretical; reported by real users [5].
  • +The discipline matches legal intuition. A well-organized matter folder — the thing a well-trained paralegal would assemble for trial prep — is exactly what Cowork needs. The bad news: a dumping-ground folder is what Cowork gets from most users by default.

The Home-Directory Constraint (Still Active April 2026)

Before designing a folder structure, understand the constraint that governs where you can put it. As of April 24, 2026, Cowork rejects folders outside the user's home directory — `~/` on macOS and `C:\Users\<username>\` on Windows. This is a UI restriction imposed by the folder picker, not a security limit of the VM sandbox itself. It is tracked in multiple open GitHub issues [2][3][4][6]; Anthropic has not resolved it.

Symlinks do not work around it: The folder picker uses `fs.realpath()` to resolve symbolic links before validation. A symlink from `~/work` pointing at `/Volumes/FirmDrive/Matters` is rejected because the resolved path is outside home. NTFS junctions on Windows behave the same way [2].
External drives fail on Windows: Firm-issued laptops often store matter files on D: or E: drives. Those paths cannot be selected. Workaround: copy or sync the needed subset into `C:\Users\<username>\` before the Cowork session. For Mac users, `/Volumes/` paths are similarly rejected [3].
Network drives and mapped shares fail: If your firm keeps matters on a SMB share or a mapped network drive, Cowork cannot mount them directly. You'll need either a local sync copy inside home, or a DMS-to-Cowork bridge via MCP (see our MCP guide: /research/claude-mcp-explained).
The practitioner workaround: Most power users adopt a `~/Cowork/` top-level folder as their mount root, with subdirectories for different workstreams. This accepts the constraint rather than fighting it and produces clean, predictable mounts.

Cloud-Synced Folders — Read Before You Use Them

  • +Many firms are tempted to point Cowork at a Google Drive, OneDrive, or Dropbox folder synced into `~/`. This works inconsistently and has a documented failure mode worth flagging.
  • +macOS FileProvider (Google Drive, OneDrive): Cowork can LIST files in these paths but cannot reliably READ them. Tracked in GitHub issue #29914 [3]. If the file is cached locally, reads work. If the file is on-demand/not yet downloaded, reads fail silently — Cowork sees the filename but gets empty content.
  • +Microsoft OneDrive 'Files On-Demand': Explicitly problematic. The OS tries to stream content when Cowork opens it; the handoff fails. Turn off Files On-Demand for any folder Cowork will use, or right-click folders and choose 'Always keep on this device.'
  • +Google Drive 'Streaming': Same issue — the streaming abstraction breaks Cowork's file reads. Use 'Mirror files' mode (downloads the files) rather than streaming.
  • +Dropbox: Works reliably if the folder is marked 'Make available offline' so content exists in local cache. Online-only files will fail the same way FileProvider does.
  • +Bottom line: For any cloud-synced folder Cowork will touch, force it to full local sync. Half-downloaded cloud mirrors produce hard-to-diagnose failures.

The Recommended Legal Hierarchy

Most firms already organize matter content in some version of firm → practice → matter → sub-content. That hierarchy translates cleanly to Cowork. The pattern below is the default starting point; the firm-size templates below adapt it.

1

Firm root (inside home)

`~/FirmDrive/` or `~/Cowork/` — the top-level directory you mount. Contains nothing directly except subdirectories and a firm-wide CLAUDE.md. This is the 'anything I'd let Cowork see' boundary.

2

Practice-area layer

`~/FirmDrive/Litigation/`, `~/FirmDrive/Corporate/`, `~/FirmDrive/IP/`. One folder per practice with a practice-area CLAUDE.md at each root (see /research/claude-md-files-guide for template).

3

Matter layer

`~/FirmDrive/Litigation/Smith-v-Acme/`. One folder per active matter. Matter CLAUDE.md at the root. Subdirectories for pleadings, discovery, depositions, research, strategy, opposing.

4

Content subdirectories within a matter

Structured by function (pleadings/, discovery/, depositions/, research/, strategy/, opposing/, exhibits/) rather than by date or author. Function is what Cowork needs to find things; dates belong inside filenames.

5

Outputs folder (optional but recommended)

`~/FirmDrive/Outputs/` or inside each matter: `~/FirmDrive/Litigation/Smith-v-Acme/outputs/`. A dedicated landing area for Cowork-generated drafts, summaries, and work product — makes review workflows cleaner.

CLAUDE.md at each level customizes behavior for that scope — firm-wide rules at the root, practice-specific conventions at the practice level, matter-specific facts at the matter level. See our CLAUDE.md guide for concrete templates.

Template — Small Firm (1–20 attorneys)

Lightweight layout optimized for solo practitioners and small firms where one attorney may cross multiple practice areas

Small firms often don't have enough matter volume per practice to justify a practice-area layer. Collapse the hierarchy and put matters directly under the root.

Root layout: `~/Cowork/` as the top-level mount. Contains firm-wide `CLAUDE.md`, an `Active/` folder for open matters, an `Archive/` folder for closed matters (usually NOT mounted — see active-vs-archive section), and a `Reference/` folder for firm templates and style guides.
Active matter layout: `~/Cowork/Active/Smith-v-Acme/` with a matter `CLAUDE.md`, and subdirectories `pleadings/`, `discovery/`, `research/`, `strategy/`, `outputs/`. Skip folders you don't need — a transactional matter may need `drafts/`, `due-diligence/`, `closing-binder/` instead of litigation folders.
Reference folder contents: `~/Cowork/Reference/` holds firm-level templates, style guides, citation quick-references, and a jurisdiction-specific rules summary. Claude reads these once when mounted and uses them across all matters — saves repetition across matter CLAUDE.md files.
What to mount: Mount `~/Cowork/` as a whole, OR mount individual `Active/<matter>/` folders as you work. Mounting the whole `~/Cowork/` with 3–8 active matters generally works fine; mounting 30+ is where you start seeing slowdowns.
CLAUDE.md placement: Firm-wide at `~/Cowork/CLAUDE.md`. Matter-specific at `~/Cowork/Active/<matter>/CLAUDE.md`. Skip the practice-area layer — your firm is small enough that practice-specific rules can live in each matter file.

Template — Mid-Firm (20–100 attorneys)

Full three-tier hierarchy with centralized practice conventions

Mid-firms have enough matter volume per practice to justify practice-level rules and enough attorney specialization that practice conventions diverge meaningfully. Use the full firm → practice → matter hierarchy.

Root layout: `~/FirmDrive/` with `Litigation/`, `Corporate/`, `IP/`, `Employment/`, etc. Firm-wide `CLAUDE.md` at root. Each practice folder gets its own `CLAUDE.md` encoding practice-specific drafting conventions (see /research/claude-md-files-guide for a commercial-litigation example).
Active matter layout per practice: Consistent across practices: `pleadings/`, `drafts/`, `discovery/`, `research/`, `strategy/`, `opposing/`, `outputs/`. Use the same folder names regardless of practice — predictability helps both attorneys and Claude.
What to mount — per-attorney: Attorneys typically mount only the practice folder they're working in, not the full firm root. A litigator mounts `~/FirmDrive/Litigation/` and gets firm-wide + practice-level CLAUDE.md automatically via the walk-up-tree behavior, plus access to all active litigation matters.
Shared drive handling: Most mid-firms store matter content on a network share or DMS. Sync each attorney's active matters into their local `~/FirmDrive/` via iManage Desktop, NetDocuments Connect, or a nightly rsync. Do NOT mount the network share directly — it fails, per the home-directory constraint.
Alternative: skip the local mount, use MCP: At this firm size, standing up an MCP connector to iManage or NetDocuments may be cleaner than per-attorney local syncs. See our MCP guide: /research/claude-mcp-explained.

Template — Large Firm (100+ attorneys)

Centralized policy + attorney-specific active matter mounts, with MCP as the preferred DMS bridge

Large firms have the attorney count and matter volume where local folder sync becomes a nightmare to manage. At this scale, MCP is almost always the right DMS bridge, and local folder mounts should be reserved for attorney-personal content and scratch work.

Managed-policy CLAUDE.md: Deploy a firm-wide `CLAUDE.md` to the managed-policy location on every attorney's device via MDM — `/Library/Application Support/ClaudeCode/CLAUDE.md` (macOS), `/etc/claude-code/CLAUDE.md` (Linux), `C:\Program Files\ClaudeCode\CLAUDE.md` (Windows). Cannot be excluded by individual settings [7].
MCP as the matter-content bridge: Instead of syncing matter folders locally to every attorney, connect Claude to your DMS via MCP — NetDocuments MCP went live April 1, 2026; iManage targets H1 2026 GA. Attorneys query matter content through MCP; they don't need local copies. See /research/claude-mcp-explained.
Local mounts for attorney-personal content: `~/Cowork/` becomes each attorney's private workspace — drafts in progress, personal templates, scratch research. Matter content stays in the DMS. This separation keeps local mounts small (~5–20 files typically) and performance predictable.
Practice-area rules in .claude/rules/: Practice conventions that would bloat a single CLAUDE.md instead go into `~/.claude/rules/<practice>.md` files with path-scoped loading. Only loaded when Claude touches files matching the practice's path pattern. See our CLAUDE.md guide [1] for the rules-directory pattern.
Gateway/proxy for MCP: At 100+ users, an MCP gateway that logs tool calls and enforces allow-lists becomes standard — this is where enterprise-grade MCP governance lives. Out of scope for this article but covered in our MCP deep-dive.

What to Exclude From Mounted Folders

A lot of Cowork slowdowns come from files that shouldn't have been in the mount in the first place. Exclude these aggressively.

.git directories

If any folder in your mount is a git repo, the .git directory contains compressed object history that Cowork may try to read. Exclude via folder-level .claudeignore or move git-managed folders outside the mount.

node_modules, .venv, build/, dist/

Development artifacts in matter folders from custom tools. Not relevant to legal work; hundreds of MB of noise. Always exclude.

Large binary archives

ZIP files, TAR balls, backup archives, old discovery productions as multi-GB folders. Cowork cannot usefully read them and will still scan the directory listing. Keep archives in a separate non-mounted folder.

Email export files (.pst, .mbox)

Often multi-GB, rarely useful to mount raw. If you need email content for a matter, extract the relevant messages into readable form first.

Video and audio files

Deposition video, recorded calls. Cowork's agent cannot transcribe inline; use a transcription tool first and mount the transcript, not the media file.

Third-party production sets you haven't reviewed

A raw opposing-party production folder may contain content outside the matter's scope — or privileged material that was inadvertently produced. Never mount unreviewed productions; review, carve out what's relevant, then mount only the carved set.

Personal files that ended up in firm folders

Audit mount contents before adding. If an attorney's personal financial documents or unrelated drafts are in the folder, they'll end up in Cowork's context. Clean before mounting.

CLAUDE.local.md from other attorneys

If a shared folder has been used by multiple attorneys, CLAUDE.local.md files from previous users may linger. These are personal context files — not meant to be shared. Remove before mounting on a different attorney's machine.

How to Recognize a Bloated Mount

  • +If you see any of these, the mount is probably too large. Trim first, before debugging anything else.
  • +Cowork pauses for 20+ seconds before responding to a simple prompt. The pause is context ingestion. Smaller mount = faster start.
  • +Claude says 'I'll review the files' and then doesn't use the relevant ones. Attention is spread too thin across too many files. Reduce the mount to what the task actually needs.
  • +/compact fires multiple times in a short session. Classic sign of system-context bloat. If you're compacting every 5 minutes, the mount is the cause [5].
  • +Responses start accurate but degrade over the session. Context rot. Start a fresh session with a narrower mount.
  • +Cowork forgets the CLAUDE.md instructions partway through. When the context fills, earlier parts (including CLAUDE.md) can get pushed out of attention. Shorter mount = longer adherence.

The Active vs Archive Split

Matters have a lifecycle. Open matters get touched weekly; closed matters get touched maybe once a year for records requests. These two states deserve different mount strategies.

Active matters — mount freely: Mount the matter folder whenever an attorney works it. Update the matter `CLAUDE.md` as facts change. Close the session cleanly when done (no lingering mounts hoarding context across idle days).
Recently closed matters — keep accessible but unmounted: Keep the folder in `~/Cowork/Closed/` or similar. Not mounted by default. Mount only if a specific question arises (records request, collateral matter, follow-on representation). When you do mount, treat it as a fresh one-off session.
Archived matters — off the mount entirely: For matters closed more than a year or beyond retention review, move the folder outside any Cowork mount path. Firm record retention policies should govern, not convenience of Cowork access. If attorneys need archived matter content, use a deliberate export-and-review workflow rather than keeping the archive perpetually mounted.
Rotation discipline: Review mount contents monthly. If a matter hasn't been touched in 60 days and won't be, move it from `Active/` to `Closed/`. This keeps the active set lean and prevents the slow bloat that causes compaction spirals.

When Local Folders Are Wrong — The DMS Bridge

Local folder mounting is the right approach for small firms, individual attorney workspaces, and scratch work. For firms with matter content already in iManage or NetDocuments, trying to replicate that content locally is the wrong abstraction — the DMS is the source of truth, and its permissions, ethical walls, and audit logs matter. The right bridge is MCP.

The local-sync tax: Syncing matter content from iManage to every attorney's `~/FirmDrive/` means duplicated storage, stale local copies, and broken ethical walls. Any document that crosses an attorney's local sync boundary has left the DMS's governance. For small firms this is tolerable; at mid-firm scale, it becomes a compliance liability.
MCP preserves DMS governance: NetDocuments MCP (LIVE April 1, 2026) and iManage MCP (H1 2026 GA target) both commit to preserving 'existing permissions, ethical walls, and audit controls' through the connector. Claude reaches into the DMS, reads files on the attorney's behalf with the attorney's permissions, and the DMS records the access. Much cleaner governance than local sync.
Hybrid patterns work: Most mid and large firms end up hybrid: MCP for matter content in the DMS, local folders for attorney scratch work and personal templates, CLAUDE.md files in both places. The two approaches coexist fine.
Read the MCP deep dive first: Before standing up DMS-via-MCP, read our MCP guide: /research/claude-mcp-explained. The April 2026 security reckoning is relevant background for any MCP rollout.

Anti-Patterns

Predictable failure modes seen in the wild.

Mounting all of ~/Documents/

Every personal tax return, every old draft, every vendor invoice — all in Cowork's context. Slow, privacy-compromising, and the quality of Cowork's answers drops sharply. Always create a dedicated `~/Cowork/` folder and mount only that.

CLAUDE.local.md in source control or DMS

The `.local.md` suffix means 'do not share.' Committing it to source control or pushing it to iManage defeats the purpose. Add CLAUDE.local.md to .gitignore and your DMS ignore list.

Practice-area CLAUDE.md that duplicates firm-wide rules

Triples token cost, creates drift between copies. Write each rule at the broadest tier it applies to and trust the hierarchy. Firm-wide rule goes in firm-wide CLAUDE.md, only. See /research/claude-md-files-guide.

Mounting the firm's network share directly

It doesn't work (home-directory constraint). And even if it did, you'd expose every matter every attorney has ever worked to a single Cowork session. Use per-attorney active-matter sync or MCP instead.

Never rotating the Active/ folder

Matters accumulate. Without pruning, `Active/` grows from 5 matters to 50 over the course of a year. Performance degrades steadily. Monthly review is cheap; annual rebuild-from-scratch is painful.

Binary files in matter folders

Depositions in .mp4 format, evidence photos as 50MB JPEGs. Cowork can't read them usefully but will scan the directory. Pull them into a separate `~/Cowork/media/` folder that is NOT mounted into matter sessions.

The Bottom Line and Cross-Links

  • +Folder structure is the physical layer underneath Cowork's other context mechanisms. Get this right and CLAUDE.md, Global Instructions, and MCP all work better. Get it wrong and nothing else can save you.
  • +Three-step start for a firm new to Cowork: (1) Create `~/Cowork/` as the mount root. (2) Move only active matters into it, nothing else. (3) Add CLAUDE.md files at firm, practice, and matter levels per our template guide.
  • +The companion articles in this series:
  • +• Overview: Claude Cowork Cheat Sheet at /research/claude-cowork-cheat-sheet — what every feature does and how they combine.
  • +• Context files: CLAUDE.md Files: A Practical Guide for Law Firms at /research/claude-md-files-guide — the 200-line rule, the four-tier hierarchy, and three templates.
  • +• DMS bridge: Claude MCP Explained at /research/claude-mcp-explained — when local folders are wrong and the protocol bridge is right, plus the April 2026 security reckoning.

Key Takeaways

  • 1.Cowork reads folder context before every session. A bloated mount burns tokens before you type a prompt and triggers documented 'compaction death spiral' failures in extreme cases.
  • 2.As of April 2026, Cowork still restricts mounts to the user's home directory (~/ on macOS, C:\Users\<username>\ on Windows). Symlinks, junctions, external drives, and network shares are rejected — tracked in open GitHub issues.
  • 3.Cloud-synced folders (Google Drive, OneDrive, Dropbox) work unreliably via macOS FileProvider paths. Turn off on-demand / streaming modes and force full local sync for any folder Cowork will touch.
  • 4.Recommended hierarchy maps to firm structure: firm → practice → matter → content subdirectories. Put a CLAUDE.md at each level per our companion CLAUDE.md guide.
  • 5.Small firm (1–20 attorneys): collapse the hierarchy — `~/Cowork/Active/<matter>/`. Mid-firm (20–100): full three-tier. Large firm (100+): managed-policy CLAUDE.md + MCP for DMS content + local mounts only for attorney-personal work.
  • 6.Exclude aggressively: .git, node_modules, binary archives, email exports, video/audio, raw unreviewed opposing productions, personal files. Every irrelevant file burns context.
  • 7.Keep Active/ and Archive/ separate. Only mount active matters. Rotate monthly. Archived matters come outside the mount path entirely.
  • 8.For mid/large firms, MCP to the DMS (NetDocuments MCP LIVE April 1, 2026; iManage H1 2026 GA) is the cleaner bridge than replicating matter content via local sync — see our MCP deep dive.
  • 9.Symptoms of a bloated mount: 20+ second session start, Claude ignores relevant files, /compact fires repeatedly, CLAUDE.md instructions forgotten mid-session. Fix by trimming the mount.
  • 10.The simplest path forward for any firm: create `~/Cowork/`, put only active matters inside, add CLAUDE.md files at each level, and mount that — nothing else.

References

  1. [1]Anthropic, "Get started with Claude Cowork," Claude Help Center.Link
  2. [2]anthropics/claude-code GitHub, Issue #24964: "[BUG] Cowork: Folder picker rejects folders outside home directory, symlinks/junctions also blocked."Link
  3. [3]anthropics/claude-code GitHub, Issue #29914: "Claude Cowork can list but not read files in macOS FileProvider paths (Google Drive, Microsoft OneDrive)."Link
  4. [4]anthropics/claude-code GitHub, Issue #33590: "Claude Co-Work Cannot Access or Modify Files in Google Drive Directory — Limited to Home Directory Only."Link
  5. [5]anthropics/claude-code GitHub, Issue #24677: "Compaction death spiral in Cowork: 6 compactions in 3.5min due to system context consuming 86.5% of window."Link
  6. [6]anthropics/claude-code GitHub, Issue #27697: "[FEATURE] Cowork: Allow folder selection outside home directory (custom allowed paths)."Link
  7. [7]Anthropic Claude Code Docs, "How Claude remembers your project."Link
  8. [8]The AI Corner, "Claude Cowork Setup Guide: Context Files, Instructions, Plugins, Workflows (2026)."Link
  9. [9]Towards Data Science, "How to Maximize Claude Cowork."Link
  10. [10]Artificial Corner, "Before You Use Claude Cowork, Build This First."Link
  11. [11]Anthropic, "How large is the context window on paid Claude plans?" Claude Help Center.Link
  12. [12]Wondering About AI, "I tried using Claude Cowork to organize 2,200 files in my Downloads folder."Link
Back to Research