Claude Cowork Daily Tasks Worth Scheduling (Not the Viral Slash List)

Claude Cowork daily tasks worth scheduling are recurring jobs, not a one-shot organize-my-files chat.

You keep handing the same morning pile to a window that treats Tuesday like a first hello. Someone sent you a list. You typed the first slash. The product stared back. The jobs that actually come back finished were never on that list.

Claude Cowork daily tasks are recurring knowledge-work jobs: file cleanup, connector briefs, document transforms, and scheduled automations. Cowork is the non-coding agent workspace in Desktop, web, and mobile. Create a cadence with /schedule or the Scheduled sidebar; cloud tasks run with the laptop closed. Viral lists that teach /compact, /clear, /plan, /doctor, /memory, /cost, and /undo as Cowork commands are naming Claude Code. Cowork's / surface is /schedule and /plugin-name:command.

Monday 7:12. I opened the knowledge-work window and typed the first slash from a saved list. Compact, then clear, then plan. The names felt like muscle memory from a terminal I use for repos. The briefing I actually needed was still sitting in Gmail.

That is the mix-up this catalog exists to kill.

Most people still open Cowork, type "organize my files," and stop there. That prompt is a real job. It is not the product. Claude Cowork uses, on the official product page, the same agentic architecture as Claude Code without a terminal: research, analysis, documents, spreadsheets, slides, local folders, connectors, scheduled tasks. The features that matter for daily work are those jobs plus a cadence, not a ten-item Code palette pasted into the wrong box.

This page will not walk first-run install. Paid plan, then select Cowork in the message box unless you are on the Unified Claude rollout where the picker is gone. The how to use Claude Cowork URL owns that path. If the Desktop tab is missing, use Claude Desktop Cowork tab missing.

Last verified: 10 October 2026 (official Anthropic docs and R3 research; no live CLI verify)

Table of contents

1. Cowork is the knowledge-work surface, not Claude Code

2. The viral slash list is Claude Code, not Cowork

3. Daily file jobs that beat organize-my-files

4. Connector chains: Gmail, Calendar, Slack, Drive

5. Document and content workflows you can run as tasks

6. Claude Cowork scheduled tasks: cloud vs laptop-open

7. Skills, plugin commands, and connectors (official map only)

8. Permissions, Allow on delete, and what not to schedule

9. Usage, batching, and Settings > Usage (not a pre-run 0)

10. FAQ

Anthropic's own film is the cleanest picture of the category: hand off a task, files and tools, finished outputs. Watch it as product identity, not as a Claude Code tutorial. Dated 12 January 2026. The viral post that mixed the two products landed later, on 24 April 2026. Do not fuse those frames.

https://www.youtube.com/watch?v=UAmKyyZ-b9E

Cowork is the knowledge-work surface, not Claude Code

Claude Cowork is the agentic workspace for non-coding knowledge work. Claude Code is the agentic workspace for software engineering. Claude Desktop is the macOS and Windows app that can host Chat, Cowork, and a Code tab. Desktop is the app. Cowork is a surface inside Claude, not a separate download.

I have watched people argue this as if it were branding. It is a workspace split. Same agent loop. Different files, tools, and slash names.

Access as of 10 October 2026: paid plans only (Pro, Max, Team, Enterprise). Desktop on all of those. Web and mobile: Pro, Max, Team; Enterprise where an admin enabled it. Chat and Cowork now share one home on desktop, web, and mobile. A staged Unified Claude rollout drops the Chat/Cowork picker on Pro and Max. Help Center line: "Claude Cowork is now just Claude." Until that lands on your account, select Cowork in the message box.

Official matrix: Chat / Claude Code / Claude Cowork

Chat drafts and answers questions in the browser, desktop, and mobile. Claude Code works in a repo from the terminal, an IDE, or the desktop Code tab. Claude Cowork does cross-app knowledge work on files and tools: full experience in Claude Desktop, with web and mobile in the mix.

Chat drafts. Claude Code works in a repo. Claude Cowork is the knowledge-work surface on files and tools.

