Claude Cowork: How to Set Up Your AI Working Partner in 30 Minutes

Mar 13, 2026 · 9 min read

You've used Claude before. You've written something detailed, got back something technically fine but completely generic, spent 20 minutes editing it to sound like you, and wondered why you bothered.

Then you tried again the next day. Same problem. Every session starts cold. The machine has zero memory of who you are, how you think, or what you're building.

So you compensate. You cram your professional identity into every prompt. Voice guidelines. Priorities. Standards. Every single time.

Claude Cowork solves this. And the setup takes less than 30 minutes.

What Claude Cowork Actually Does

Cowork is a tool built into the Claude Desktop app. You give it access to a folder on your computer. It reads your files, creates new ones, runs multi-step tasks, and delivers finished work directly to that folder.

No command line. No code. You describe what "done" looks like, and the machine plans, executes, and delivers.

The key difference from regular Claude chat: Cowork works with your actual files. You stop copying and pasting things in and out of a chat window. You delegate real work, walk away, and come back to a finished deliverable.

But here's the part most people miss in the setup. Cowork can read context files before every task. Which means you can give it a single document that captures who you are, how you work, and what you're focused on. Load that once, and every session starts with full context instead of a blank slate.

That document is the difference between a generic tool and a working partner.

The SIM Card: One File That Changes Everything

Think about your phone before you insert a SIM. It's a capable device. It connects to Wi-Fi, runs apps, takes photos. But it doesn't know who you are.

AI works the same way. Claude, out of the box, is powerful but generic. Every response starts from nothing because there's no context for you, your work, your voice, or your direction.

Install one file and the experience transforms. You're working with a partner that knows your expertise, matches your communication style, understands your priorities, and produces work that sounds like it came from someone on your team.

That file is your operating system. It lives in your workspace folder, and Cowork reads it automatically before every task.

Here's what that looks like in practice:

Before: You write a 200-word prompt explaining your role, your voice, the format, the audience, what to avoid, and what "good" looks like. Every single time.

After: You write: "Create a client summary from the files in /project-x/notes. Match my usual format." Ten words. Output that sounds like you wrote it.

The SIM card does the heavy lifting that used to live in your prompts.

How to Set Up Claude Cowork Step by Step

Step 1: Get Cowork Running (5 minutes)

Download the Claude Desktop app from claude.ai/download. You need a paid plan. Open the app and click the Cowork tab.

You should see a clean workspace. If you're prompted to select a folder, that comes next.

Step 2: Create Your Workspace Folder (5 minutes)

Make a folder on your computer. Call it whatever makes sense: Claude-Workspace, AI-Workspace, your name. Inside it, create two subfolders:

Claude-Workspace/
  context/      → Your SIM card lives here
  projects/     → Active work folders

Two folders is all you need. Point Cowork at your workspace folder when it asks.

Important: Don't share your entire Documents directory. Keep the scope contained. Cowork has real read/write access to whatever you share.

Step 3: Build Your SIM Card (20 minutes)

Create one file in your context/ folder. This is your operating system for AI.

It covers three dimensions: Self (who you are), Systems (how you work), and Strategy (where you're headed). One document, three layers of context, and the machine stops guessing.

If you know my work, you'll recognise this. This is my Amplify OS™ framework applied directly to your AI workspace. The same architecture I use in keynotes and workshops, installed as a single context file.

Here's what the three dimensions cover:

Self: Your expertise, your voice, your values, your quality standards. This is what makes the AI sound like you instead of a committee report.
Systems: Your tools, platforms, processes, workflows, and working preferences. This is how the AI fits into the way you already operate.
Strategy: Your current priorities, positioning, active projects, and what you're deliberately NOT doing. This gives the AI direction instead of trying to optimise for everything.

The section that matters most for output quality is your voice. Include 2-3 samples of writing you're proud of: emails, posts, client communications. These teach voice better than any description. Add your anti-patterns too: "never write like this." The more specific you are, the less editing you do on the other side.

The section most people skip but shouldn't: what you're NOT doing. Without it, Claude optimises for everything. With it, every output serves the direction you're actually moving.

Use the Amplify OS™ Builder to create your context document.

You don't need a novel. A solid first version takes 20 minutes. Start with what you know and refine as you go. This is a living document: update it as your priorities shift and your standards sharpen.

Step 4: Set Global Instructions (2 minutes)

Go to Settings in the Claude Desktop app. Find the Cowork section. Add your ground rules:

Before starting any task, read my context files first.
Always ask clarifying questions before executing.
Show a brief plan before taking action.
Never delete files without my explicit approval.

Four lines. These shape how Cowork behaves in every session. Adjust to suit how you want it to operate.

Three Claude Cowork Workflows to Try Today

Don't just read about this. Pick one and run it now.

Workflow 1: The Voice Test

Once your context file is saved, open a new Cowork session and type:

Read my context files. Then write a short LinkedIn post about a challenge I'd typically face in my work. Match my voice exactly.

Read the output. Does it sound like you? If it reads like a generic AI post, your voice section needs more specificity. Add writing samples. Add your anti-patterns ("never write like this"). Run it again.

This single test tells you how strong your SIM card is.

Workflow 2: The Messy Folder

Find a folder on your computer with 30+ disorganised files. Point Cowork at it and ask:

Organise these files into sensible subfolders. Rename them with consistent naming conventions. Create a log of every change you make so I can review it.

What takes you an hour takes Cowork a few minutes. And because it has your context, the naming conventions and folder logic should match how you actually work.

Workflow 3: From Raw Notes to Finished Output

Drop some rough notes, a meeting transcript, or a collection of client feedback into a project folder. Then:

Synthesise everything in /project-name/ into a structured summary. Include key themes, decisions made, and action items. Format it as a clean document I could share with a colleague.

This is where the partnership becomes real. You provided the raw material. The machine shaped it. You review and refine. The output should be 80% there on the first pass if your SIM card is well-built.

Common Claude Cowork Problems (and How to Fix Them)

What Happens	What It Means	What to Do
Output is generic	SIM card is thin on voice	Add more writing samples and anti-patterns to your context file
Output misses the point	Task brief was vague	Be specific about what "done" looks like before asking
Technically right but wrong tone	Voice section needs work	Add examples of "never write like this" to your context file
Claude asks good questions before starting	Everything is working well	Let it run: this is the goal
Excellent on first pass	SIM card is dialled in	Celebrate it. This is what partnership looks like.

Making Claude Cowork a Daily System

One solved problem is useful. A repeatable workflow that runs every week without you thinking about it is a business advantage.

Three moves to get there:

Stop doing it manually. You just proved the machine can handle it. Let it.

Turn your task into a reusable brief. Save the prompt that worked. Structure your recurring prompts using the ACT framework to get consistent results. Set up the folder structure so files flow in and outputs flow out. If it's recurring, use Cowork's /schedule command to automate it.

Redirect your attention. What does this free you up to do? The client call. The strategic decision. The creative work that requires your full presence. Focus there.

The people who get the compound return from Claude Cowork refine their context file after every session and build one workflow at a time. Not ten. One. Get that one dialled in. Then add the next.

Start Here

Three things to do right now:

Build your context file. Use the Amplify OS™ Builder to create it. 20 minutes gets you a working first version.
Run one workflow. Pick the voice test, the messy folder, or the raw-notes synthesis. See what happens.
Refine after. Whatever the output got wrong, fix it in your SIM card. That's the compound return.

The setup takes an afternoon. The return shows up every day after that.

Your wisdom, your relationships, your judgment: those stay yours. The machine handles the production mechanics. That's the partnership.

Launch the Amplify OS™ Builder and start building your AI working partner.