Claude Cowork use cases: what people build, and how to put it online

TL;DR. Claude Cowork is Anthropic's agent for knowledge work: give it a goal, point it at folders and connected tools, and it plans and carries out multi-step tasks, handing back spreadsheets, documents, decks and small working tools. As of August 2026 it runs in the Claude desktop app on macOS and Windows, on the web and on mobile, on paid plans. The Claude Cowork use cases and examples below are grouped by what comes out the other end. When that is a live app or website, the Hatchable connector lets Cowork deploy it to a real URL with a database and sign-in.

What Claude Cowork is, as of August 2026

Anthropic released Cowork as a research preview in January 2026, first in the macOS app for Max subscribers, and has widened it since. Per Anthropic's help center it is now in Claude Desktop on macOS and Windows, on claude.ai for Pro, Max and Team (Enterprise where an admin enables it), on iOS and Android, and as a Chrome side panel. Anthropic describes it as bringing "agentic capabilities to knowledge work beyond coding": you describe an outcome, Claude makes a plan, splits the work into subtasks, reads and writes files in the folders you grant, opens a browser when a task needs one, and comes back with finished work rather than suggestions. Tasks can run in Anthropic's cloud (in beta) and be scheduled on a cadence, so they do not need your laptop awake. It supports connectors and plugins, and it is a paid-plan feature.

A few limits Anthropic lists as of this writing: sessions cannot be shared with other people, what Claude remembers about you in chat does not yet carry into Cowork, and some features are desktop-only.

Product details are drawn from Anthropic's public help center and product pages as of August 2026. Cowork is changing quickly, so check Anthropic for current specifics.

Claude Cowork connectors, plugins and MCP

Connectors are how Cowork reaches anything outside your folders, and under the hood a connector is an MCP server. Anthropic's help center says custom connectors over remote MCP are available on Claude, Cowork and Claude Desktop, that a connector added once is available the next time you sign in on another surface, and that inside a Cowork session you toggle connectors on from the "+" menu in the chat box. Plugins go one step further and bundle skills, connectors and sub-agents for a job (Anthropic's library covers sales, finance, legal, marketing, HR, engineering, design, operations and data analysis), and are available on paid plans.

Hatchable is a listed connector in Claude's connector directory, and the setup page at /howto/connect-claude notes that connectors are shared across Claude surfaces, so adding it for Claude sets it up for Cowork and Claude Code as well. Whether a given connector shows up in your Cowork depends on your plan and settings: on Team and Enterprise an owner or admin may need to enable it, and a free account (which cannot run Cowork anyway, as of August 2026) is limited to one custom connector.

Claude Cowork use cases and examples, grouped by what comes out

Documents and spreadsheets

1. The monthly report. A folder of exports from three systems, a request to reconcile them and explain the differences, and an Excel workbook with working formulas plus a short summary document come back. This is the centre of what Cowork is for, and the output is a file.

2. A deck from notes. A folder of meeting notes and a brief become a PowerPoint with speaker notes, in your template if you give it one. Still a file.

Research

3. A vendor or competitor brief. Cowork reads the PDFs in a folder, opens a browser for what is missing, and writes a comparison table with a recommendation. Output: a document.

4. Bulk review. Twenty contracts, applications or invoices checked against a checklist, with findings in a spreadsheet and a flag on anything unusual. Output: a spreadsheet.

Ops dashboards

5. The weekly KPI dashboard. The first version is a document with charts, or an HTML page Cowork writes from the CSVs. Then someone asks for it at a URL that updates. With Hatchable connected, Cowork can create a project with a metrics table, a route that serves the latest numbers, sign-in so only the team sees it, and a scheduled job that refreshes the figures. Output: a live app.

6. A scheduled digest. Cowork's own scheduled tasks can run the report each Monday. If the digest should go out as email from the dashboard itself, a project on Hatchable can send it on a cron schedule from its own address. Output: a file, or email from a live app.

Small internal tools

7. A request tracker. The moment a form has to be filled in by people who are not at your laptop, it has to be online. Cowork with the Hatchable connector builds a requests table, a public submit form, a member-only list with status changes, and sign-in by email code, then deploys. Output: a live app.

8. An inventory or asset list. A spreadsheet is right until two people need to edit it at once. A small app with a table, a search box and sign-in replaces it, and the project's database keeps a real history. Output: a live app.

A simple website

9. A landing or event page. Cowork writes the HTML and CSS in a folder. Zip it and import it at /deploy, or ask Cowork to deploy it through the connector. Output: a live website at your-site.hatchable.site.

10. A team directory or FAQ site. Private by default, so only people you invite can open it, with sign-in handled by the platform rather than by anything Cowork has to build. Output: a live, private website.

From a Cowork-made tool to a live app

1. Add the Hatchable connector

   Add it from Claude's connectors page (the button at /howto/connect-claude pre-fills the URL https://hatchable.com/mcp). Click Connect, approve the OAuth tab, and a free account is created. No API key.

2. Turn it on in the Cowork session

   Open the "+" menu in the chat box and toggle Hatchable on. If it is not listed, check your plan and, on Team or Enterprise, ask an admin to enable it.

3. Ask for the live version

   Something like: "Put this request tracker online on Hatchable. Create a project, a requests table, a public submit form, a member-only list, sign-in for my team, deploy, and give me the URL."

4. Publish, or keep it private

   Projects start private. "Publish to the web" makes one public. The free plan is unlimited private projects and one published app, no card. Builder is $12 a month for unlimited published apps and custom domains (see pricing).

One boundary worth knowing before you ask: Hatchable runs web apps written in HTML, JavaScript and SQL, with a Postgres database, sign-in, email, cron and AI calls included. It is not a Python or Docker host and does not run long-running processes, so a Cowork task that produced a Python script stays a Cowork task. The web app it feeds can live on Hatchable.