If you wanted the comparison URL that ranks the two products against each other, that is Claude Code vs Cowork. This page stays on daily tasks.

So what? You stop teaching Code chrome as Cowork chrome. You start scheduling jobs the knowledge-work surface can actually finish.

Official product page: Cowork is built for non-coding knowledge work, research, analysis, document creation, and other multi-step tasks. It uses the same agentic approach as Claude Code. The point stands: Cowork is for the rest of your work. See claude.com/product/cowork.

Close the laptop, it keeps going. That sentence is on the product page too. It is true for cloud scheduled tasks. It is not true for local folders, browser, or computer use. We will get there.

The tweet hook and workshop are Code

The viral hook that often sits above this catalog is a Claude Code workshop teaser. Anthropic's own team. Thirty minutes. Free. The person who created Claude Code.

That last claim is directionally confirmed. Official pages call Boris Cherny Head of Claude Code, creator of Claude Code, inventor of Claude Code. The title card on the clip says Member of Technical Staff. Current webinar byline says Head of Claude Code. Use the current official title. Do not freeze the old slide.

The talk is Mastering Claude Code in 30 Minutes. Plan before edits. CLAUDE.md. Code slash. It is not a Cowork how-to. If you watch it hoping to learn /schedule in the Scheduled sidebar, you will learn a different product and then wonder why Cowork will not /compact.

Want Cowork for automation? Start from the knowledge-work surface, not from the Code workshop. Automation with Claude Cowork means recurring jobs on files and connectors, not a terminal palette.

The viral slash list is Claude Code, not Cowork

I tried this and it did not work the way the list promised. I typed /compact into a Cowork task because a saved thread said that was how you free context. Cowork Help does not list /compact as a Cowork command. The Claude Code commands reference does.

That is the gap this URL owns.

Cowork's documented / surface is small on purpose. Type / or click + to see skills and plugin commands. Type /schedule in a Cowork task, or open Scheduled in the left sidebar. Run a plugin command as /plugin-name:command. That is the official pattern. There is no ten-item Cowork slash palette that matches /compact, /clear, /plan, /doctor, /memory, /cost, /undo.

Whether the Cowork message box silently accepts those Code names on a given build is not in the sources. Do not teach them as Cowork.

Cowork's documented / surface is /schedule and /plugin-name:command. The rest of the viral list is Code or author invention.

Not following the slash split? Fair enough. Cowork / is /schedule and /plugin-name:command. Everything else in that viral ten is Code or an author name.

Walk the viral names against official homes.

/schedule is Cowork. Help Center: type it in any Cowork task, or click Scheduled. Code also has /schedule (alias /routines) for cloud routines. Confirmed on both products. This page teaches the Cowork path.

/compact is Code. It summarizes the conversation to free context. Not listed as a Cowork slash in Cowork Help.

/clear is Code. New conversation, empty context. Aliases /reset, /new. Not listed in Cowork Help.

/plan is Code. It enters plan mode from the prompt. The Cowork tab does not use Code permission modes. Cowork still creates a plan as step 1 of a task under Manual, Auto, or Skip. Teaching /plan as a Cowork slash is the mix-up. Teaching "Claude writes a plan you can approve" as Cowork Manual mode is the product.

/doctor is Code. Setup checkup: install health, settings, extensions, CLAUDE.md. Alias /checkup. It does not print connected apps, loaded skills, available commands, and current permissions as four Cowork fields. In Code those jobs split across /mcp, /skills, /permissions, and the / menu.

/memory is Code. It edits CLAUDE.md and auto memory. Cowork memory is Settings > Memory and the + menu Memory toggle. Cloud Cowork shares chat memory. Local-on-computer Cowork sessions do not use that memory.

/cost is Code. Alias of /usage. Session cost and plan limits after or during the session. Not a pre-run 3x widget. Cowork: Settings > Usage.

