My file system is a disaster in a way that builds up over years of telling yourself you’ll sort it later. Nothing is unfixable, it’s just boring enough that something else always takes priority - and after long enough, the pile gets too big to feel worth starting on. I’d been hearing about Cowork for a while and figured if anything was going to make a dent in this, something that runs inside Claude already was probably worth trying - I already use Claude every day anyway.

My expectations weren’t high - Cowork gets talked about mostly by marketers and content teams and people running actual operations, and I’m none of those things. I just have a lot of bad organization habits. But I tried it anyway, and it turns out that’s a fine enough reason.

A few things worth knowing first

The setup, the caveats, and who Cowork is actually for

Cowork is Claude’s desktop agent - you need the desktop app and at least a Pro subscription, it’s not on the web version or the free plan. The general idea is that it can actually execute tasks on your computer rather than just talk you through them: reading files, renaming things, sorting folders, and if you connect it to external tools, handling browser and email workflows too. That last part is where most people seem to get the most out of it, and it’s also why I assumed it wasn’t really built for someone like me.

I’m not connecting the browser or Gmail integrations, which is a deliberate call. Prompt injection is a real and documented attack vector - malicious instructions hidden inside a webpage or an email can manipulate what an agent does on your behalf without you realising it. Anthropic’s own safety documentation flags web content and email as the primary surfaces for this.

This is what made me think Cowork was going to be pretty limited for my use case, since that’s where most of the touted functionality lives. Turns out the local-only version is more capable than I gave it credit for - there’s a lot it can do without connecting to cloud or online tools, and for someone whose main problem is a chaotic file system rather than a chaotic inbox, it’s been more than enough.

Why not just use the filesystem connector?

One needs you in the chat, the other doesn’t

The filesystem connector in regular Chat does a lot of the same things Cowork does. It can also access your files, scan them, and amend them. The issue isn’t really what it can’t do. Filesystem has actually been the backbone of a lot of my workflows, including connecting it to Obsidian for easy access to my notes and bringing them into the context of any conversation. This is also part of what took me a while to try Cowork - I already had access to my local files through filesystem.

But Cowork operates differently. It’s not necessarily more powerful than the filesystem in Chat; you don’t actually get the same chat context in Cowork, but you do get more broad-spectrum and automated control. Where it pulls ahead for recurring file work specifically is context memory - every folder you connect to Cowork gets a CLAUDE.md file dropped into it, which is basically a plain text file storing the rules for that folder. Naming conventions, sorting logic, what the folder is actually for, whatever you need Cowork to execute in that folder.

Every time you point Cowork at that folder again, the md file loads automatically and you don’t need to re-explain or re-establish anything. So my Screenshots folder and Downloads folder can have completely different instructions and Cowork just knows, per folder, the moment I start a task. For something like file admin where you’re doing the same kinds of tasks over and over, never having to rebuild that context is such a time saver.

Cowork also has extras that Chat lacks. There’s scheduling - repetitive tasks can run automatically without you initiating anything. And Dispatch lets you kick off tasks from your phone if you think of something while you’re away from your desk. So basically, filesystem needs you to guide it in the Chat, and it works best in the conversational context. Whereas Cowork needs to be instructed once and it’ll run the task from start to end, on repeated schedule if you like.

How I’m actually using Cowork

Keeping it local-only, and it’s still more useful than I expected

What I kept seeing before I tried Cowork was people building out elaborate skill libraries for marketing workflows and content pipelines. Skills are basically saved instruction sets you can load into Cowork for recurring task types - there’s a whole community library of them, and they’re definitely worth grabbing or making your own. But the reason I kept dismissing Cowork is the same reason I eventually found a use for it - most people seem to be doing a lot more with it than I needed to.

What I actually needed was someone to handle my file mess. Screenshots mostly, but also downloads and notes. The reason Cowork works better than the filesystem connector for this specific thing comes back to context - there’s no chat happening in Cowork, so the entire context window goes toward the task. Pointing it at a large folder of screenshots and asking it to read, rename, and sort all of them is a different ask than doing the same thing in Chat where tokens are already being spent on conversation and I’m trying to stay on track of what’s being discussed.

One of the specific workflows I set up: Cowork reads every screenshot in my folder, figures out what’s in each one (without me needing to add them manually, so there’s no 20-file upload cap), and sorts it into the relevant subfolder based on topic. That runs on a schedule every night before I shut my PC down. Screenshots are one of the biggest bottlenecks in my workflow, so this has been a major help. Same logic applies to my downloads and my notes folders, just with different instructions loaded in the CLAUDE.md for each one. Nothing sophisticated about it, it’s just file admin that was never going to happen manually.

File admin, handled

If your version of file management is telling yourself you’ll sort it later and then not doing that, Cowork can fill that gap. I’m not using it for anything ambitious - no integrations or elaborate skill stacks, and nothing that touches the outside world. Just a few folders that needed someone to care about them more than I did. Turns out that’s a legitimate use case, even if nobody’s making YouTube tutorials about it.