Howardism

Sources#

Anthropic's Boris Cherny: Why Coding Is Solved, and What Comes Next
How Anthropic's product team moves faster than anyone else | Cat Wu (Head of Product, Claude Code)

Summary#

Anthropic's knowledge-work agent product, sibling to Claude Code. Where Claude Code targets work whose output is code, Cowork targets work whose output is non-code: slide decks, inbox triage, customer dossiers, launch docs, meeting prep. Co-led on product by Cat Wu.

Positioning (Cat Wu's framing)#

Claude Code (CLI) — one-off coding tasks; CLI gets new features first; "the most powerful of all the tools"
Claude desktop / Claude Code in IDE — front-end work where you want a preview pane; better for non-technical users uncomfortable in terminal
Claude Code mobile / web — kicking off tasks AFK; "missing product" before it shipped — people would tether laptops to phones outdoors
Cowork — anything where the output isn't code

How Cat Wu uses it#

Connects Google Calendar, Slack, Gmail, Google Drive — "the more context, the better." Example workflow: feeds a draft outline + relevant Twitter / launch-room links into Cowork at night, returns to a 20-page polished slide deck the next morning, iterates with one round of feedback. The Anthropic design system is loaded so the deck looks like a designer made it.

Why people use it (per Cat Wu)#

The "Applied AI" team — second-largest internal token spender after engineering — uses Cowork for:

Customer-meeting prep ("dossier" workflow: yesterday's questions, action items, ETA research)
Inbox-zero / Slack-zero triage
Launch plans, internal docs, customer-tailored decks pulled from Salesforce + Gong + Slack

Where it ties into the larger Anthropic roadmap#

Boris Cherny cites Cowork as the venue for general-purpose MCP and computer use integration — same MCP connectors as Claude AI, plus Anthropic's lead on computer use for software lacking MCPs ("quite good" on Opus 4.7).
"We have no more manually written code anywhere at the company" — Cowork covers the non-code half of that claim (SQL, decks, ops docs all model-generated).

Key quotes#

(Cat Wu) "If I'm building something where the output is code, I'll use Claude Code or desktop or Claude Code on mobile. And if the output is anything that's not code, I'll use Cowork for it."
(Boris Cherny) "Claude design I think is a really good example. It's pretty good today. It's going to get a lot [better]." (Referring to Cowork-class products in his vision answer.)

Connections#

Claude Code — sibling product
Cat Wu — Head of Product
Boris Cherny — names it as an area of investment
Anthropic — vendor
Engineer PM Convergence — Cowork plus Claude Code is what makes "everyone codes" + "everyone runs ops via agents" possible across non-engineering functions
AI Employee Framing — Cowork's deployment surface (Gmail, Slack, Calendar, Drive) is where "AI as employee" framing decisions get made; HBR research suggests how these get framed changes accountability and review quality
Human-AI Accountability Redesign — non-code agent output (decks, dossiers, inbox triage) lacks compiler/test verification, so accountability redesign matters more, not less, than for Claude Code
Agentic Misalignment (AM) — Cowork-style deployments (long-context, tool-using, weak per-action oversight) are exactly the AM eval setting

Open questions#

How does Cowork's harness compare to Claude Code's? Both surface skills, MCP, sub-agents — but the failure modes for non-code output differ (no test suite, no compiler, no diff to review).
What's the eval discipline for Cowork-class outputs? Cat Wu says memory benefits a lot from evals; unclear how slide-deck quality is measured.