/undo is Code. Alias of /rewind. Checkpoint menu, up to 100 file snapshots, code and/or conversation. Not last-file-operation-only. Bash mv / rm are not tracked. Not documented as a Cowork control.

/review is Code. Alias of /code-review. It reviews a diff or PR. It is not "a custom slash command you can build," even though you can write a skill named review. Built-in Code /review is already taken as that alias.

.claude/commands/ is Code. Project path .claude/commands/. User path ~/.claude/commands/. Preferred now: .claude/skills/<name>/SKILL.md. Cowork does not read ~/.claude. Cowork loads skills, plugins, and connectors from Customize on the claude.ai account.

The paste was never the catalog; naming the product was.

The Product Management plugin is real. Made by Anthropic. Install from Customize / claude.com/plugins. Official commands: /write-spec, /roadmap-update, /stakeholder-update, /synthesize-research, /competitive-brief, /metrics-review, /brainstorm. /brainstorm is the closest official stand-in for a strategy canvas. It is not named /strategy.

/strategy chained to /business-model then /pricing then /plan-launch is not Anthropic's plugin. Those names show up in third-party marketplaces. Do not attribute that chain to Anthropic. Do not reconstruct a Cowork screen with vision, goals, target audience, and competitive positioning as official command chrome. Plugin depth lives on Claude Cowork plugins.

This will not work if you treat a viral "40 Claude Cowork commands" thread as a command reference. Items 01-10 in that genre are mostly Code names plus three invented PM commands. Items 11-40 are prompts. Count of forty is author packing, not a product fact.

Watch the Code workshop after this section if you want the real home of /plan and CLAUDE.md. Caption for yourself: Code, not Cowork.

https://www.youtube.com/watch?v=B_KAEqiC-0Q

Daily file jobs that beat organize-my-files

"Organize my files" is the anti-pattern prompt. Official get-started examples are sharper: organize Downloads by type and date, batch rename with YYYY-MM-DD, process receipts in a folder into an expense report. Using Claude Cowork to automate tasks on disk works when the instruction is a move, a rename, a convert, or an archive, not a vibe.

These are prompts. They are not slash commands. Numeric cutoffs (90 days, 1GB, 6 months unused) are your instructions, not product limits. "In seconds" is author speed. The sources do not state a timed SLA.

Permanent delete always needs Allow, in any permission mode. Local folders: Desktop open and connected.

Cowork reads and writes file types the product page names: Word (.docx, .doc), PDF, Excel (.xlsx, .xls, .xlsm), PowerPoint (.pptx, .ppt), plus text, markdown, csv, images, and more. Capability class is official. The folder names in the prompts below are examples you type.

# Prompt: batch rename (official capability class: YYYY-MM-DD)
Rename all files in /Downloads using YYYY-MM-DD_description_type.
Use the file creation date for the date. Generate the description from file content.
Show me the mapping before you rename.

# Prompt: archive stale work (90 days is your cutoff, not a product limit)
Find files in /Projects unmodified in 90 days.
Move them to /Archive/[year]/[month].
Do not touch /Projects/Active.
Show the plan, then wait.

# Prompt: receipts to expense report (official get-started example)
Process receipt images in /Receipts.
Extract vendor, amount, date, and category.
Write /Finance/expenses-[month].xlsx with category totals.
Do not delete the images

Other file jobs that earn a place in a daily-tasks catalog, still as labelled prompts:

• Duplicates across /Documents and /Desktop. Show findings before deleting. For near-duplicates, keep the most recently modified. Delete still hits Allow.

• Folder structure from /Downloads: group by project, then file type, then summarize what moved.

• Reverse-engineer completed proposals into a blank /Templates/proposal-template.docx that follows the same structure. That is a document skill job, not a Cowork "template" menu.

• Search every PDF in /Research for a topic, extract paragraphs with document and page, compile one summary. Official synthesis examples exist. Do not call it "cross-document research in seconds" as a measured fact.

• Convert .docx in /Content to .md, preserve headers and bullets, save to /Content/markdown.

