The Difference Between a Reply and an Artifact

You ask Cowork to pull together a status view of your open projects. It reads your tracker, your inbox, your calendar, and writes back a clean summary. Owners, due dates, what's blocked. It's genuinely good. You skim it, feel oriented, and move on.

Monday, you want that view again. You scroll up to find it. The numbers are four days stale now, so you can't trust them. You retype the request. Cowork rebuilds the whole thing from scratch (same shape, slightly different wording) and you skim it again.

You've done this six times. Six identical asks, six disposable answers, none of which got better and none of which is where you left it.

The tool wasn't the problem. You kept asking for a reply when what you wanted was an artifact.

#A reply is a snapshot; an artifact is a place

A reply is a paragraph in a conversation. It's true for the instant it was written, then it freezes and drifts toward the top of the thread. To use it again you find it, re-read it, and hope nothing's changed; or you ask again and get a fresh one that doesn't remember the last.