This website uses cookies

Read our Privacy policy and Terms of use for more information.

The Cowork we have been writing about since August is now just Claude. On 16 Sep Anthropic said it is merging Claude Cowork and chat into a single product, so you no longer pick a mode before you start. Ask a quick question and you get an answer. Hand over a report, and Claude works through it, in the cloud, after you have shut the laptop. We covered Claude in Chrome turning into a Cowork session on 18 Aug, made Cowork's browser sign-ins the featured story on 1 Sep and used Claude Design for the 15 Sep Quick Win. All of that now sits inside an ordinary conversation.

Two new outputs arrived with it. Claude Docs and Claude Slides are in beta on paid plans, and Claude Design now works inside conversations rather than as a separate tool. Anthropic says you can edit the result directly, present slides straight from Claude, or download as PowerPoint or PDF, and everything lives at one shareable link you can open on a phone. The rollout starts with Pro and Max over the coming weeks, with Team and Free to follow and Enterprise admins given at least 30 days' notice before anything changes.

For a project manager or cost consultant, the relevance is straightforward. Two of the things you produce most often are the monthly progress report and the deck that summarises it for a board or client. Anthropic’s own example uses a weekly report and five slides for a leadership meeting. That is very close to the work many of us already do.

One hand-off, two artefacts

The example on Anthropic's page runs like this. A report is due at noon. You ask what moved in the pipeline last week, then add 'write it the way we always do, flag anything that slipped, and put the highlights in five slides for the leadership meeting'. Claude asks when something is unclear. You check progress from your phone, and by the time you reach your desk, the report is ready as a document and the slides are ready to edit and download. Because both were created from the same conversation, Anthropic says the slides already match the report. You can even schedule it for every Monday, so Claude starts the report automatically.

Swap 'pipeline' for 'programme', cost and risk, and the shape is familiar. The monthly report pulls from the schedule, the cost plan and the risk register, then someone rebuilds the same numbers in PowerPoint and hopes nothing drifted between the two. If one hand-off produces both, the reconciliation step disappears. So does the two hours on a Sunday evening.

Who checks it

Anthropic is careful to say you keep the final say, and the Help Center guides how you can do that. A permission setting in the message box controls independence. In Manual, the default, Claude asks before it takes actions, and you approve each one. In Auto, it keeps working, and automated safety checks run before it acts. The setting applies to the whole conversation. Anthropic still recommends reviewing its work when the task involves something important, such as sending a message or changing a key file.

Our view is that the approval gate is well designed for actions and says nothing about accuracy. It will ask before emailing the client. However, it will not check whether the items it flagged are the ones your planner would have flagged. That is still the PM’s job, and it becomes harder when the report reads well and the deck matches it. Two consistent artefacts can be consistently wrong.

What a firm on Team or Enterprise actually gets

The announcement is aimed at individuals first, and firms should read the small print before assuming anything lands on their desks this month.

  • Pro and Max accounts move first, Team follows, and Enterprise admins choose when Docs, Slides and Design are turned on for their organisation.

  • Once an account has moved over, the Help Center says you cannot switch back to separate Chat and Cowork options.

  • Tasks that use files or apps on your own computer still need Claude Desktop open, while cloud tasks keep running when it is shut.

  • Anthropic told VentureBeat in an emailed statement that Claude Slides can be downloaded as PowerPoint or PDF, while Claude Docs can be exported to Microsoft Word or Google Docs, with additional export destinations planned. That matters because a Word file is still what most contracts and document control systems expect.

  • Longer agentic tasks generally use more of your plan's usage allowance than a quick question, so a scheduled Monday report is a recurring cost, not a free one.

A day later Anthropic also previewed a redesign of Projects, currently in beta for select Pro and Max subscribers in Claude Code, where a coordinating Claude splits a goal across parallel cloud threads with shared memory and keeps working after you step away. It is developer-only for now, but it points at where the report-and-deck pattern goes next.

Doing more, trusted less

Anthropic's stated reason for the merge is that "people used both, and told us the frustrating part was deciding where a task belonged." It is a fair one. But 'does more' has arrived in the same week as 'trusted less' by some very large customers. The Information reports that Nvidia, Palantir and Booz Allen have restricted Claude Fable on sensitive work over 30-day data retention. We cover that separately this week. For a firm deciding whether a client's cost report should flow through a scheduled Claude task, both stories belong in the same conversation with the information security lead.

Takeaway

The interesting change is not that Claude can write a report or a deck. It could do both before. The change is that one instruction now yields both, keeps them aligned, and can be told to repeat every Monday. That moves the PM's effort from producing the artefacts to owning them, and ownership means a check that no permission dialogue performs.

  • Pick one recurring report, run it manually in Claude for two cycles, and compare its 'slipped' list against your planner's before you let it near a schedule.

  • Leave the permission setting on Manual for anything that touches a client, and write down who approves the output before it leaves the building.

  • If you are on Team or Enterprise, ask your admin when Docs and Slides will be switched on and what the retention terms are, so the decision is made on purpose rather than by default.

If you want to see how we test tools like this against real project workflows before they reach your Monday morning, join Project Flux at projectflux.ai.

All content reflects our personal views and is not intended as professional advice or to represent any organisation.