• Size audit: list the 20 largest files, flag folders over 1GB, estimate space from files you have not opened in 6 months. Those numbers are prompt parameters. Official docs do not expose an "opened versus modified" API. Say so in the prompt if you care which one you mean.

Why does the vague prompt fail? Claude spends the session asking what "organized" means. A named pattern does not.

The cleaner the folder tree, the less Claude spends guessing. That is author-shaped advice that matches official grouping guidance. It is not a hidden filesystem feature.

Best Claude Cowork workflows on disk look boring: one folder, one pattern, one Allow for anything destructive. If you want the first-run folder grant, go back to the how-to. This page assumes the folder is already connected.

Connector chains: Gmail, Calendar, Slack, Drive

A connector is a link to an outside app so Claude can find information there and take actions for you. MCP (Model Context Protocol) is the open protocol underneath. Directory connectors are remote MCP. You manage them in Customize > Connectors, then toggle them per task with + > Connectors.

Cowork is only as useful as what you let it touch. The four apps this catalog teaches by name are Gmail, Google Calendar, Google Drive, and Slack. Linear exists in connector docs as another example. Microsoft 365 is a separate paid-plan feature. PowerPoint, PDF, and Excel outputs are built-in file skills plus optional M365, not a single "PowerPoint connector." Do not invent a six-logo dock.

Customize > Connectors

Open Customize, then Connectors. Discover, Connect to Claude, OAuth in the browser. Tool permissions: Always allow, Needs approval, Blocked. Cowork permission modes wrap connector writes. Team and Enterprise owners may have to enable Google Workspace first.

Cowork is only as useful as what you let it touch. Default for send is Needs approval.

Draft vs send

Gmail can search and read, draft, and send, reply, or forward. Attachment metadata only, not attachment content, on the Workspace connector. By default Claude asks for approval before send, reply, or forward. "Show me the emails before sending" matches that default. It is not a Cowork-only trick.

Team and Enterprise owners can allow send without asking. You remain responsible for messages sent as you. But is send actually gated on your account? Look at Needs approval on Gmail before you schedule anything that talks to people.

Claude Cowork automate emails, then, is a Gmail connector job with Needs approval left on unless you have a reason to change it. Email automation that drafts routine replies and flags urgent mail is a daily task. Email automation that sends while you sleep is a scheduled-task safety problem. Official safety article: do not schedule tasks that send messages on your behalf.

Connector chains worth running as labelled prompts, not as extra slash names:

• Unread Gmail: categorize urgent / needs response / FYI / can delete. Draft routine replies. Save the summary to Google Drive /Daily with today's date.

• Tomorrow's Google Calendar: research attendees and companies, write a one-page prep brief per meeting.

• Slack last 24 hours: extract action items directed at you, sort by channel and urgency.

• Drive spreadsheet plus a 5-slide PowerPoint: Cowork can create .pptx with the PowerPoint skill. Asking for a generic "doc" without naming Google creates a local file. Name Google Drive if you want it in Drive.

• One Gmail thread: decided, still open, who does what next, draft a follow-up.

• Sheet plus Slack #sales: weekly sales report saved as PDF.

• Meeting notes in a folder: one draft email per person with their items and deadlines, shown before send.

• Cross-source search: Drive, Slack, Gmail, one document organized by source.

Drive reads Docs, Sheets, Slides, PDFs, images, and Microsoft Office files. Share, move, and trash ask for approval by default. Calendar can view, create, update, and delete events.

Plugin install depth is a sibling URL. One sentence: Customize > Plugins, then invoke with /plugin-name:command. Details: Claude Cowork plugins.

Rick Hightower's connectors walkthrough is the right watch after this section. Cowork is only as useful as what you let it touch.

https://www.youtube.com/watch?v=5ESsnGSH9XQ

Document and content workflows you can run as tasks

Claude Cowork use cases that stick are document transforms you can name in one sentence. Official built-in skills: Professional Word, PowerPoint, PDF, Enhanced Excel. Official examples include transcript analysis, research synthesis, first-pass contract review, spreadsheets with working formulas, presentations from messy inputs.

