Claude Chat and Cowork Merge: What Changes and Who Gets Access?
Claude is bringing chat and Cowork together in a single conversation. You can ask a question, then hand over research, file analysis or document creation without selecting a different mode. Availability and rollout controls depend on your plan and, for workplace accounts, your organization’s settings.
How are Claude chat and Cowork coming together?
Previously, you chose between chat for conversational help and Cowork for tasks involving multiple steps. In unified Claude, every conversation starts in the same place. When the request requires code execution or file work, Claude uses the relevant tools and cloud environment within that conversation. Anthropic announced the integration on September 16, 2026.
For example, you can ask about product documents and then request a comparison spreadsheet and a report in the same conversation. You spend less effort reopening the work elsewhere and explaining the context again. A quick question can still receive a quick answer; unification does not mean every exchange becomes a long autonomous task.
This changes the workflow. Choosing a model and determining which tools your account can use remain separate questions. The model picker and Code tab stay in place, according to the official unified Claude guide.
What can you do in the unified experience?
You can move from discussing a result to producing it. Claude can work through source material, perform calculations and organization, and return editable files. The actual scope depends on plan availability, connected services and access you grant.
- Research and analysis: investigate web sources or compare themes and differences across supplied documents.
- File creation: request documents, spreadsheets with formulas, or presentations you can open in PowerPoint. Check the formulas and sources before relying on the output.
- Connected apps: retrieve relevant material from services you have connected, such as Google Drive or Microsoft 365. Review connections under Customize > Connectors.
- Recurring work: request scheduled summaries and reports. In an organization, the administrator must also permit scheduled tasks.
The scheduled tasks documentation lists support on paid plans. Specify the frequency, time zone, source scope, output format and whether Claude may send or modify anything externally. Also say whether an existing output file may be overwritten, so each run has clear boundaries.
What does a practical workflow look like?
The following is an example of how to brief Claude, rather than a report of a test we performed. It combines inputs, decision criteria and review points.
- Provide the sources and goal. Upload three pricing sheets and ask for a comparison separating setup costs from monthly charges. Specify dates and currencies, and ask Claude to mark missing values as unknown.
- Check the reasoning. Ask which file and condition supports each comparison. Avoid filling gaps such as cancellation fees or taxes with assumptions.
- Request the deliverables. Continue in the same conversation: ask for a spreadsheet and a five-slide decision brief. Identify the audience and desired detail.
- Review and revise. Compare numbers and formulas with the originals, check whether recommendations follow the stated criteria, and request specific corrections. Download the final files and open them in the apps you actually use.
Research and file production now share conversational context. That continuity does not guarantee accuracy. Verify consequential facts against the originals, and separately define whether sending messages or changing source files is authorized.
Does work continue when your computer is off?
Cloud-based work can continue after you close your laptop or leave the page. Tasks that need files or applications on your computer require Claude Desktop to remain open. Cloud execution does not make files on a powered-off computer accessible.
Producing a report from uploaded files and connected cloud sources has different requirements from organizing a local folder or operating an installed application. Local work needs the computer powered on with the required connection and permissions available. Check the computer use documentation for supported environments and current limitations.
You can continue work across web, desktop and mobile, including checking progress and adding instructions from your phone. Starting or redirecting a task on mobile does not remove its local execution requirements. Before turning off your computer, establish which sources and execution environment the task depends on.
Which plans get access?
As of November 16, 2026, the official guidance distinguishes the following cases. Accounts on the same individual plan can receive the change at different times, so check the actual account experience alongside the announcement.
| Plan | Rollout and controls |
|---|---|
| Pro, Max and Ultra | Gradual rollout on web, desktop and mobile. The guidance says there is no individual switch to enable it. |
| Team | Controlled through Chat and Cowork unified. Default activation for existing organizations is scheduled for December 1, 2026, subject to prior administrator choices and required capabilities. |
| Enterprise | Organization and role settings apply. Organizations that have not changed the setting are being notified of conditional automatic activation on November 16, 2026. |
| Free | The original announcement listed it for later availability. The current unified guide does not give a completed rollout date for all Free accounts, so universal access should not be assumed. |
Team and Enterprise administrators can check Organization settings > Capabilities > Chat and Cowork unified. Cloud code execution and file creation settings, as well as certain special data-retention configurations, can affect availability. Consult the separate Team administrator guide and Enterprise administrator guide for applicable conditions.
For individual Pro, Max and Ultra accounts, the guide says that seeing separate Chat and Cowork options in the message box means the account has not moved yet. You can continue using the existing interface. On an organization account, check administrator settings and your permissions before assuming you only need to wait.
What should existing users check?
Existing conversations, tasks, projects, settings, connectors and skills carry over, and older Cowork tasks can still be opened. However, the individual-account guidance says you cannot return to separate Chat and Cowork options after migration. Distinguish that rule from the controls available to organizational administrators.
After migration, look for conversations and tasks together in Recents. Check common instructions under Settings > Your Claude, or Settings > Account in the older layout. Make sure previous Cowork global instructions still reflect what you want, and review local storage and trusted-folder settings.
Some limitations remain: the current guide lists branching a conversation from an earlier point and Add from GitHub as unsupported. Search does not include older Cowork tasks, although you can find them by name in Recents. Check any feature your workflow depends on before assuming it migrated unchanged.
Long research and file-generation tasks can consume more of your allowance than quick questions; review Settings > Usage. Execution permissions can affect the whole conversation. For important file edits or outgoing messages, narrowly define what may change and review intermediate and final results.




