Claude Cowork Local File Access: What Really Syncs

Claude Cowork Local File Access: What Really Syncs

The task ran. The task synced. The task showed up on my phone. And then Claude, sitting in a rideshare interface on a 6-inch screen, told me it couldn't touch a single file in the folder I'd pointed it at ten minutes earlier from my desk.

That was my introduction to the actual rules of Claude Cowork local file access after the July 2026 cloud update — not the version in the announcement, the version that shows up when you're three tasks deep and something quietly refuses to work. Anthropic's blog says your sessions and files "go where you go, on any device." That sentence is true. It's also doing a tremendous amount of hiding. Because whether Claude can reach the real files on your real hard drive depends on three things most people never think to check: where the task was born, which approval setting you picked, and whether your desktop is still awake.

I've spent the last few days deliberately breaking this to find the edges. Here's the map I wish I'd had on day one — the three kinds of tasks, the one dropdown that silently strands your work, and the exact conditions under which your phone can and can't reach your laptop's files.

The One-Line Answer, Before Anything Else

Here's the direct version, because you probably searched for it: Claude Cowork local file access only works through the desktop app, and a task can keep that access from your phone only while your computer is powered on with Claude Desktop running. Tasks you start on web or mobile never get local file access at all. Tasks you start on desktop keep it — but only if you leave that machine on, and only if you picked the right approval mode.

That's the whole thing in four sentences. Everything below is the why, the how to set it up, and the trap that turns "it works" into "it silently stopped working" — because the difference between those two states is one setting almost nobody looks at.

If you want the emotional, big-picture version of what this launch means — the "your assistant now keeps its hours after you close the laptop" story — I wrote that up separately in my hands-on first look at Cowork on mobile and web. This piece is the opposite. This is the engineering manual. This is what you read after the excitement wears off and you're trying to figure out why yesterday's file cleanup isn't on your phone.

Why This Matters Right Now, Specifically

Anthropic shipped Cowork to iOS, Android, and the web on July 7, 2026, rolling out to Max subscribers first, with usage limits doubled through August 5 to get people stress-testing it. So there's a real clock on this. You've got a window where experimentation is effectively half-price in tokens, and the smart move is to figure out the file-access rules now, while mistakes are cheap, rather than in September when every misfired scheduled task costs you real quota.

But here's the part that makes the local file access question urgent rather than academic. Anthropic has said publicly that more than 90% of what Cowork does is not software development — it's everyday knowledge work, and roughly half of all usage is business operations or content creation. That means most people using Cowork aren't running ephemeral code sandboxes. They're pointing it at actual folders — the client documents, the invoices, the video project files, the spreadsheet that lives on their Documents drive. For those people, "can Claude reach my files from my phone?" isn't a nice-to-have. It's the entire question.

And the answer the marketing gives — "your work goes where you go" — is precisely true for cloud-born work and precisely false for the local file grind. Confuse the two and you'll build a workflow on a foundation that isn't there. So let's separate them cleanly, starting with the thing the announcement glosses over entirely.

There Aren't Two Kinds of Cowork Tasks. There Are Three.

Almost every explainer I've read, including good ones, describes the new Cowork as a binary: cloud sessions that sync everywhere, and local sessions that stay on your desktop. Clean story. Wrong count.

There are three, and the third one is where all the confusion lives.

Type 1 — The pure cloud task. You start it on web or mobile. It runs entirely on Anthropic's servers, its files stored server-side. It shows up on every device including your desktop. It is convenient, portable, and completely blind to your local hard drive. It cannot open the invoice on your Documents folder because, from its point of view, that folder does not exist. There is no bridge to your machine.

Type 2 — The pure local task. You start it on desktop, and — this is the trigger — you set it to skip all approvals. It runs locally on your machine, touching real files, and it does not sync to the cloud. It is invisible on web and mobile. It's the old Cowork, essentially: powerful on the box it was created on, stranded there.

Type 3 — The hybrid task, which is the actually-new thing. You start it on desktop and set it to require manual approval. Now something genuinely different happens. The task syncs to the cloud and retains a live bridge to your local files. You can open it, monitor it, and continue it from your phone or the browser — while it still reaches into the real folders on your desktop machine.

