Writing with Cowork
Writing with Cowork
When Cowork Should Write Nothing
Sometimes the right move is for Cowork to push back, not draft.
You paste a tense email thread into Cowork and say "draft a reply." Three seconds later you have a calm, well-structured three-paragraph response. You read it, nod, and send it.
The draft was good. Sending anything was the mistake. The thread had already resolved itself two messages up; your reply reopens a closed decision, pulls four people back into a settled question, and makes you look like you weren't reading. Now there are six more emails.
Cowork did exactly what you asked. You asked it to draft, so it drafted. What it didn't do (what it almost never does on its own) is stop and say "you probably shouldn't send anything here."
That gap is the whole article. The fix isn't a better draft. It's a different question, asked first.
#Why Cowork won't volunteer "no"
Cowork is built to be honest. Anthropic's published constitution for Claude is explicit that it should "point out things people might not want to hear" and be "diplomatically honest rather than dishonestly diplomatic" instead of offering empty validation. The disposition to disagree is real and it is designed in.