Hi, this is my team! Happy to answer any questions.

There's a lot in this launch, but the core idea is to simplify the product while giving users access to more capabilities. You no longer need to know ahead of time how much work a conversation might involve. If you're at your computer, Claude can use your local files and apps. If you close your laptop, Claude can keep working on its own computer.

This launch also lets you use Claude Design, Claude Docs, and Claude Slides directly from conversations. That's possible because we made Artifacts much more powerful: whenever Claude makes you an app, website, design system, or anything else, it can deploy an artifact with multiplayer features and databases.

As many of you probably know from your own work, giving users more power while making the experience simpler is really, really hard. It took many iterations to get to this version. We're far from done, but I expect people will be able to do much more while having to think about it less.

From a user experience standpoint this sounds like a clear win. Congratulations.

With AI safety top of mind so much lately, I can't help but notice the announcement does not address this.

With "Chat" mode, there was a user expectation that session had only limited capability to produce unexpected side effects, read sensitive files, etc.

With "Cowork" mode, it seems like more powerful capabilities have been on by default, requiring deep settings and safety understanding to disable if desired.

Merging modes feels like it is removing a simple and easy to understand risk management tool. How does the combined mode help users understand, manage and feel confident about what risks they are accepting?

As part of all the work being done I really hope the sidebar gets more user control. There is a bunch of stuff that I don't intend to use myself but take up first class space (designer is always there, I never need to bring up artifacts, etc). I'd like to reduce the sidebar to what I use most often.

Specifically around the work UX. Trying to bring up scheduled tasks is really painful and required a lot of clicking around instead of just seeing the task results under my project. I hope this is being looked at.

Lastly, and this is a real nit. Let me turn off the "tips" when stuff is being worked on. I'm already paying, you don't need to force a rotating feature advertisement into the interface.

How are you determining how much oomph Claude gives a particular question? When I ask Claude Chat to e.g. summarize a document, it does this and returns a summary inline, whereas cowork does a bunch of tool calls and intermediate steps, eventually writing a document to disk. How does new claude know how deep to go?

> Claude Design, Claude Docs, and Claude Slides

Why/when would I ever need any of these? Can't y'all focus on useful features instead?

Why is Claude Code still proprietary, while Codex is Open Source? What would it take to fix that? This is a major reason to pick OAI models over Anthropic (because while you can use an open agent with any model, the AI labs charge much more for that interaction style).

Will there be a Claude Sheets too? I find myself using Claude to work with spreadsheets more than almost any other document type. It does okay now, but feel like it could be even better, especially with visualizations and formulas.

It's not a bad idea, however if Cowork, Designs, Docs and Slides are still different products, it'd be great for the user to know they are being routed to that particular product automatically because of what they were asking for in their prompt.

In the web interface, are there any plans to support attaching local directories through File System Access API and accessing internal (as in, not reachable over Internet) MCPs, assuming correct CORS setup, of course?

I liked the ability to explicitly only chat, without the possibility of Cowork activating since I have never wanted that. It's unclear how I can still guarantee that now.

this is good change for ux. thanks

I'm operating Team accounts, are there changes on how org-wide skill/plugin get loaded and used?

How do you guys have so many resources but no taste? It’s crazy.

[dead]