Live data from Hacker News

Claude Cowork and chat are now one Claude

claude.com

11–20 of 218 posts

Re: Claude Cowork and chat are now one Claude

#12
post #7

I'm starting to explore alternative options because Claude has become an awful value proposition. Any suggestions?

I turned off Anthropic properly and switched all of that over to OpenAI yesterday. (I use other models for other things too, especially DeepSeek in Pi). Honestly aside from the voice it uses you wouldn't notice a difference. Switching costs are low, vote with your wallet.

So you voted for Kodos instead of Kang [1]. Local models are the way out of the rug pulling

[1] https://m.youtube.com/watch?v=BUAnyVAanac&ra=m

Re: Claude Cowork and chat are now one Claude

#16
post #7

Earlier quoted context omitted.

I turned off Anthropic properly and switched all of that over to OpenAI yesterday. (I use other models for other things too, especially DeepSeek in Pi). Honestly aside from the voice it uses you wouldn't notice a difference. Switching costs are low, vote with your wallet.

So you voted for Kodos instead of Kang [1]. Local models are the way out of the rug pulling [1] https://m.youtube.com/watch?v=BUAnyVAanac&ra=m

I don't actually disagree, and advocate that for now the thing to do is use both.

You need to use frontier models to understand where the puck is going, but also to use local ones for anything remotely sensitive.

Re: Claude Cowork and chat are now one Claude

#17
post #6

People keep asking for this w/ Codex, too, and I really regret that both labs seem inclined to listen. If you ask a thinking/research type question in 'Chat' versus 'Work' mode in these products -- say, something complex about politics, or do a multiturn business strategy, or want to work thru a new concept, you get very different answers. The harness, steering, etc. in the chat/reasoning products is so much better f…

The fact that it doesn't work well today doesn't invalidate the user need. Not everyone wants a terminal style interface. Traditional UX makes more sense especially if say you are accessing existing plugins and say kicking off a scheduling task - no way would I want to do that via a chat interface if I have the option.

Re: Claude Cowork and chat are now one Claude

#18

To Anthropic: I hope you don't merge Claude Code and chat, I like keeping their memory separate.

I very intentionally have all memory turned off for chat. The amount of times I want to discuss an approach for it to pull memory out and have that steer the decision making is so obnoxious

Re: Claude Cowork and chat are now one Claude

#19
post #10

Nobody really knows how to product-ize any of these LLM interfaces beyond just chat. They don't want a traditional UI with buttons and forms and labels because they want the interface to be "chat". The problem is that "chat" is tedious. And the turn-based, linear nature of the chat interaction model makes it even more tedious and unproductive.

[dead]

Re: Claude Cowork and chat are now one Claude

#20
post #10

Nobody really knows how to product-ize any of these LLM interfaces beyond just chat. They don't want a traditional UI with buttons and forms and labels because they want the interface to be "chat". The problem is that "chat" is tedious. And the turn-based, linear nature of the chat interaction model makes it even more tedious and unproductive.

This has been my ongoing gripe. Someone put chat in front of a transformer model. It exploded like all prior versions of “AI chat” did. Now what?

The moment someone figures out a new modality for LLMs is when we’ll see the next hockey stick.

Post reply on HN