AI-First
Claude's unified interface, which Anthropic announced on September 16, 2026, brings Chat, Cowork and Artifacts into a single window. It routes each request to the right feature, so you no longer have to pick a tab. For a small business, this consolidation is a step in the right direction, because how easy a tool is to use decides whether people actually use it.
That said, I think it only solves half the problem. The other half, structuring your own context, is still up to you.
- 🎯 One window: Chat, Cowork and Artifacts merge, and Claude routes each request on its own.
- 📊 Docs and Slides: create, edit and export to PDF or PowerPoint without leaving Claude.
- ⚠️ Context still needs structure: a 2026 skill doesn't always load on its own in Claude Code.
- 🚀 Hands-on exercise: turn a repetitive task into a skill this afternoon.
What did Anthropic actually merge in September 2026?
On September 16, 2026, Anthropic merged the Claude Chat and Cowork front ends into a single interface that also includes Artifacts. According to TechCrunch, Claude Design, launched in April 2026 for designing websites and prototypes, now works from anywhere in Claude. Claude itself decides which part of the app to use.
Which features live in the single window?
First, three workspaces: Chat for quick questions, Cowork for more complex projects, and Artifacts for interactive content. Génération NT, quoting Anthropic, says the new interface lets Claude "determine what a task needs" and route the request to the right capabilities.
On top of that come two new beta features: Claude Docs and Claude Slides. Ask for a presentation and Claude builds it, edits it and presents it. You can download it as a PDF or PowerPoint file, or share it through a link that can be edited from a phone. With documents, you can comment on finished sections and ask Claude questions.
Who gets access, and when?
According to TechCrunch, the rollout starts with the Pro and Max plans, on web, desktop and mobile, "over the coming weeks." The Free and Team plans come later. blog-nouvelles-technologies.fr also describes a gradual rollout that starts with paying subscribers. None of the sources I read mention any extra charge, so check your own plan.
The table below sums up the before and after as the three sources describe it.
| Criterion | Before | After | Trend |
|---|---|---|---|
| Choosing a workspace | Three workspaces to pick from | One window, automatic routing | ↑ 2 fewer choices |
| Context across tools | Didn't always carry over | Cowork memory available everywhere | ↑ continuity |
| Documents and slides | No dedicated tool | Docs and Slides in beta | ↑ 2 new tools |
| Claude Design (April 2026) | Separate workspace | Usable anywhere in Claude | ↑ wider access |
| Availability | All plans | Pro and Max first | → gradual |
SOURCE: TechCrunch (Sep 16, 2026), Génération NT (Sep 17, 2026) · UPDATED 09/2026
Why a simpler interface matters more than one more feature
A unified interface removes the most expensive decision any tool asks of you: working out which one to open before you've even started. According to TechCrunch, Anthropic acknowledges that customers often weren't sure which tab suited which task. For a small-business owner, that hesitation costs you adoption. Anything that needs thinking about up front rarely becomes a team habit.
Why was picking a tab holding back adoption?
Génération NT describes a split that created "confusion and information silos", with context that didn't follow you from one tool to the next. On blog-nouvelles-technologies.fr, Yohann Poiron puts it differently: the split makes sense from the point of view of the service's architecture, but much less to someone who just wants a result.
A tool you have to understand before you can use it is a tool you don't use.
That's exactly what I see in the small businesses I train on Claude Code. The first question is never "what can the tool do?" but "where do I start?". The merger answers the second question.
Is simplicity enough to create value?
No, and this is where I part ways with the enthusiasm of the articles I read. blog-nouvelles-technologies.fr sees the merger as a step that brings the assistant closer to a real working environment. That's true, but a working environment is only worth what it connects to: email, CRM, documents, databases.
A nice window that produces slides is still an AI stuck in a chat window. The value isn't in the model or the tab. It's in how well it fits into your processes. If you want to see what Cowork does in practice, our guide to automating with Claude Cowork walks through the use cases.
What the consolidation doesn't solve: your own context
The merged interface makes picking a tool easier, but it doesn't tell Claude how your business works. That specific know-how goes into skills, instruction files that Claude loads on demand. A video from the AI LABS channel on front-end design skills shows both why they're useful and where they currently fall short.
Why do models keep producing the same generic output?
AI LABS repeats Anthropic's explanation: distributional convergence. A model predicts its next words from the probabilities in its training data, so it produces the most likely, safest, blandest option. That's why so many homepages look the same.
The good news, again according to the video, is that the model is very steerable when the instructions are precise. The problem is context size. Putting every rule about typography, colours and animation into a system prompt would clutter every conversation, including the ones that have nothing to do with design.
How does a skill avoid flooding the context?
A skill is a specialised instruction file that Claude only loads when the task calls for it. AI LABS sums up the division of labour: skills carry specialised expertise, subagents are full Claude instances with other tools for dedicated tasks, and MCP provides access to external data, since skills don't make network requests.
A clean context matters because, as the video points out, too many tokens degrade performance. It's the same logic as the merger, applied to your own work: load only what the task needs.
Why isn't my skill always being used?
Because the promised automation isn't quite there yet. The AI LABS presenter tested two skills in Claude Code: "typography", then "front-end aesthetics". Neither was picked up on its own, even with a prompt that explicitly asked for a landing page. Claude only ran the skill once it was told to use it.
The same presenter says the problem doesn't occur in the Claude desktop app. So a unified interface doesn't yet guarantee unified behaviour. The results are worth a look, though: with the fonts the skill enforced, the output was noticeably better, but a glow effect spoiled it, and the admin dashboard ended up too colourful to be usable.
The presenter's advice is pragmatic: be specific about what matters, such as fonts, instead of leaving the model to guess. To understand how skills and the configuration folder work, read the .claude folder nobody looks at.
Do this afternoon: consolidate your own usage
The consolidation I recommend isn't Anthropic's. It's yours: one repetitive task, one skill, one measurable test. Allow half a day at most, with no code to write. The goal is to see whether Claude follows your rules without you repeating them every time.
Which task should you start with?
Pick one that eats up time every week and whose output you can judge at a glance: a standard reply to a customer, meeting minutes, a sales proposal. Set a simple criterion, for example "the output matches our tone and format without edits." If you can't measure it, the task is too vague.
How do you build the skill, step by step?
Here's the method AI LABS followed for its test, adapted to a business task:
- Write your instructions in focused, plain language (tone, format, what to avoid), without going into technical detail.
- Ask Claude to turn that text into a skill.
- Download the skill and put it in your project's skills folder.
- Launch Claude Code and give it the task.
- If the skill isn't used, name it in your request. That's what had to be done in the video.
If you're new to this, the Claude Code tutorial in French covers installation, and this article on Claude Code for non-developers lays the groundwork. To gauge how widespread this is in your industry, McKinsey's AI adoption surveys are still a good starting point. And if you'd like help with integration, our team at GoLive Software does this every day.
Verdict: the merger is good news, as long as you don't stop there
Unifying Claude's interface is a good call, and I prefer it to three tabs nobody knows how to choose between. It lowers the barrier to entry, which matters for a team of 10 to 250 people without a technical culture.
Should you change the way you work because of this merger?
Not radically. If your team already uses Claude, wait for the rollout to reach your plan and watch what automatic routing does with your requests. Don't launch a "transformation" project: pick one use case, measure it, then expand.
My verdict fits in one sentence: the simpler interface wins, but your skills, your tool connections and your rules are what will make the difference. A useful assistant beats an impressive demo. And a Reddit thread like the one on r/InterstellarKinetics, which as far as I can tell just reposts the announcement without any comment, shows that community discussion is still thin. It's up to you to test it against your own usage.
Frequently asked questions
Does Claude's unified interface replace Cowork?
No. It brings Chat, Cowork and Artifacts together in one window, and Claude automatically picks the right feature for each request. Cowork still exists, but you no longer have to open it yourself. Cowork's memory, recently improved according to TechCrunch, keeps your context from one conversation to the next.
Are Claude Docs and Claude Slides available to everyone?
Not yet. According to TechCrunch and Génération NT, these features are in beta and are coming first to the Pro and Max plans, on web, desktop and mobile. The Free and Team plans are due to follow later, with no date given in the sources I consulted.
Can you export presentations created by Claude?
Yes. According to TechCrunch, generated presentations can be downloaded as PDF or PowerPoint files. Documents and slides can also be shared through a link and edited from a phone. You can even start a document on your computer and follow its progress in the mobile app.
Why doesn't my Claude Code skill trigger on its own?
In the AI LABS test, Claude Code didn't pick up two design skills on its own, even after they were renamed and even with an explicit request for a landing page. It only ran them when the presenter asked it to use them. The problem didn't show up in the Claude desktop app. So name the skill in your request.
Which interfaces can you use to access Claude in 2026?
Anthropic's help centre lists five access points: chat on claude.ai, the iOS app, the Android app, Claude Desktop, and the Console or API. The September 2026 merger concerns how the app is organised internally, not this list of entry points.
Vidéos YouTube
Discussions Reddit
Articles & ressources
- Anthropic merges Claude chat and Cowork in one interface | TechCrunch — techcrunch.com
- Claude fusionne ses interfaces et introduit de nouveaux outils — generation-nt.com
- Claude : interface unifiée, création de slides et documents — blog-nouvelles-technologies.fr
- Quelles interfaces puis-je utiliser pour accéder à Claude ? — support.claude.com