Claude Cowork and chat are merging: how to hand over a whole task

What changed on 16 September 2026?

Anthropic announced on 16 September 2026 that Cowork and chat were becoming one Claude experience. For migrated accounts, a conversation can move from discussing a task to working on it without choosing a separate Cowork mode.

The change is about how you hand work over. Instead of treating every step as a new question, you can describe the outcome and continue the same conversation through the working process. It does not remove the need to define the job, grant appropriate access or review the result.

Who has the merged experience?

Anthropic’s announcement describes a gradual rollout to Pro and Max across web, desktop and mobile. The dedicated help article says that if you still see separate Chat and Cowork controls, your account has not yet migrated. Do not assume a rollout announcement means every account has changed.

The tools a task can use still depend on your account, device, connections and permissions. Start with what is available to you. A request to use a file is not proof that Claude can access it; ask it to identify the sources it is actually using.

Worked example: prepare a weekly operations pack

Consider a fictional team that needs a Friday update. Inputs are a small job-status file, meeting notes and an approved report template. Outputs are a one-page management brief and a short set of slides for Monday’s meeting.

Give the brief a clear finish: what changed, what is delayed and which decisions need the manager. The slides should follow the checked brief, not introduce a second set of claims. Keep the exercise small enough to inspect every important fact.

This is a suggested workflow. We are not claiming that a particular account completed it or that it saves a measured amount of time.

Hand over the task in stages

1. Supply the approved files or authorised connections, then ask Claude to list what it can access.
2. Describe the audience, required outputs and facts that must be preserved. State which actions require your review.
3. Ask for a short plan and any missing inputs before it starts producing the pack.
4. Have it extract the key figures, deadlines and decisions with source references. Check these before turning them into a narrative.
5. Request the management brief, correct any issues, then ask for slides based on the approved brief.
6. Open each output and verify facts, labels and completeness. Share it yourself once the review is complete.

Copy this original task brief

Prepare a weekly operations pack from [approved job-status file], [meeting notes] and [report template]. Audience: the operations manager. First list the sources you can actually access and propose a short plan. Extract completed work, delays and decisions needed, with source locations. Do not invent owners or deadlines; mark missing details. Produce a one-page brief in Australian English. Wait for my factual review before creating five meeting slides from that brief. Do not email, publish or modify the source files. If a required tool is unavailable, explain the limit and stop that step.

Keep the handover bounded

A whole-task brief should specify what Claude may do and where you want to review the work. “Prepare the pack” is narrower than “sort out operations”. The latter could imply contacting people, changing records or making decisions you did not intend to delegate.

For the fictional pack, a missing delivery date should become a question for the manager. It should not become a guessed commitment. A task can be complete as a draft while still containing clearly marked questions.

Check the actual files as well as the conversation summary. If a slide contains a chart, compare its labels and totals with the approved figures. If an output is missing, ask for that item specifically instead of assuming the task summary means it exists.

Adopt the new flow with one repeatable job

Choose a recurring job with known inputs and an obvious reviewer. Record the brief that worked and the checks that caught mistakes. Expand the scope only after the team understands the permissions and review points.

If your account still has the old controls, follow the current official help page for that experience. Avoid redesigning the team’s process around a feature you have not received. For practical support, use the workshop enquiry form on the 27 AI homepage.

Common questions

Why do I still see a Cowork mode?

Anthropic describes a gradual migration. Its help page says separate Chat and Cowork controls mean your account has not yet moved to the merged experience.

Does the merger mean Claude can access everything on my computer?

No such assumption is justified. Available tools, connected sources and permissions determine what it can use. Verify the sources it actually accessed.

Can I ask for several outputs in one task?

You can describe several required outputs, then check the available tools and review the results. Use a clear sequence so later outputs rely on facts you have already checked.