Keep these as labelled prompts. 1,500-word, 2-page, 12-articles, and 8 tweets are prompt parameters, not product caps. This is not a marketing, LinkedIn, or browser-automation vertical. Those jobs get their own URLs.

• Voice note to draft: read a transcript, keep the author's voice, add structure. Word count is yours to set.

• Meeting transcript to markdown: decisions, action items (owner plus deadline), open questions, key discussion points.

• Research brief: read a folder of saved articles, synthesize, flag conflicts, recommend actions, cite sources.

• Proposal customizer: template plus client brief, same structure, tailored sections.

• Contract first-pass: plain-English summary of key terms, deadlines, auto-renewal, liability caps, anything unusual. This is not legal advice. Anthropic's product example is first-pass contract review with departures cited. Cowork is not a lawyer. If you wanted the legal cluster, that is Claude Cowork legal.

• Spreadsheet narrative: top trends, anomalies, recommended actions, numbers explained for a non-technical reader.

• Repurpose one markdown article into several social files. Treat platform counts as your brief, not a Cowork feature.

• Newsletter assembler: pick the strongest drafts from this week, teasers, intro, sign-off.

Best Claude Cowork automations in this band are the ones you can later put on a cadence: Monday brief, monthly receipts, end-of-day log. A one-shot proposal customizer can stay a task. A daily inbox processor wants /schedule. Which of these can wait until a cadence? The ones whose inputs already live in Drive, Gmail, or Calendar.

Claude Cowork automation ideas fail when they dump every vertical into one prompt. Record-workflow, dynamic-workflow, and agentic-workflow phrasing you will see in search is not a Cowork menu. Official words: sub-agent coordination, plugin Agents, Dispatch. No /sub-agent-pattern.

Worked Cowork use cases on video help after you have the prompt shapes. This is not the owned beginner how-to URL.

https://www.youtube.com/watch?v=ETBa3s2FNQo

Claude Cowork scheduled tasks: cloud vs laptop-open

You can set the dishwasher to start at two in the morning. You do not leave the tap running until then. You do not sleep on the kitchen floor to press Start. You pick a delay, you close the door, you go to bed. If the machine needs a filter you left in the garage, it will not run while you are gone.

That is a Claude Cowork scheduled task in the cloud versus a job that still needs the local machine. Cloud cadence does not magically reach a folder on a closed laptop.

But here's the thing. A cloud job that can run with the lid closed still cannot touch /Downloads on that laptop. It still cannot send Gmail unless you left Needs approval off, which you should not. The cadence picker is not a permission waiver.

Claude scheduled tasks, in Cowork, are recurring automations you create with /schedule or the Scheduled sidebar. Current Cowork scheduled tasks run remotely. The computer can be asleep. Desktop can be closed. Connectors and files saved to the Claude account keep working.

If the task requires local files or apps, it will only run locally. Local files, browser, and computer use still need Desktop open and connected. The viral line "your computer needs to be on and Claude Desktop open" is the local / computer-use / Code Desktop rule, over-applied to every Cowork schedule. That is the correction.

Why does the rumor persist? Because it used to be the local default, and Code Desktop local tasks still work that way.

Create with /schedule or Scheduled

Two official create paths.

1. In a Cowork task, type /schedule.

2. In the left sidebar, open Scheduled, then New task. Choose Create with Claude, or Set up manually.

Cadence picker: hourly, daily, weekly, weekdays, or manually. Do not treat "every Monday at 8am" as a labeled product control. That string is a prompt example. The control is the cadence list above.

HowTo, short:

1. Open Cowork (or describe the task if Unified Claude has dropped the picker).

2. Type /schedule, or click Scheduled > New task.

3. Write the job in natural language. Name the connectors. Name the destination file.

4. Pick hourly, daily, weekly, weekdays, or manually.

5. Leave send, purchase, delete, and sensitive files off the unattended list.

