Claude Cowork reviews: an honest look at what's great and what's rough
Most Claude Cowork reviews are either breathless or dismissive. This is a balanced synthesis of what practitioners consistently report — the genuine strengths and the equally genuine rough edges — so you can decide whether it fits your team.
What Cowork does brilliantly
The praise is consistent: for multi-step knowledge work, Cowork delivers finished outputs that used to take a person an afternoon. Non-developers get real leverage without a terminal, the plan-act-check loop is genuinely agentic rather than a glorified chatbot, and connectors plus scheduled tasks turn one-off wins into standing automations. Anthropic's own May 2026 data — a third of sessions in business-process operations — matches what reviewers say it's best at.
Where it frustrates
The honest criticisms are just as consistent, and worth knowing before you buy. Reviewers repeatedly flag the lack of cross-session memory, the speed at which Cowork burns through usage, and desktop-only limitations on some features. On the desktop app, standing up the local sandbox can be fiddly — it needs local virtualisation — and Windows Home users in particular report friction. It's powerful, but it's still maturing, and some tasks need a second attempt.
Who it's actually for
The fairest verdict: Cowork is for teams whose bottleneck is repetitive knowledge work and who are willing to invest a little in setup and governance. If you want a hands-off magic button, you'll be frustrated; if you'll spend an hour on connectors, permission modes and a couple of Skills, the payback is real. For engineering-heavy work, use Claude Code instead. If you'd rather not navigate the setup and caveats alone, that's exactly what our training and consulting are for.
Frequently asked questions
What are Claude Cowork's biggest limitations?
No cross-session memory by default, no session sharing, heavier usage consumption than chat, some desktop-only features, and local tasks that stop if the desktop app closes (scheduled and remote tasks don't). The local sandbox can also be fiddly to set up. It's powerful but still maturing.
Is Claude Cowork worth it?
For teams whose bottleneck is repetitive, multi-step knowledge work — reports, decks, data clean-up, file wrangling — yes, provided you invest a little in setup and governance. For hands-off simplicity or heavy engineering work, it's a weaker fit (use Claude Code for the latter).
Want a hand putting this into practice?
Our hands-on Claude Cowork training takes your team from the basics to a repeatable practice, using your own data.