Type 3 is the release. Type 3 is what "your work goes where you go" is quietly describing when local files are involved. And Type 3 comes with a leash: that live bridge to your files only exists while your desktop computer is on and Claude Desktop is running. Close the lid, and the phone still sees the task — but the file access blinks out.

Read that structure again, because the whole rest of this piece is just consequences of it. Two of the three task types can't touch your local files at all. Only one can do it remotely. And the difference between the two desktop types — the stranded one and the portable one — comes down to a single dropdown you clicked past without reading.

The Dropdown That Decides Everything

When you kick off a task on Cowork desktop, there's an approval setting. Most people treat it as a "how annoying should the permission prompts be" toggle. It is not. It is the switch that determines whether your task is a Type 2 or a Type 3 — whether it stays chained to your desk or follows you to your phone.

The two options that matter here:

"Skip all approvals" — formerly labeled "act without asking." Claude runs the whole task with no pauses, no checks, nothing verifying its actions against your permissions. Anthropic's own safety guidance is blunt about this one: you should only use it when you completely trust every action, connector, file, and app the task will touch. And critically for our purposes — a task set to skip all approvals runs local-only. It does not sync to the cloud. Pick this, and you've built a Type 2. It will never appear on your phone, no matter how much you want it to.

"Manually approve" — Claude pauses at the decisions that carry weight (sending an email, spending money, deleting files, reaching into new folders) and pings you for a yes or no. Because it's checking with you, it consumes more of your usage limit than skip-mode does. But this is the setting that produces a Type 3: cloud-synced, phone-visible, and still wired to your local files while the desktop's awake.

So here's the trap, stated plainly. If you want to start a file-touching task on your desktop and then keep working with it from your phone, and you reach for "skip all approvals" because you don't want to be pestered with permission prompts — you've just guaranteed the exact opposite of what you wanted. You've locked the task to your desk. The setting that feels like more freedom is the one that takes your portability away.

I did this to myself on the first day. Set a document-sorting task to skip approvals so it'd run unattended, walked away, checked my phone an hour later expecting to see progress, and found nothing. The task was running perfectly — on my Mac, invisible to every other device I own. Nothing was broken. I'd simply told it to be a Type 2 and then expected Type 3 behavior.

That's the single most important sentence in this article, so I'll make it its own paragraph: to keep local file access reachable from your phone, start the task on desktop and choose "manually approve," not "skip all approvals."

How to Tell Which Kind of Task You've Got

Anthropic built a diagnostic into the interface, and once you know to look for it, the guesswork disappears.

Each task carries an icon that tells you where it actually runs:

• A cloud icon means the task runs in the cloud and syncs across your devices. Type 1 or Type 3.
• A computer icon means the task runs locally only and stays on that machine. Type 2.

Glance at the icon before you close your laptop and you'll know instantly whether that task is coming with you or staying behind. If you were counting on continuing something from your phone and it's wearing a computer icon, that's your warning — it's a local-only task, and no amount of refreshing the mobile app will summon it.

One more diagnostic detail that catches people. A task you started on web or phone will show the cloud icon — because it is a cloud task, a Type 1 — but that cloud icon does not mean it can reach your local files. It can't. Nothing you initiate off the desktop ever gets a bridge to your hard drive. The cloud icon tells you the task syncs; it says nothing about local file access. Those are two separate properties, and conflating them is the second most common mistake I've watched people make with this release.

The Setup Checklist for Claude Cowork Local File Access

If you updated the app and expected Type 3 tasks to just work, you may have found them not working — and the reason is usually one of three boring, fixable things. Here's the sequence I ran to get cloud sync plus local file access behaving reliably.

1. Update every Cowork surface to the latest version. Desktop and mobile both. A version mismatch between your phone and your desktop is the fastest way to get sync that half-works — tasks appearing but not updating, or approvals not routing. Update all of them before you troubleshoot anything else.

