How to Use Claude Co‑work in 2026: Turn Claude into a Real Workflow Assistant

If you’re still copy‑pasting from Claude chat into docs and spreadsheets, you’re using a tiny fraction of what it can do. Claude’s Co‑work mode can act like a real digital employee: it operates on your computer, works with your actual files, runs research, and completes entire workflows while you do something else.

This guide walks you through how to set up Co‑work properly, how projects and skills work, and how to automate recurring tasks so Claude becomes part of your daily operations, not just a smarter chatbot.

Chat vs Co‑work vs Code: When to Use What

When you open Claude desktop, you’ll see three tabs: Chat, Co‑work, and Code. They each serve a different purpose:

Chat is for quick questions and back‑and‑forth conversations. You ask, it answers. Great for ideas and explanations, but you still have to manually move the output into your tools.

Code is for developers. It helps you write scripts, build apps, and work with code. It’s powerful, but assumes some technical skills.

Co‑work is different. It’s not just a chatbot and not just a coding assistant. It’s an AI worker that can operate on your computer, read and write local files, and complete end‑to‑end workflows: spreadsheets with working formulas, formatted Word docs, PowerPoint decks, and more.

Use Co‑work instead of Chat when:

• You want a complex task handled from start to finish.
• The work touches your local files directly (docs, sheets, slides, PDFs).
• You’re doing repetitive work every week.
• You need a mix of file work and online research.

If any of those are true, Chat is usually the wrong tool. Co‑work is built for that kind of work.

Essential Setup: Turn Claude into a Trained Employee

Most people skip setup and then wonder why outputs feel generic. With a bit of structure, Co‑work starts behaving like a trained employee who already understands you, your brand, and your workflows.

Step 1: Create a Dedicated Co‑work Folder

Don’t point Claude at your entire Documents folder. That’s noisy and confusing. Instead, create a single working folder, for example:

Co‑work Station

Inside it, create three subfolders:

• context – what Claude needs to know about you and your business.
• projects – active workspaces for ongoing workflows.
• output – where finished deliverables are saved.

This keeps your AI work clean, contained, and easy to manage.

Step 2: Add Context Files (The Real Unlock)

Inside the context folder, create three markdown files:

1. aboutme.md
Describe your role, your business, your audience, and what you care about. Two short paragraphs are enough. This helps Claude understand who it’s working for.

2. brandvoice.md
Explain your tone and style, plus examples of how you actually write. Include:

• Words and phrases you like to use.
• Words and phrases you never want to see.
• A short sample of your writing.

3. workingpreferences.md
Tell Claude how you like your work structured and how it should handle uncertainty. For example:

• How to structure documents and reports.
• Whether it should make decisions on its own or ask you first.
• Any formatting rules you care about.

Claude automatically reads these context files at the start of every session. That means you don’t have to re‑explain yourself every time.

Step 3: Set Global Instructions

In Claude desktop, go to Settings → Co‑work → Global instructions. Here you can define default behavior:

• Your typical role (e.g., marketing lead, founder, analyst).
• Default tone (e.g., professional but conversational).
• Preferred output formats (e.g., Word docs, Excel, markdown).

Think of this as the onboarding brief you’d give a new hire on day one. You write it once, and it applies to everything you do in Co‑work.

Real Workflow Examples: From Messy Inputs to Finished Files

Once setup is done, you can start handing Claude full workflows instead of tiny prompts. Here are two practical examples that show what Co‑work can actually do.

Example 1: Client Meeting Transcripts to Trackers and Emails

Imagine you have several messy client meeting transcripts: discovery calls, strategy sessions, follow‑ups. They’re full of crosstalk, vague action items, and fuzzy deadlines like “sometime next week.”

You want:

• A project tracker for each client.
• A short follow‑up email confirming next steps.

Your prompt to Co‑work could be:

“Process these six meeting transcripts. For each client, create: (1) an Excel project tracker with tasks, owners, deadlines, priority levels; (2) a follow‑up email under 150 words confirming next steps. Use a professional but conversational tone. Save all files to the output folder.”