6. If the job needs a local folder, leave Desktop open and connected for that run, or save the work to Drive instead.

Type /schedule in a Cowork task, or open Scheduled and choose New task. Cloud jobs keep running with the laptop closed.

Cloud vs local vs Code Desktop

Four rows. Do not flatten them into "keep the laptop open" or "the laptop never matters."

Cowork cloud schedules run remotely. Local files, browser, and computer use still need Desktop open and connected.

• Cowork cloud schedule: laptop closed is OK. Runs on cadence in the cloud. Schedule Help: "Scheduled tasks run remotely, so they run on their cadence even when your computer is asleep or the Claude Desktop app is closed."

• Local files / browser / computer use: Desktop open, only while connected. Computer use also needs the computer awake. Research preview. Extra risk: no sandbox between Claude and the screen.

• Pro/Max tasks created before 6 October 2026 that run on the computer stay on the computer.

• Claude Code Desktop local tasks: app running, computer awake. Sleep skips the run. Lid-close still sleeps. Off-machine Code work is a remote routine, not this Cowork sidebar.

Claude Cowork desktop automation, then, is the local-file exception, not the default cloud story.

Items 35-40 from the viral list are prompt examples for scheduled automations, not extra slash names:

• Daily inbox processor: categorize unread Gmail, draft routine replies, flag urgent, save a Drive or account file. Needs approval on send.

• Weekly file cleanup: sort /Downloads by type. Delete older than 60 days still needs Allow. Do not schedule deletions you are not watching.

• Monday planning brief: calendar, Drive prep, outstanding Gmail, one weekly file.

• Monthly receipts: official capability class. Destination spreadsheet in Drive if you want it with the lid closed.

• Competitive scan: web search plus a dated markdown file. Cadence "every other Monday" is your instruction; the picker is weekly or manually.

• End-of-day log: files created or modified today. If /Projects is a local folder, Desktop has to be open.

Do not schedule deletions or sends you are not watching.

A live Cowork build of the first scheduled task, then a cadence walkthrough:

https://www.youtube.com/watch?v=1FCc3E5Od2U

https://www.youtube.com/watch?v=GwS-anYPTzs

Skills, plugin commands, and connectors (official map only)

The viral intro promised slash commands, scheduled tasks, sub-agent patterns, connector chains, and workflow templates. Sub-agent patterns were named and never shown. Official vocabulary fills that hole without folklore.

A skill is reusable instructions Claude loads when the task matches. Manage in Customize > Skills. Invoke automatically, from the / menu, or as /name. Upload a ZIP, or install a plugin.

A command is a named action you trigger. In Cowork it lives inside a plugin. Invoke as /plugin-name:command.

A plugin is a package of skills, connectors, commands, and agents (optionally hooks). Manage in Customize > Plugins. Install once.

A connector, or MCP, is a link to an app. Manage in Customize > Connectors. Toggle with + > Connectors.

Cowork loads skills, plugins, and connectors from Customize. It does not read ~/.claude.

# Cowork slash pattern (documented)
/schedule
/plugin-name:command

There is no /sub-agent-pattern menu. Official Cowork words: sub-agent coordination (complex work split into parallel workstreams), plugin Agents (specialists with their own context, prompt, tools, permissions; grayed out in chat), and Dispatch (a long-running agent that splits work into child Cowork or Code sessions). Dispatch is different from in-task sub-agents. Do not paste Code .claude/agents/ recipes as Cowork UI.

Where do you actually put a custom command in Cowork? Customize > Skills, or a plugin. Code built-in /review is /code-review. Memory: Cowork cloud shares chat memory (Settings > Memory, + Memory). /memory is Code.

Cowork also has Global instructions (Settings > Cowork, or Instructions for Claude in the new experience) and folder instructions on a local folder. Those are not slash commands.

Skills depth: Claude Cowork skills. Skills versus commands as a comparison job does not live here.

Permissions, Allow on delete, and what not to schedule

