Live data from Hacker News

Claude Cowork and chat are now one Claude

claude.com

221–230 of 231 posts

Re: Claude Cowork and chat are now one Claude

#221

Earlier quoted context omitted.

This is a nightmare scenario to me. "Claude, prepare me a presentation on XYZ." I get to work, go straight to the meeting room, and pull up what it made to present. It's barely coherent nonsense. Lots of irrelevant details, buzz words, wrong charts or confusing phrasing. Obviously LLM output. I read it out. When I'm done, I get a question about one of Claude's incorrectly inferred details. The shame instantly kills m…

> It's barely coherent nonsense. Lots of irrelevant details, buzz words, wrong charts or confusing phrasing. Obviously LLM output. Plenty of that even before LLMs too though.

I'm attending a conference that I also attended last year, and it's night and day.

This year, a good 40% of workshop slides are fully LLM generated, incomprehensible, and almost not matching what the speaker is talking about at all. Last year, while there were some poor presentations, standards were much higher.

Re: Claude Cowork and chat are now one Claude

#222
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 harness, steering, etc. in the chat/reasoning products is so much better for this type of question (that doesn't require code as a primary substrate).

I had this same thought recently. Is it possible to 'recreate' ChatGPT/Claude Chat easily in Codex or Claude Code? I assume it would roughly be just swapping the system prompt. Anthropic seems to publish theirs but I don't think OpenAI does

https://platform.claude.com/docs/en/release-notes/system-pro...

Re: Claude Cowork and chat are now one Claude

#223
post #199

Earlier quoted context omitted.

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

Imagine the fear these people will feel walking in to a vacation planned by … a ROBOT!

Social media has fried some people’s brains so much that it is incredibly anxiety inducing to make many typically mundane or routine choices, for fear of missing / missing out on something.

Re: Claude Cowork and chat are now one Claude

#224

Earlier quoted context omitted.

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

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.

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.

Re: Claude Cowork and chat are now one Claude

#225

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 le…

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.

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.

Re: Claude Cowork and chat are now one Claude

#226

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 le…

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?

Re: Claude Cowork and chat are now one Claude

#227

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 le…

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.

Re: Claude Cowork and chat are now one Claude

#228

Earlier quoted context omitted.

Can you elaborate? How in the world would I interface with claude other than sending it messages?

For the abstract "you can do anything" product, you want an open ended interface, but if I'm, eg, renting a car, is a free form text box really the way to go? The rental company knows exactly what information they need from me before they'll rent me a car, so a free form text box so the computer can ask me questions one by one vs a traditional form, seems suboptimal.

But we're talking about Claude right? Not some bespoke app powered by AI? The interface cant only be wide enough to rent cars.

Re: Claude Cowork and chat are now one Claude

#229
post #165

Earlier quoted context omitted.

Can you elaborate? How in the world would I interface with claude other than sending it messages?

> How in the world would I interface with claude other than sending it messages? The protocol will of course be `text -> text` for the typical LLM (though some new models are structured, as we saw yesterday with Jev). Even so, the user doesn't need to be exposed to the protocol (almost ever). It's not like I'm crafting a POST request to send this form. There's a lot of room for window dressing, and I look at AI like…

So ... what?

Dictation? Neuralink thought-to-text?

Re: Claude Cowork and chat are now one Claude

#230
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.

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.

So what kind of interface would you prefer?
Post reply on HN