Claude Cowork and Chat Are Now One: A Practical Guide to the Unified Workflow
Anthropic announced on September 16, 2026 that Claude Cowork and regular chat are being merged into one Claude experience. The practical change is simple: users no longer need to decide whether a request belongs in “Chat” or “Cowork” before they begin. A quick question, a multi-step research task, a report, a spreadsheet, or a presentation can now start from the same conversation.
Korean edition: 한국어로 읽기
This is a change to the entry point, not the removal of Cowork capabilities. In the unified experience, Claude can decide whether a request needs a short answer or a longer task involving web research, connected apps, code, files, documents, spreadsheets, or slides. Developers who want to package reusable team instructions can also read Shiftlog’s guide to Claude Code plugins.
Who gets the unified experience, and when?
The rollout starts with Claude Pro and Max on web, desktop, and mobile and is being staged over several weeks. Accounts on the same plan may receive it at different times, and there is no manual switch to enable. Team and Free are planned to follow. Enterprise administrators are expected to receive at least 30 days’ notice before their organizations change.
Open Claude and inspect the message box. If it still shows separate Chat and Cowork choices, the account remains on the earlier experience. Keep using either option as usual. If those choices have disappeared, the unified experience has arrived: start a normal conversation and describe the complete task. After an account migrates, it cannot return to the separate Chat and Cowork interface.
What merged, and what carries over?
| Area | Before | Unified experience |
|---|---|---|
| Starting point | Choose Chat or Cowork | Describe the task in one conversation |
| Long-running work | Mostly started in Cowork | Research, code, and file work can begin from chat |
| Deliverables | Split across Cowork and creative surfaces | Docs, sheets, slides, and designs share one context |
| Existing work | Stored in Cowork tasks and projects | Tasks, projects, connectors, skills, artifacts, and files carry over |
Existing Cowork tasks can still be opened and continued. Global instructions move to Settings > General > Instructions for Claude, so check that the tone, output format, and standing business context still say what you intend. Recents combines quick chats and longer work, but search does not include older Cowork tasks. Those older items can still be found by name in Recents. Memory from tasks that ran only on a local computer remains with those tasks.
Prerequisites: plan, connectors, and local access
- Account: Cowork-style task capabilities require a paid Claude plan. The unified interface reaches Pro and Max first.
- Connected apps: To use material from Google Drive, Gmail, Microsoft 365, Slack, or another supported service, connect only the apps needed under Customize > Connectors.
- Local files: Claude Desktop must be installed, open, and connected whenever a task needs local folders, the local browser, or computer-use features.
- Inputs: Prepare the source files, links, folder path, reporting period, intended audience, output format, and acceptance criteria. Missing inputs invite assumptions.
Many tasks run in the cloud and can continue after the browser closes, the laptop sleeps, or you switch to mobile. Scheduled cloud work can run while the computer is off. That does not give Claude automatic access to a Downloads folder or a desktop application. Local work still depends on explicit permission and an available Claude Desktop app.
A reliable way to hand over a task
- State the outcome. Define what “done” means: a weekly report, a five-slide leadership deck, a folder structure, or a table of themes.
- Name the format. Ask for a Word document, PowerPoint file, spreadsheet, shareable document, or a message ready to paste into Slack. Include length or slide-count limits.
- Identify the inputs. Attach files, share links, name a folder, or point to connected apps. Also say what Claude must not use.
- Choose a permission setting. Manual is the default and pauses before actions. Auto keeps working while automated safety checks review actions.
- Watch and redirect. Follow progress from web, desktop, or mobile. Correct the audience, remove a source, change the format, or stop an unsafe step while the task is running.
- Verify the deliverable. Read the output, check calculations and quotations against the original sources, and confirm that no unsupported claims or unintended file changes remain.
- Export, share, or schedule. Download editable files, share an artifact link where appropriate, and schedule recurring work only after reviewing a successful first run.
Do not treat a completion message as proof that the job is ready. Confirm that every requested file exists, opens correctly, and matches the audience, date range, format, and count. Claude is a production tool and a drafting partner; it does not replace factual review or ownership of the final decision.
Use case 1: A weekly report plus five leadership slides
Goal: Produce a written pipeline report and a five-slide leadership summary from the same work materials. Inputs: Provide the relevant project notes, CRM export, previous report template, reporting period, audience, and connected source such as Drive or Slack.
Process: Ask for the report in the established format with week-over-week movement, risks, slipped items, and decisions required. Then request exactly five slides based on that report. Because both deliverables live in one conversation, the deck can reuse the approved report context rather than starting from a separate handoff. Review the written draft before requesting the final presentation when accuracy matters.
Validation: Reconcile pipeline totals with the source export, check that “slipped” uses the team’s real definition, and make sure uncertain forecasts are labeled rather than presented as facts. Confirm that the report and deck use the same numbers. Limitation: If access depends on a local spreadsheet or browser session, Claude Desktop must remain open. Sensitive sales data should be exposed only to the minimum required connector or folder.
Use case 2: Themes and supporting quotes from interview notes
Goal: Find recurring themes across five interviews and attach a representative quotation to each theme. Inputs: Supply the notes, the research question, the desired number of themes, participant labels, any segmentation rule, and an anonymization policy.
Process: Ask Claude to separate direct evidence from interpretation, cite each quotation by speaker or filename, and preserve conflicting views instead of forcing consensus. Approve access only to the specific notes needed for the analysis.
Validation: Open the original note for every quote. Check whether a theme is genuinely recurring or driven by one participant, whether dissenting evidence was omitted, and whether identifying details were removed. Limitation: Theme synthesis is interpretive. A model can flatten nuance or choose a vivid quote that is not representative, so the output is a structured first pass rather than final qualitative research.
Use case 3: Organizing a Downloads folder
Goal: Sort a Downloads folder by file type and date while preserving an auditable structure. Inputs: Use Claude Desktop, authorize only the target folder, define categories such as PDFs, images, installers, spreadsheets, and archives, and list anything that must be excluded.
Process: Start in Manual. Ask Claude to show the proposed moves before changing anything. Specify whether duplicates should be flagged instead of removed, whether filenames must stay unchanged, and where recent files should remain. Approve the plan only after checking that important material will not be buried or overwritten.
Validation: Compare file counts before and after, spot-check several destinations, and confirm that extensions and contents still match. Limitation: Claude requires explicit permission before permanent deletion, but moving or renaming files can still disrupt work. Back up irreplaceable material and do not automate cleanup of credentials, financial records, or unknown installers without close review.
Manual versus Auto
| Question | Manual | Auto |
|---|---|---|
| How it acts | Asks before actions | Continues after automated safety checks |
| Best fit | First runs, sensitive data, hard-to-reverse changes | Well-scoped, lower-risk repetitive work |
| Trade-off | Frequent approvals can pause work | Uses more of the plan limit and no safety check is perfect |
Claude can act only through the folders, connectors, browsers, and computer access you grant, but approved access can still reach sensitive material. Limit the scope, review connected apps regularly, and be cautious with instructions found inside untrusted documents or websites. For actions with real consequences, such as sending a message, changing an important record, moving money, or deleting a file, stay close and review the result.
Everything counts toward the plan’s usage limits. Web searches, code execution, file creation, and connected-app steps generally consume more than a quick answer, and Auto consumes more than Manual because of its additional checks. Monitor Settings > Usage and start unrelated work in a new conversation instead of carrying unnecessary context.
Current limitations
- Add from GitHub is not supported in the new experience.
- Conversation branching from an earlier point is unavailable.
- Incognito chats open the previous experience, where Claude cannot create files or run code.
- Search does not cover older Cowork tasks, although they remain available by name in Recents.
- Dispatch is unavailable to new users; existing users can continue using it for now.
Who should try it now?
The unified workflow is a good fit when a task has several connected steps, requires a finished deliverable, benefits from background execution, or needs context to flow from research into a report, spreadsheet, or deck. Start with a small, reversible task whose inputs and acceptance criteria are clear. Use a smaller manual workflow when the material is highly sensitive, the sources are incomplete, an error would be expensive to reverse, or a current limitation such as GitHub import or conversation branching is essential.
Practical checklist
- Check whether separate Chat and Cowork choices are still visible.
- Define the outcome, format, audience, source inputs, and exclusions before starting.
- Use Manual for consequential actions and Auto only when the scope and risk are understood.
- Keep Claude Desktop open for local folders, browser access, or computer use.
- Validate quotations, figures, file changes, and exported files before sharing.
- Schedule only a workflow that has already produced a reviewed result.
Official sources
- Claude Cowork and chat are now one Claude
- Claude Cowork and chat are one Claude
- Get started with Claude Cowork
Sources checked: September 17, 2026
Comments
Post a Comment