Cowork for automating processes still has a human on the hook. Workflow automation that deletes, sends, or spends is not "set and forget" because the cadence picker exists.

Cowork modes: Manually approve (Manual), Automatically approve (Auto), Skip all approvals (Skip). New experience: Auto and Manual, with Manual as default. Code plan mode, EnterPlanMode, and the status bar plan mode on are not the Cowork tab.

Cowork still "analyzes your request and creates a plan" as step 1. Manual waits for approval. Auto uses a classifier, still blocks unsafe actions, still asks before permanent delete. Skip turns off the automatic check. If you are still on Skip for money or mail, that is a choice. It is not a Cowork default.

What about you? Manual for anything you cannot undo. Auto for the rest. Skip only if you already trust the blast radius.

"More than 3 files" as a reason to force plan mode is author heuristic, not an official threshold. Stay on Manual for money, messages sent as you, and important files. Get started says that in those words.

Deletion always needs Allow, in any mode. You will see a permission prompt. Select Allow. A Friday cleanup prompt that says "delete anything older than 60 days" still hits that gate. If you scheduled it and closed the laptop, the Allow prompt is not a silent yes.

Cowork creates a plan as step 1. Manual waits. Code /plan is a different product. Delete still needs Allow in any mode.

Official do-not-schedule list, from the Cowork safety article: do not schedule tasks that access sensitive files, send messages on your behalf, make purchases, or take other actions that are difficult to undo. You remain responsible for content published and messages sent.

Do not schedule tasks that access sensitive files, send on your behalf, make purchases, or take hard-to-undo actions. You remain responsible.

Computer use is a separate permission per application. Desktop awake. Extra risk. Do not treat it as the same gate as a Gmail draft sitting on Needs approval.

Usage, batching, and Settings > Usage (not a pre-run /cost)

/cost is Claude Code /usage. It shows session cost, plan limits, and activity stats after or during a session. It is not a Cowork pre-run estimator. There is no official "3x normal usage" number. Check Settings > Usage.

Web, desktop, mobile, and Claude Code share one pool. No fixed message count. Agentic Cowork uses more than chat. Auto uses more than Manual because of extra safety checks. Connectors and tools are token-intensive. Turn off connectors you do not need.

Check Settings > Usage. Web, desktop, mobile, and Claude Code share one pool. Do not look for a pre-run /cost in Cowork.

Pro list price: $20 if billed monthly. $17 per month with annual ($200 billed up front). Max is monthly only: Max 5x at $100, Max 20x at $200, as 5x or 20x Pro usage per 5-hour session, plus higher output limits, early access, and priority access at high traffic times. That last line is the opposite of "evenings and weekends give higher throughput." Drop the off-peak rumor. Plan math and whether Cowork is worth a given tier live on Claude Cowork pricing 2026. Do not treat $20 as the only Pro number.

Official batching: group related work into one task instead of several. Start a new conversation for unrelated work so extra context is not carried. Tell Claude when you only need a quick answer, not a file. Each step uses tokens.

Vague "organize my files" burns clarification. A specific move-rename-delete instruction runs in one pass. Keep that. Drop "10 files versus 10 sessions," "3x," and "/plan saves tokens" as measured facts. The sources do not publish those formulas.

So what do you check instead of /cost? Settings > Usage. Same pool as Code. Same surprise if you ignore it.

Claude automations that share this pool with your Code sessions will surprise you once. Settings > Usage is the screen. Not a slash you type before the task.

FAQ

Can Claude Cowork automate tasks?

Yes. Cowork runs multi-step knowledge-work jobs on files, connectors, and scheduled cadences. Create a recurring job with /schedule or Scheduled > New task. Cloud tasks keep running with the laptop closed. Local files, browser, and computer use still need Desktop open and connected. Viral slash names like /compact and /plan are Claude Code, not the Cowork automation surface.

Does my computer have to stay on for Claude Cowork scheduled tasks?