2. Sign out and back in on every instance. This is the step people skip, and it's the one that fixes the most problems. The update changes how your session authenticates against the cloud, and existing logins can end up in a stale state. Some instances auto-logged me out after updating; others I had to manually sign out of and back into. Do it everywhere — desktop and phone — so every device re-authenticates against the new cloud session model. If your tasks aren't syncing after the update, this is almost always the fix.

3. On desktop, pick "manually approve" for any new task you want to be portable. We covered why. This is the step that turns a local task into a hybrid one. Make it a habit for anything file-related that you might want to touch from elsewhere.

That's it. Three steps, and the "sign out and back in everywhere" one does more heavy lifting than it has any right to. If you've done all three and a desktop-started, manually-approved task still won't show local file behavior on your phone — check whether the desktop is actually still on. Which brings us to the constraint that trips up even people who set everything up correctly.

The Leash: Your Desktop Has to Stay Awake

Here's the condition that separates "I can access my files from my phone" from "I can access my files from my phone sometimes."

A Type 3 task — desktop-born, manually-approved, cloud-synced — can reach your local files from a remote device only while the Claude Desktop app is open on the powered-on computer that holds those files. Anthropic's help documentation states it directly: a remote session reaches your computer only when the Claude Desktop app is open, only for the folders you've connected there, and with the permissions you've already set. Every local file the session touches gets checked against those permissions before it runs.

Unpack what that means in practice. Your phone is not talking to your files directly. It's talking to the cloud session, and the cloud session is reaching back through your still-running desktop app to touch the actual disk. Your desktop is the bridge. Kill the bridge — shut the laptop, quit the app, let the machine sleep — and the cloud session survives, the task is still there on your phone, but the file-access half of it goes dark. Claude can keep doing anything that lives in the cloud. It just can't reach a folder that only exists on a machine that's now asleep.

This is why the "runs while your laptop's closed" excitement needs an asterisk the size of a billboard. Cloud-only work — Type 1 tasks, pure server-side operations — genuinely runs with every device dark. I've had scheduled cloud tasks fire at 6 AM with my Mac shut and offline, and they executed fine, because they never needed my hardware. But the moment a task depends on a real local file, that independence evaporates. The file lives on your machine. Reaching it requires your machine to be reachable. There's no cloud copy of your Documents folder for Anthropic to serve.

Once I internalized this, my mental model got simple: cloud work is device-independent; local-file work is desktop-tethered, even when you're driving it from your phone. The phone is a remote control for a bridge that has to stay standing.

The Practical Playbook: Match the Task to the Rules

Theory's done. Here's how I actually organize work now that I understand the three types, sorted by what you're trying to accomplish.

If the task doesn't need local files at all — research, drafting, summarizing, pulling from cloud connectors like Gmail or a web crawler, generating something from scratch — start it wherever you are. Phone, browser, desktop, doesn't matter. It'll be a Type 1, it'll sync everywhere, and you never have to think about whether a machine is awake. This is the majority of knowledge work, honestly, and it's the effortless case.

If the task needs to touch real files on your disk and you want to monitor or continue it remotely — start it on desktop, choose "manually approve," confirm it shows the cloud icon, and leave that computer powered on with Claude Desktop running. Now you've got a Type 3: file access on the desktop, visibility and control from your phone. This is the hybrid sweet spot, and it's the genuinely new capability worth restructuring a workflow around.

If the task needs local files but you'll only ever run it at your desk — set it to skip all approvals if you fully trust every action, let it run unattended locally, and don't expect it on your phone. That's a deliberate Type 2. Perfectly fine, as long as you chose it rather than stumbled into it.

Here's the setup move I now use to make the good case automatic. In the desktop app, I select the key working folder I want Claude to have access to, then start one basic task there with a trivial prompt — literally just enough to establish the session against that folder with manual approval. From that moment, the task is cloud-synced and reachable across all my devices while retaining its local file access on the desktop. It becomes the anchor session I continue from wherever I am. One deliberate setup at the desk, portable for the rest of the day.

If you'd rather have someone architect this whole cross-device setup for your business — the folder connections, the approval policies, the scheduled tasks that fire in the cloud and the hybrid ones that keep local access — that's exactly the kind of build I take on. You can see my work at fiverr.com/s/EgxYmWD.