Co‑work then:

• Reads multiple transcripts in parallel.
• Extracts tasks, owners, and deadlines (even when dates are implied).
• Calculates actual calendar dates from phrases like “end of next week.”
• Builds Excel files with proper columns, conditional formatting, and summary rows.
• Writes follow‑up emails that reference specific points from each client’s call.

What would normally take a couple of hours of manual work is done in minutes, and you get ready‑to‑send emails plus usable spreadsheets, not just text you have to copy somewhere.

Example 2: YouTube Niche Research in One Go

Say you want to understand what’s working on YouTube right now in the AI tools niche: top videos, hooks, topics, and content gaps.

Your prompt might be:

“Search YouTube for top‑performing videos in the AI tools niche from the last 30 days. For each of the top 10 videos, extract the title, view count, hook style, and main topic. Identify three content gaps (topics with high search interest but low competition). Save as a research report in Word format with an executive summary. Save to the output folder.”

Co‑work will:

• Open the web and run searches.
• Pull video data and rank by views.
• Categorize hook styles (e.g., curiosity gap, shock stat, before‑after).
• Identify content gaps with reasoning.
• Package everything into a Word report with an executive summary.

You can then add one extra line to the prompt:

“Also, suggest which of these three gaps best fits my channel based on my aboutme.md file.”

Now Claude cross‑references your context files and tells you which opportunity best matches your audience and style. That’s closer to a research analyst than a search tool.

If you’re new to Claude overall, you may also find this broader walkthrough helpful: a full Claude tutorial for beginners in 2026.

Projects: How Co‑work Learns Your Work Over Time

Global setup gives Claude a sense of who you are, but it doesn’t remember the details of each recurring workflow: what you changed last time, which formats you prefer for a specific client, or how you tweaked a particular template.

That’s where projects come in.

What a Project Really Is

Most people treat projects as simple folders for files. In Co‑work, a project is more than storage. It’s a workspace that combines:

• Files (inputs and outputs).
• Project‑specific instructions.
• Context files (like brand voice).
• Work history and adjustments.

Over time, each project becomes a specialized environment tuned to a specific workflow.

Example: Client Deliverables Project

Suppose you create a project called Client Deliverables and point it at your client folder. Inside the project, you add instructions like:

• “Use brand voice from context files.”
• “Emails always under 150 words, professional but conversational.”
• “Excel trackers use this column order: task, owner, deadline, priority, status.”

Now, when you run the same transcript‑to‑tracker workflow inside this project:

• Spreadsheets automatically use your preferred column order.
• Emails match your brand tone.
• Formatting stays consistent across clients.

On future runs with new inputs, the project already contains previous outputs and any edits you made. Co‑work can build on that history, so results get closer to what you want without you repeating instructions.

A good rule of thumb: create one project per recurring workflow, such as:

• Client deliverables.
• Content production.
• Admin and finance.
• Weekly reporting.

Each project compounds in value the more you use it.

Skills: Reusable Playbooks for Your Best Work

Projects give you memory; skills give you repeatability. A skill in Co‑work is an instruction file that tells Claude exactly how to handle a specific type of work. Think of it as a detailed playbook for one workflow.

Co‑work ships with built‑in skills for Excel, PowerPoint, Word, and PDFs. When you ask Claude to build a spreadsheet, it automatically uses the Excel skill so you get formulas, charts, and proper formatting instead of a raw data dump.

But the real power comes from custom skills.

Why Custom Skills Matter

Without a custom skill, if you ask Claude to write a content brief, you’ll usually get a generic structure that looks like every AI‑generated brief: predictable sections, bland tone, and little personality.

With a custom content brief skill, you can define:

• The exact sections you want (e.g., audience, angle, hook, outline, CTAs).
• The tone and style that match your brand.
• Specific research prompts or checks you always run.
• Any formatting rules you care about.

Once that skill is loaded, every new brief follows your structure and reads like something you wrote yourself.

You can build skills for any repeatable workflow, such as:

• Weekly reports.
• Sales proposals.
• SOPs and playbooks.
• Onboarding documents.
• Content outlines and scripts.

