Anthropic has merged Claude Chat and Cowork into a single product experience. According to the company’s September 16, 2026 announcement, users will no longer need to decide whether a request belongs in a normal conversation or a separate Cowork task. Claude will make that distinction itself.
A short question can still receive a direct answer. A more involved request might turn into a longer-running task in which Claude searches for information, works with files, uses connected services, or produces a finished document. All of that now starts from the same prompt box.
This isn’t a new Claude model, and Anthropic hasn’t attached new benchmark results to the release. It is a significant product change, however. The merger turns the boundary between chatbot and AI agent into an implementation detail that Claude manages on the user’s behalf.
Claude Now Decides How the Work Gets Done
Cowork was originally positioned as the place for “bigger work.” Users could give Claude a more open-ended assignment, allow it to operate across files and tools, and return to the task later. Chat remained the familiar option for questions, writing help, analysis, and shorter interactions.
Anthropic had already begun narrowing that divide. A July 2026 Cowork update brought chat and Cowork into a shared home on web and desktop, while adding cloud-based tasks that could be checked from mobile. The new release removes the remaining mode decision rather than merely placing both options on the same screen.
Under the merged system, Claude decides how much work a prompt requires. It may answer immediately, ask follow-up questions, build an execution plan, or continue operating on the task while the user does something else. Anthropic says people can still steer the process, correct its direction, or take over before the result is finalized.
The announcement does not explain the routing logic behind those decisions. That will be an important part of the experience. Claude needs to recognize when a prompt warrants autonomous work without turning every moderately complicated question into a slow, token-intensive project.
One Conversation Keeps More of the Relevant Context
The strongest part of the merger may be context continuity rather than autonomous execution.
Claude’s migration guide says existing tasks, projects, artifacts, connectors, and skills will transfer into the unified interface. Chats and tasks will appear together in Recents, while memory, preferences, project context, and global instructions can apply across both kinds of work.
