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?
Why/when would I ever need any of these? Can't y'all focus on useful features instead?
Not really proving their usefulness there :P
Just wait for the next leak!
I'm operating Team accounts, are there changes on how org-wide skill/plugin get loaded and used?
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.
This was pretty frustrating. By trying to organise my chats, I actively made them worse. ChatGPT at least gives you the option to have either open or closed memory. Is this being considered?
Where do you see Claude doing better than what I'm seeing with Claude Code in these circumstances? Are there any reasons for me to leave my pretty heavily customized CC environment for the other versions?
Chat is a horrible interface for this, having to scroll up and down across lengthy conversations to try and pick up a thread.
I’m really sorry but I really fail to understand why this massive push to “chatify” everything. A task with its own context and multiple chats feel like a much better approach to work. Even if the work is spawned from a main chat window - eg “Claude we need to work on XYZ” and it creates a task to track this piece of work.
Further, recurring tasks again are really really hard to manage with a chat interface - which of the 10 chats has that question that the recurring task raised?!
And of course all this UX debt will likely stand in your way of building reactive items - ie spawning a task in response to some outside event. Think an inbound email being handled by a prompt that triggers a task and creates a draft response ready for my review and approval. Very hard to do with chat windows.
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.