Claude now picks chat or agent for you. Approval stays the default

On Tuesday, @claudeai announced that Claude Cowork and chat "are merging into one Claude." You ask a quick question or hand over a report, and Claude "takes it from there, even after you close your laptop." The post had passed 2.7 million views by Wednesday, and Anthropic says the change reaches Pro and Max users over the next few weeks.

Cat Wu, who works on Claude at Anthropic, explained the thinking. @_catwu wrote that people didn't want to choose which Claude product to use for a task, and that "Claude can handle the routing for you." Based on the prompt, the model decides whether to give a quick answer or go do deeper agentic work, and what kind of output fits.

The timing is what caught my eye. One day earlier, Anthropic had expanded Claude for Small Business to 43 workflows and 27 new integrations, including Shopify, Square, Stripe, Gusto, Xero, and Zapier. Owners have installed the plugin more than 900,000 times since May. Monday's announcement said it "runs in Claude Cowork, the desktop app." A day later, Anthropic announced that Cowork would stop being a separate app.

What actually changed

Claude used to come in three modes: chat, Cowork for longer jobs with your files and connected tools, and Claude Code for developers. Now there are two, Claude Chat and Claude Code. Anthropic says there is nothing to turn on, and that your chats, projects, artifacts, connectors, and skills carry over.

The same update puts Claude Docs and Claude Slides into beta on paid plans and moves Claude Design into the conversation, so a one-pager can become a deck without switching tabs. Enterprise admins decide when those turn on, and Enterprise customers get at least 30 days notice before the merge reaches them. Team and Free plans come after Pro and Max.

Monday brought a second business-facing launch. @claudeai posted that Salesforce in Claude is now in beta, with "37 pre-built sales skills" for call prep, deal review, pipeline dashboards, and forecasts. That post drew close to 5 million views, more than the merge itself.

The default that matters

For an owner, the line worth reading twice this week is about permission, not routing.

Claude for Small Business ships with approval mode on: "Claude does the work and waits for your approval before anything sends, posts, or pays." Some workflows stop a step short on purpose. Claude stages payroll in Gusto, and you submit it. The weekly Monday brief pulls cash position, last week's sales against the week before, pipeline movement, overdue invoices, and the three things that need you, onto one page.

The merged app keeps the same posture. By default, Claude asks before it acts. You can loosen that so it keeps working and only checks in when it hits a problem.

Compare that with Meta's Muse, which sends every outbound action past a second AI before it goes out. Anthropic's design puts the reviewer's job on you. That's slower. It's also the only version where you know what left the building under your name.

My read

The routing change is bigger than it looks. Until this week, you decided whether a request was a question or a job. Now the model decides. Most of the time it will guess right. Some of the time you'll ask for a two-line answer and get a background task, or the reverse. Wu's post says you can stop, redirect, or "exert finer control over Claude's effort." Watch how often you have to.

The product churn bothers me a little. A plugin pitched Monday for a desktop app is being folded into a different one by Tuesday. Anthropic says nothing gets lost, and it probably doesn't. I'd still open the new app and confirm that your connectors and your approval settings survived the move before you trust a Monday brief.

And I'd leave approval mode on longer than feels necessary. The temptation, once the drafts look good for a few weeks, is to switch to check-ins only when something goes wrong. The trouble is that agents don't always know something has. Nous Research's cleanup run passed its tests with 65 error-handling changes that only human review caught.

What this means for your business

Forty-three workflows are templates. The Monday brief works if your invoices live in Xero or QuickBooks and your pipeline lives in a CRM the connector can read. If your numbers live in a spreadsheet someone updates on Friday, the brief will be as stale as the spreadsheet. Before you pick a workflow, ask which of your systems hold data clean enough to feed one.

Then draw the line. Payments and anything that goes to a customer stay behind approval. Internal summaries can run on their own once you've checked a few.

New Face Design's free process audit starts with that map: which of your systems software can read today, and where a person still has to sign off. Start here.