3 ms·

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 mor

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.

LoganDark 10d ago
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.
- ChickeNES 10d ago
  This! My use of the web chat/app was already basically 0, now it will be 0.
ecliptik 10d ago
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.
- giwook 10d ago
  Oh sheet son.
- tstrimple 10d ago
  What sort of issues do you see with spreadsheets? I almost never use Claude or Cowork. Just Claude Code. When I've generated or modified spreadsheets it tends to build python scripts for it which makes regeneration trivial. I have to fight a bit on formatting sometime, but I find if I format it the way I want I can get CC to read the file follow that in the future.
JoshTriplett 10d ago
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).
- giwook 10d ago
  I don't know how proprietary Claude Code really is. Just wait for the next leak!
  - JoshTriplett 10d ago
    That's exactly the point: it's not as if anything is being gained by it being proprietary, because nothing is actually secret.
ChickeNES 10d ago
> 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?
- cpcabbge 10d ago
  There are a lot of people using this outside of the coding space, most of my friends use these to create decks and things like that to present. Mind you they never double check information and numbers.
  - ChickeNES 10d ago
    > create decks and things like that to present Not really proving their usefulness there :P
  - tstrimple 10d ago
    Claude Code has almost always been able to do a passable job of this. I wonder if this new version will need less cleanup. Claude Code would write python scripts to generate the deck. It at least formatted cleanly with templates.
- dmd 10d ago
  I guess they didn't realize you're their only user!
bcorigliano 10d ago
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.
Selkirk 10d ago
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?
ieie 10d ago
How do you guys have so many resources but no taste? It’s crazy.
- jimmydoe 10d ago
  imo Claude is ok on taste, just with many sloppy bugs. ChatGPT/Codex is worse on taste.
jimmydoe 10d ago
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?
confusedbucket 10d ago
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?
Centigonal 10d ago
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?
hattar 10d ago
[dead]
saratogacx 10d ago
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.
dbbk 10d ago
I have a question about project memory. Last time I tried using Claude to organise my chats into Projects, it turned them into isolated silos. I asked a different chat to refer to what we'd discussed in the other chat, and it said it wasn't allowed to access it. 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?
tstrimple 10d ago
I rarely use Claude or Claude Desktop. Almost 100% of my usage is Claude Code because it ties into all of the private infrastructure I've built around it. I've had decent success using CC for generating Office documents of various formats. It tends to reach for a python script and library to generate them and the output is typically clean and easy to apply a template to. I have had issues where I need to manually modify the files to demonstrate format and style, but that's also something that can built into context after with references to templates. 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?
cpinto 10d ago
Thanks for participating in the discussion Felix. A big issue for me - not sure if others suffer from this - is that it’s next to impossible to track work in progress, especially with when there are artefacts involved or reports etc. Things that require multi-day work of back and forth and reflection. 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.
Kerbonut 9d ago
Can you standardize with all of your tools on a common registry key and settings paradigm and same plugin/skills paradigm and common method for enterprise delivery? It’s a pain in the neck getting all of this set up and deployed throughout the org.

LoganDark 10d ago

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.

ChickeNES 10d ago
This! My use of the web chat/app was already basically 0, now it will be 0.

ecliptik 10d ago

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.

giwook 10d ago
Oh sheet son.
tstrimple 10d ago
What sort of issues do you see with spreadsheets? I almost never use Claude or Cowork. Just Claude Code. When I've generated or modified spreadsheets it tends to build python scripts for it which makes regeneration trivial. I have to fight a bit on formatting sometime, but I find if I format it the way I want I can get CC to read the file follow that in the future.

JoshTriplett 10d ago

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).

giwook 10d ago
I don't know how proprietary Claude Code really is. Just wait for the next leak!
- JoshTriplett 10d ago
  That's exactly the point: it's not as if anything is being gained by it being proprietary, because nothing is actually secret.

ChickeNES 10d ago

> 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?

cpcabbge 10d ago
There are a lot of people using this outside of the coding space, most of my friends use these to create decks and things like that to present. Mind you they never double check information and numbers.
- ChickeNES 10d ago
  > create decks and things like that to present Not really proving their usefulness there :P
- tstrimple 10d ago
  Claude Code has almost always been able to do a passable job of this. I wonder if this new version will need less cleanup. Claude Code would write python scripts to generate the deck. It at least formatted cleanly with templates.
dmd 10d ago
I guess they didn't realize you're their only user!

bcorigliano 10d ago

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.

Selkirk 10d ago

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?

ieie 10d ago

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

jimmydoe 10d ago
imo Claude is ok on taste, just with many sloppy bugs. ChatGPT/Codex is worse on taste.

jimmydoe 10d ago

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?

confusedbucket 10d ago

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?

Centigonal 10d ago

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?

hattar 10d ago

[dead]

saratogacx 10d ago

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.

dbbk 10d ago

I have a question about project memory. Last time I tried using Claude to organise my chats into Projects, it turned them into isolated silos. I asked a different chat to refer to what we'd discussed in the other chat, and it said it wasn't allowed to access it. 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?

tstrimple 10d ago

I rarely use Claude or Claude Desktop. Almost 100% of my usage is Claude Code because it ties into all of the private infrastructure I've built around it. I've had decent success using CC for generating Office documents of various formats. It tends to reach for a python script and library to generate them and the output is typically clean and easy to apply a template to. I have had issues where I need to manually modify the files to demonstrate format and style, but that's also something that can built into context after with references to templates. 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?

cpinto 10d ago

Thanks for participating in the discussion Felix. A big issue for me - not sure if others suffer from this - is that it’s next to impossible to track work in progress, especially with when there are artefacts involved or reports etc. Things that require multi-day work of back and forth and reflection. 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.

Kerbonut 9d ago

Can you standardize with all of your tools on a common registry key and settings paradigm and same plugin/skills paradigm and common method for enterprise delivery? It’s a pain in the neck getting all of this set up and deployed throughout the org.