No, not for current Cowork cloud schedules. Help Center: they run remotely even if the computer is asleep or Claude Desktop is closed. Yes, if the task needs local files, browser, computer use, or a pre-6 October 2026 local Pro/Max task. Claude Code Desktop local tasks also need the app running and the computer awake; sleep skips the run.

Do slash commands work inside Claude Cowork?

The documented Cowork / surface is /schedule and /plugin-name:command, plus skills via /. /compact, /clear, /plan, /doctor, /memory, /cost, and /undo are Claude Code commands. Whether Cowork silently accepts those Code names is not in the sources. Do not teach them as Cowork.

Will Cowork send the email or only draft it?

Both, with a default gate. Gmail can draft, and can send, reply, or forward. By default Claude asks for approval before each send, reply, or forward. "Show me the emails before sending" is that default, not a hidden Cowork trick. You remain responsible for messages sent as you. Do not schedule unattended sends.

Is this Claude Cowork or Claude Code?

This catalog is Claude Cowork: non-coding knowledge work in Desktop, web, and mobile. The viral workshop hook is Claude Code. Same agentic architecture, different workspace. Desktop is the app that can host both. Select Cowork in the message box unless Unified Claude has dropped the picker.

How do I add a custom command in Cowork?

Customize > Skills (upload a ZIP) or Customize > Plugins, then invoke /plugin-name:command. Cowork does not read .claude/commands/ or ~/.claude. That path is Claude Code. Code already ships /review as /code-review; a custom review in Cowork is a skill or a plugin command, not that Code alias.

Which apps can Cowork connect?

Official directory examples include Gmail, Google Calendar, Google Drive, and Slack, plus other MCP connectors. Excel, PowerPoint, and PDF are built-in file skills; Cowork can create those files without a Microsoft 365 connector. Microsoft 365 is a separate paid-plan feature. Manage apps in Customize > Connectors. Permissions: Always allow, Needs approval, Blocked.

What does /plan show in Cowork?

/plan is a Claude Code command that enters plan mode: a written plan, no source edits until you approve. The Cowork tab does not use Code permission modes. Cowork still creates a plan as step 1 of a task. Manual waits. Auto and Skip are Cowork modes, not Code /plan.

What is a sub-agent in Cowork?

Official: Claude can split complex work into parallel sub-agents. Plugins can bundle Agents (specialists with their own context and tools) that run in Cowork and Claude Code, not in chat. Dispatch is a long-running split into child sessions, different from in-task sub-agents. There is no /sub-agent-pattern menu and no official source-style pattern roster.

The dishwasher will still need the filter from the garage. Cloud cadence will not invent a local folder. Code's slash palette will keep looking like a Cowork cheat sheet in other people's threads. I would rather you schedule the jobs that have an official home than wait for /compact to become one.

Tonight, pick one recurring job that lives in Gmail, Calendar, or Drive. Type /schedule or open Scheduled > New task. Leave send and delete off the unattended list. Stay on Manual.

Tomorrow, try the same job against a local /Downloads folder with the lid closed. If it does not run, that is the architecture, not a broken cadence picker.

If you want the next catalog in your inbox, that is what the newsletter is for.

Until then...

• Sage

PS. Official Product Management plugin commands are /write-spec, /roadmap-update, /stakeholder-update, /synthesize-research, /competitive-brief, /metrics-review, and /brainstorm. I still catch my fingers reaching for /strategy. The plugin page never had that name.

Related Reading

• How to use Claude Cowork: first-run setup, Desktop, message-box picker. This URL stays on the daily-tasks catalog.

• Claude Cowork plugins: marketplace, /plugin-name:command, plugin Agents.

• Claude Cowork skills: Customize > Skills, built-in Word / PowerPoint / Excel / PDF.

• Claude Cowork pricing 2026: Pro $20 monthly / $17 annual, Max 5x and 20x, shared usage pool.

• Claude Code vs Cowork: the product split, not this inventory.

• Schedule recurring tasks in Claude Cowork: official cloud vs local rule.

• Claude Cowork product page: Chat vs Code vs Cowork, file types, close-the-laptop line.