Honestly aside from the voice it uses you wouldn't notice a difference. Switching costs are low, vote with your wallet.
You need to use frontier models to understand where the puck is going, but also to use local ones for anything remotely sensitive.
I feel like Claude has some of the best UX, and hope this doesn’t dilute the experience.
Inside Claude code you’ve got cloud environments and local.
Let’s say as a normal desktop user you wanted to just automate something normal in your work, going to a website (maybe some internal app at your company) getting some data. Depending on what surface you used this will either not work, not work well (cowork), or work quite well but possibly be blocked because of bot controls (local Claude code) or again not work (cloud Claude code)
It was nuts. You can clearly tell these were different teams and products mashed into the same app. Super confusing for non technical users. Hopefully it’s a little better today
Genuinely curious.
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 for this type of question (that doesn't require code as a primary substrate).
Even as someone who mainlines like, 7 coding agents at all times, I regret that productivity fever will mean the regression of think-first-act-later AI UX.
Two years ago, I had no commute, and presentations were tedious ( i was NOT a good google slides user ), I kinda prefer this world for now
I see a version of that all the time and would never, ever do it.
There are several projects that injest coding sessions from lots of agents, but for the chat side I haven't found much, except replacements for Claude Desktop. Jan, for example.
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.
The moment someone figures out a new modality for LLMs is when we’ll see the next hockey stick.
Honestly, that fills me with fear. LLMs exist to make money to their companies, and said companies are not gonna turn around and say, "you know what, go are going to make an android for each elderly person, that can not only help them with their medications, but that can actually make their medications, tailored to their biologies." Instead, they are going to go for the low-handing fruit of "you know Bob, the guy who makes jokes in meetings but who is grumpy about delivery timelines? Well, we are going to make an android to replace Bob. MetalBob will make even better jokes. The blue model will be able to explain in excruciating level of detail why timelines aren't reasonable. The red model will walk through the cubicles with a whip to ensure everybody keeps working all the time, and nobody goes to pee."
"Please don't post shallow dismissals, especially of other people's work. A good critical comment teaches us something."
Claude's mobile app wouldn't show any Cowork initiated conversations, even if those conversations didn't leverage cowork specific features
Feels like the same "let us do _all_ of the thinking for you" messaging that Microsoft has with Copilot.
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.
"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 me.
This is a scenario I've seen play out with coworkers. Except that last part, instead of dying or owning up to the mistake of trusting LLM output they waffle. Their shame circuit is broken.
The downside of course is branching in got, but I usually don’t go of course more then a handful of tasks.
I had to engineer my own ticket management to keep opus on target. It’s been great for managing work, history, audit trails and commits are tagged with the task id.
I implemented subtasks to deal with the way Claude likes to stage its own objectives.
Then I made enforcement logic in the task manager so tasks can’t be closed out until reviewers have consensus on the same sha.
The adhd that is Anthropic demanded I build it and now I’m knocking out issues faster than Batman.
Probably inevitable, but seems like a lot of disruption could happen there.
I know this all sounds abstract. I've been mulling over it for the past year and it's very hard; and LLMs are super janky and inconsistent so it's 100% not trivial. So in some sense I understand why a lazy bottom-of-the-barrel "chat interface" has become the de facto standard.
But I don't agree that they aren't product-ized. There are many applications doing calls to LLMs behind the scenes and are hits, leveraging structured data very heavily and not having conversations with users at all. I would say that there is a predictable scope creep from executives to surface a conversational aspect though. We need to bring representation to that so we can point to some other best practice to push back
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 sessions, to who knows what's next.
I think the right interfaces for LLMs right now need to be very simple and easy to change/evolve. And chat still seems to be the best default solution.
Technology folks don’t really understand people and what they need.
This always happens. This is why woz needed Steve.
Steve Jobs is sorely missed tbh. For all the shit he got - he was a true visionary. He lived at the intersection of technology and the humanities… he kept preaching this. And now we are seeing why.
leohonexus•34m ago
bakies•25m ago
johen8•19m ago
"Sure! And since you were asking me about lobsters yesterday, I'll make it red and seafood themed!"
varispeed•19m ago
When casually a friend asks you to ask your Claude something about topic you chatted about earlier and then Claude brings back a secret you didn't want anyone to know yet.
Yes you can set up a project and then ask a question, but this is tedious.