Source: raw/The_Claude_Cowork_Feature_I_ve_Been_Begging_For_Finally_Arrived.md, raw/7_Powerful_Claude_COWORK_Tips_I_Wish_I_d_Known_from_Day_One.md, raw/Claude_Chat_vs_Cowork_Explained_when_to_use_each_one.md, raw/5_Claude_Cowork_Tricks_I_Wish_I_Knew_Day_1.md, raw/Everything_You_Know_About_Claude_Cowork_Is_OUTDATED.md (auto-caption transcripts, fetched 2026-10-27)
Creator: Eliot Prince Platform: YouTube Videos:
- “The Claude Cowork Feature I’ve Been Begging For Finally Arrived” — https://www.youtube.com/watch?v=bA8W7w5hlKI — 9:16 — published 2026-02-27
- “7 Powerful Claude COWORK Tips I Wish I’d Known from Day One” — https://www.youtube.com/watch?v=SzOI5zU0pLw — 15:37 — published 2026-03-06
- “Claude Chat vs Cowork Explained (when to use each one)” — https://www.youtube.com/watch?v=56pN4nQmnk8 — 15:39 — published 2026-04-20
- “5 Claude Cowork Tricks I Wish I Knew Day 1” — https://www.youtube.com/watch?v=AseH0yIySN4 — 21:25 — published 2026-09-28
- “Everything You Know About Claude Cowork Is OUTDATED” — https://www.youtube.com/watch?v=VX2G7De8Oj8 — 18:34 — published 2026-10-27
Eliot Prince, a UK AI coach who runs a “Half Day Thursdays” community and the AI Recipe Vault, published a steady run of Cowork tutorials through 2026. This article pulls the practical setup moves out of five of them and orders them by date, because Cowork changed underneath the advice: tips from February to April assume a desktop-only, separate Cowork mode; the September and October videos describe the merged product. Each section says which state it describes. The October product state itself is recorded in Claude Cowork (Product Overview); projects mechanics are in Claude Projects.
Key Takeaways
- Give Cowork a sandbox folder first. Eliot keeps a folder only Cowork works in and copies files into it, so originals stay untouched. He cites a user who pointed Cowork at the top of their file system and had files renamed that they wanted left alone. (March 2026)
- A
CLAUDE.mdin a folder is a standing instruction for every task run there. The “instructions” panel in a Cowork task writes aCLAUDE.mdinto that folder. Write the folder’s purpose and rules once, then a one-word prompt (“go”) runs the routine. (March 2026) - Use
CLAUDE.mdto make a synced cloud folder read-only. Point Cowork at a Google Drive for desktop folder, then add an instruction that it must never edit files there and must copy anything it changes into a new deliverables folder. (March 2026) /usageand “explain usage” show where tokens go./usageshows the 5-hour and weekly limit position, per-model tokens and an equivalent API cost; “explain usage” gives a plain-language breakdown. In Eliot’s session, custom instructions and the tool list were the largest share, because Claude rereads them at every step (22 times in his example). Turning off unused connectors is the fix he draws. (September 2026)- “Turn into skill” captures a process once it works. After a task produces the output you want, the button at the top of the task drops a “Turn this task into a skill” prompt; add a sentence on what the skill is for and when to call it. (September 2026)
- “Spin up a team of sub-agents” parallelises research. Adding that phrase made Cowork run one agent per competitor (it reached 12) and compile one report. It also used up Eliot’s VidIQ connector credits, so parallel agents multiply connector costs as well as tokens. (September 2026)
- Connect the phone so blocked tasks reach you. With the desktop app and phone app on one account, Cowork pings the phone when a long or scheduled task needs a permission or an answer, and you can reply by voice note. (September 2026)
- Since October you rarely pick chat or Cowork yourself. On Pro and Max the toggle disappears and Claude decides; on Team it depends on an admin setting. Eliot’s April “single-lane road vs five-lane highway” model now matters mainly to Team accounts kept on classic mode. (October 2026)
Scheduled tasks and the Customize tab (February 2026, historical)
The 2026-02-27 video covers the day scheduled tasks arrived in Cowork. Historical: at launch, tasks ran only while the computer was on and the desktop app open. Cloud scheduled tasks that need no device arrived later (July 2026; see the feature timeline).
- Where: open the sidebar, choose Scheduled, then New task. Fields: prompt, model, working folder, frequency (manual, hourly, daily, weekly) and time. Each task has an on/off switch, so you can pause everything before a holiday.
- Worked example: “scrape the most recent YouTube videos posted by all my YouTube competitors and put the results in a spreadsheet”, weekly, saved into a research folder. Eliot reports the run took 3-4 minutes and returned channel, subscribers, title, views, like rate and comments.
- Customize tab: skills had lived under Settings → Capabilities. A Customize entry in the left sidebar now holds integrations, skills (including creating new ones) and plugins in one place.
- Video editing works on first drafts. Pointed at a folder holding an intro clip and a main clip, Cowork stitched them and cut silences without being told which tools to use. Eliot reports 15-20 minutes for the job and calls the output “not production perfect”, fit for a rough cut.
Safe setup and context layers (March 2026)
Written when Cowork was desktop-only and worked only on local folders.
- Sandbox. Create one Cowork-only folder and copy material into it. His first task for anyone is renaming and filing screenshots inside a sandbox copy of the screenshots folder.
- Folder
CLAUDE.md. His screenshots example: “This is the screenshots folder. Our aim is to keep it organized at all times.” Rules follow: name each screenshot by its content, file it into a matching folder, create a folder when none fits, move duplicates to a to-delete folder, and do all of this “when asked to organize or just go”. Cowork reads the file before acting, so typing “go” starts the routine.CLAUDE.mdfiles work at every folder level. - Bring a chat project into a task. From a chat project, “start a task in Cowork”; or in a Cowork task, add files → include project. The project’s instructions and files join the folder context. (The June import flow and the October merged projects are in Claude Projects.)
- Connectors. + → Connectors → Manage → Browse. His example connected apollo.io and asked for accountancy practice owners in south-west England; Cowork called Apollo’s people search and wrote names, titles, companies, domains and industries to a spreadsheet it can update in place later.
- Cloud files without downloading. Google Drive for desktop (and the equivalents from other providers) streams cloud folders into the file system, so Cowork can work on them and changes sync back. Pair with the read-only
CLAUDE.mdabove for shared team drives. - Model choice on scheduled tasks. He picks Sonnet for a daily Slack brief rather than Opus 4.6, to save usage. Opus 4.6 is several generations old now; Opus 5.5 is current. The split still holds: the cheaper model for routine briefs, the top model for analysis.
Chat vs Cowork, as it stood in April 2026 (historical)
The 2026-04-20 video gives the pre-merge mental model. Since the September merge, Pro and Max users no longer choose (see One Claude); the model still applies to Team accounts whose admin keeps classic chat and Cowork.
- Chat ran in the cloud: one prompt, one response, a single loop. It could analyse and create files, but editing a file meant generating a new one.
- Cowork was Claude Code under a chat interface, running on local files: it edited files in place, ran scripts, used several connectors and spawned sub-agents in one run.
- The side-by-side test. The same prompt in both: scrape 100 UK office job listings from LinkedIn, find mentions of AI tools, and build an interactive HTML dashboard. Chat stopped with “Claude reached its tool use limit for this turn” and needed repeated “continue” prompts. Cowork returned the spreadsheet, analysis and dashboard in one run; Eliot reports the headline was that 7% of listings mentioned AI.
- His analogy. Chat is one car on a single-lane road that needs directions at every turn; Cowork is a five-lane highway that runs several cars at once and finds its own route.
Five tricks on the merged product (September 2026)
Recorded on 2026-09-28 with Opus 5.5. Eliot notes the chat/Cowork toggle was already disappearing on his account; with no toggle, Cowork is selected automatically.
/setup(Set up Claude). A guided setup that asks what work you do and suggests plugins and skills to match. For marketing it offered Claude’s built-in marketing plugin (8 skills, including brand review, campaign plan, competitive brief and content creation), a community “SEO GSC wizard” (keyword cannibalisation, content decay, indexing, quick wins, site audit) and an ad-intelligence plugin. A plugin is a bundle of skills; call one by slash command or in plain words (“run me a competitive brief”)./usage, then “explain usage”./usageloads instantly: progress through the 5-hour window, weekly limit, tokens by model and the equivalent API cost ($2.21 in his session, not actually billed on a subscription), plus a breakdown by contributor (the competitive-brief skill was 56% of that session,/setup40%). “Explain usage” takes a couple of minutes and found that his custom instructions and tool list dominated. His practical points: prune connectors you don’t use, and use the per-task cost figure when pricing client work.- Turn into skill. His example was a landing-page copy session built on Eugene Schwartz’s Breakthrough Advertising. He clicked Turn into skill and added: what expertise to capture, when he’d call it, and “let me know any other information or any questions you have”. The result, “Schwartz copy chief”, has write and teardown modes. He reports conversion-rate uplifts on his sales page; that is his claim, not a measured result here.
- Sub-agent teams. Ask for “a team of sub-agents to research each competitor individually and then come back and compile the report”. You can click into each agent to see what it is doing. Eliot describes Cowork as Claude Code under the hood, so Claude Code Subagents is the closest documented reference for how these agents work.
- Phone pings. His favourite scheduled task is a morning Gmail triage that, he says, took 39 threads to the 10 that matter. Another scheduled agent that manages one of his websites interviews him by phone questionnaire before outlining an article, so it can quote his real views instead of inventing them.
The October 2026 state in brief
From the 2026-10-27 video; full detail and caveats are in Claude Cowork.
- No mode toggle on Pro and Max. Team admins control it under Organization settings → Capabilities → “Chat and Cowork unified”. Eliot recommends turning it on.
- Cowork runs on the web and on the phone. Settings → Cowork → “Cowork in the cloud”. While the desktop app runs on your computer, the web and phone apps can still use that computer’s files and apps.
- Projects are one kind with a local folder and uploaded context, and scheduled tasks can be attached to a project.
- Memory spans the whole account, Cowork included. Turn on “search and reference chats” and “generate memory from chats” in settings.
- A built-in browser in the desktop app, and Claude Docs / Sheets / Slides for editing inside Claude.
Try It
- Make a sandbox and a folder rule. Create
~/Cowork/, copy your screenshots folder into it, add aCLAUDE.mdwith Eliot’s organise-on-”go” rules, and typego. Re-run it next week to see the rule hold. - Audit usage after your next long task. Run
/usage, then “explain usage”. If instructions and tools are the largest share, disconnect the connectors you haven’t used this month and compare the next run. - Capture one process. The next time a back-and-forth finally produces the right output, click Turn into skill, describe when you’d call it, and save it. Test it on a fresh input the same day.
- Run one parallel research job. Pick 5-10 competitors and ask Cowork to “spin up a team of sub-agents” for one each. Check connector credit balances (VidIQ, Apify and similar) before and after.
- Pair the phone app before you schedule anything that might need approval, so a blocked task reaches you instead of waiting.
- Team admins: check Organization settings → Capabilities → “Chat and Cowork unified” and decide deliberately rather than leaving members on whatever the default is.
Open Questions
- Which
/usagefeatures are Cowork-specific? Eliot shows/usageand “explain usage” inside Cowork; the wiki’s/usagecoverage is from Claude Code releases. Whether “explain usage” is a built-in command or a skill on his account is not stated. - Is
/setupavailable on every plan? The video shows it on his account only; the plugin suggestions depend on what is already installed. - Sub-agent model choice. The September video doesn’t say which model the 12 agents ran on. The Cowork article records NLW’s warning that Fable 5.1 sub-agents can consume a large share of a usage cap.
- Video editing tools. The February video doesn’t say what Cowork used to cut the video (ffmpeg or another tool). Check before relying on it.
Related
- Claude Cowork (Product Overview) — feature timeline and the October 2026 state
- Claude Projects — Cowork project creation modes and the merged projects area
- Getting Started with Claude Cowork — Eliot’s earlier Notion onboarding recipe
- Top 5 Cowork Tips from Day One (Jeff) — another creator’s beginner rules, for comparison
- CLAUDE.md File Primer — the same instruction-file mechanism in Claude Code
- Claude Code Subagents — the closest documented reference for Cowork sub-agent teams
- Cowork Plugins — the plugin layer
/setuprecommends from - Data-Led PR Studies with Claude Cowork — Eliot’s largest worked Cowork project