Create the playbook once, and Claude follows it every time.

If you’re interested in going even deeper into AI agents and automation, you might also like this guide on setting up your first AI agent in 2026.

Scheduled Tasks: Let Claude Work While You Don’t

Once you have good projects and skills, the next step is to stop running everything manually. Co‑work lets you schedule tasks so Claude runs them automatically at set times—no code, no APIs, no extra tools.

How Scheduling Works

In the Co‑work sidebar, open Schedule and create a new task:

• Write your prompt (just like you would normally).
• Choose how often it should run (daily, weekly, etc.).
• Save.

From then on, Claude will run that workflow on your desktop at the chosen time.

Some examples:

1. Morning Briefing (Daily)
“Every morning at 9:00 a.m., check Gmail for unread messages from the last 12 hours, check calendar for today’s events, extract action items and deadlines, save as morningbrief.md in the daily briefings folder.”

You wake up to a concise summary of what actually needs your attention.

2. Weekly Content Research (Weekly)
“Every Monday at 12:00 a.m., search trending topics in AI productivity from the past 7 days, identify three content opportunities based on search volume and engagement patterns, save research brief to the content project, post summary to Slack.”

Your content calendar starts to fill itself with data‑backed ideas.

Keep in mind:

• Tasks only run while your computer is awake and Claude desktop is open.
• Each run counts against your usage, so keep prompts tight and focused.
• Always test a task manually before scheduling it.

Dispatch: Trigger Full Workflows from Your Phone

Sometimes you’re away from your desk but still want to kick off a workflow. That’s where Dispatch comes in.

Dispatch lets you send Claude a task from your phone. The task runs on your desktop, using your existing projects, context, and skills, and you get a notification when it’s done.

Setup is simple:

• Open Co‑work on your phone.
• Enable Dispatch.
• You’re ready to go.

From there, you can trigger things like:

• Full research reports while you’re at the gym.
• Content audits from a coffee shop.
• Client deliverables from your car before a meeting.

Claude automatically routes tasks to the right mode (Code vs Co‑work) based on what you ask. Your phone becomes a remote control; your desktop does the heavy lifting.

Putting It All Together: A Complete Content System

Here’s how everything looks when you combine projects, context, skills, and scheduling into one working system—for example, a YouTube content workflow.

1. Create a YouTube Content Project
Point it at a dedicated folder and add instructions like:

• “Use a conversational tone.”
• “Use pattern‑interrupt hooks.”
• “Open with the problem first.”
• “Write in spoken paragraphs, never bullets.”

2. Add Context Files to the Project
Drop your aboutme.md and brandvoice.md into the project so scripts match your voice and audience.

3. Connect Your Tools
Connect Gmail, Calendar, Slack, Notion, or other apps Co‑work can access, so it can pull tasks, events, and notes into your content planning.

4. Set Up Scheduled Tasks

• Morning briefing (daily, 9:00 a.m.): Check Gmail, calendar, Notion; summarize what’s on your plate; save as morningbrief.md in the project.
• Content research (weekly, Monday 12:00 p.m.): Search trending AI automation topics from the past 7 days; identify three video opportunities; save a research brief to the project; post a summary to Slack.

Now, when you sit down to create, you’re not staring at a blank page. You have a script outline that:

• Matches your voice and structure.
• References fresh research Claude already pulled.
• Lives inside a project that remembers what worked last time.

Key Takeaways

To get the most out of Claude Co‑work, keep these three principles in mind:

1. Setup is everything.
Your folder structure and markdown context files (aboutme.md, brandvoice.md, workingpreferences.md) are non‑negotiable. A few minutes of setup can save hours every week.

2. Use projects for anything you do more than once.
Projects give you memory at the workflow level. They accumulate context and edits over time, so Co‑work starts to feel like a real employee who learns how you like things done.

3. Scheduled tasks are the real unlock.
Scheduling turns Claude from a tool you use into an assistant that works for you in the background. That shift—from generating content to completing work—is where the real leverage is.