How This Compares to the Old Way — and to Dispatch

To appreciate why the three-type model is an upgrade rather than just complexity, it helps to remember what remote Cowork used to be.

Before this, if you wanted to touch a task from your phone, your only real option was Dispatch — and Dispatch worked completely differently. It turned your phone into a remote control pointed at a desktop that had to stay awake, running everything through one continuous conversation. No separated tasks, no cloud sessions, just a live line to a Mac that couldn't sleep. I walked through its quirks in detail when I tested Dispatch back in March, and the short version is that it always felt like a workaround. The phone wasn't independent; it was a window into a machine.

The new model keeps the one genuinely useful thing about that arrangement — remote access to local files via a running desktop — but rebuilds everything around it. Now you get distinct, separated tasks instead of one endless thread. You can see every cloud task from mobile and web, including the hybrid ones that still reach local files. You choose the AI model per task. There's even a dictation button for voice input when you're kicking things off from your phone. Dispatch was a tether. This is an actual architecture, with the tether reserved only for the specific case that genuinely needs it — local files.

And if you want the broader tour of running Cowork from your pocket, my older write-up on controlling Claude from your phone and my breakdown of Cowork's scheduled task automation both hold up — but this release is the first time the initiation point and the file access became separate, controllable properties instead of one fused constraint.

What I Got Wrong, and What I'd Warn You About

I'll be honest about the misconceptions I carried in, because they're probably yours too.

I assumed "cloud sync" and "local file access" traveled together — that a task showing up on my phone meant it could do everything there that it could at my desk. Wrong. Those are orthogonal. A task can sync perfectly and still be blind to your disk (any Type 1), and the cloud icon tells you nothing about file reach. Keep those two properties separate in your head and half the confusion dissolves.

I also assumed the safest-sounding, least-annoying approval setting was the harmless default choice. Also wrong, in a different direction. "Skip all approvals" isn't just a convenience toggle — it changes the architecture of the task, forcing it local-only, and it removes every safety check at the same time. That's two significant consequences hiding behind a setting that reads like "don't bug me." I'd treat "skip all approvals" as a deliberate, high-trust choice, never a default, and not only for the file-portability reason — for the security one too.

The limitation I'd flag hardest: none of this lets you leave your desktop off and keep local file access. If your work genuinely lives in local files and you genuinely need it while traveling with the laptop shut, this release does not solve that. It solves the "my laptop is on at home and I want to drive it from my phone" case beautifully. It does not solve "my files are on a machine that's asleep." Whether Anthropic eventually lets local desktop work sync fully into the cloud is the open question I'm watching, and they haven't said. Until they do, plan around the leash.

The Takeaway You Can Act On Tonight

Go back to that rideshare, phone in hand, task synced but files unreachable. That wasn't a bug. That was the system working exactly as designed, and my mental model being wrong. The task had followed me. My files hadn't — because they couldn't, from a task I'd initiated the wrong way with the wrong setting.

The fix wasn't technical. It was understanding. Cloud work is portable and device-independent. Local-file work is desktop-tethered, reachable from your phone only through a desktop that stays awake, and only when you start it on desktop with manual approval. Three task types, one dropdown that decides which you get, one icon that tells you the truth, one leash you can't cut yet.

So here's your move while limits are still doubled through August 5. Pick a folder you actually work in. Open Cowork on your desktop, point a task at that folder, set it to manually approve, confirm it shows the cloud icon, and leave your computer on. Then walk away, open the same task on your phone, and try to have Claude touch a file in that folder. When it works, you'll have felt the entire architecture in one motion — and you'll never again wonder why some tasks reach your files from your pocket and others just sit there wearing a cloud icon that promised more than it could deliver.

Let's Work Together

Looking to build AI systems, automate workflows, or scale your tech infrastructure? I'd love to help.

• Fiverr (custom builds & integrations): fiverr.com/s/EgxYmWD
• Portfolio: mejba.me
• Ramlit Limited (enterprise solutions): ramlit.com
• ColorPark (design & branding): colorpark.io
• xCyberSecurity (security services): xcybersecurity.io