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.
Claude Cowork and chat are now one Claude
191–200 of 218 posts
Re: Claude Cowork and chat are now one Claude
#192Earlier quoted context omitted.
Isn't that expected since LLMs are inherently non-deterministic?
LLMs are inherently deterministic. The way everyone deploys LLMs leads to non-deterministic results, but there's nothing† stopping providers from offering deterministic evaluation if they choose. All the sources of randomness are under the control of the provider, even if today's deployment structures mean providers introduce extra randomness due to the concurrent nature of the evaluation. Serialise the computation,…
Its also about very similar inputs -> different outputs. Even with everything you said, yes, same input would result consistently into same output, but sliightly different input and you might get completely different/semantic answer.
Re: Claude Cowork and chat are now one Claude
#193People 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 model itself should figure out how much “power” it needs to run the query. I’m just asking a question. Whether you need to do a simple internet search or spin up a VM and run scripts is up to you.
Re: Claude Cowork and chat are now one Claude
#194Earlier quoted context omitted.
I don't think it's that anyone wants the interface to be chat. I think it's that the underlying technology is inherently words in and words out. It's similar to how devices with capacitive screens are most naturally going to support tapping, dragging, and pinching.
It's funny to me that instead of moving existing tech to a word in word out paradigm, people are dropping millions getting the chat to work with the existing paradigm. Probably inevitable, but seems like a lot of disruption could happen there.
Re: Claude Cowork and chat are now one Claude
#195Hi, 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 le…
Re: Claude Cowork and chat are now one Claude
#196Hi, 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 le…
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.
Re: Claude Cowork and chat are now one Claude
#197Earlier quoted context omitted.
And does having an AI call the restaurant instead of you doing it sound cool to you?
I’m not the person you asked but I’m also confused by this use case. Most restaurants have a web UI which is very simple and easy to use.
Re: Claude Cowork and chat are now one Claude
#198Re: Claude Cowork and chat are now one Claude
#199Earlier quoted context omitted.
honestly, one day i will understand why these guys go so hard on planning vacations. one of the best parts of vacations is actually planning it! trying to find restaurants, organizing your days, trying to fit activities -- that makes you look forward to your time off. really, i want to automate the boring parts of my life (did i really pay rent this month?) not the things that make me happy.
> one of the best parts of vacations is actually planning it For some. Others hate or fear it. For others it just feels like work.
Re: Claude Cowork and chat are now one Claude
#200Earlier quoted context omitted.
IMO no one knows what LLMs are capable of yet and the goal post keeping moving every few months that building any specific UIs right now risks rendering them obsolete or too slow. e.g. We went from somewhat smarter code autocomplete, to asking chatgpt copy paste, to cli agent running inside your project, managing session, to GUI to manage that, to projects where you talk to a "Chief of Staff" agent that manages other…
We have all that? I'm still copying and pasting off the WebUI of ChatGPT. Traditional and boring works for me.
I wouldn't call copy & paste code from a webui of chatgpt either traditional or boring. I'd call it tedious, error prone and guaranteed to get poor results. There is much better tooling and harnesses to leverage now.