YHK - yet another hacker news clone

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

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

I hope this doesn’t get confusing like ChatGPT made it.

I feel like Claude has some of the best UX, and hope this doesn’t dilute the experience.

A change for the better. The distinction made it unnecessarily complex for users. The ChatGPT desktop app inherited the same separation. Having to change between ChatGPT for day to day questions, to Codex for everything else always seemed too cumbersome.

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

These kinds of updates always have this romantic scenario of someone having Claude develop a presentation or something on their way to work between multiple devices, which actually feels a little sad and does not align with what happens in my life at all.

Is there a mature centralized platform, self hosted, that sync all your “AI stuff” across multiple devices? So regardless of the harness, it sync the api keys, providers, skills, and seasons for starters with other authenticated machines? Say you used codex on macos_1 through this platform, and later you used opencode on linux_3, it syncs everything to the new machine, no ssh to centralized machine, no git, none of that duct tape solutions, which they work but cumbersome.

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 guess this is a feature worth announcing

"We're not getting adoption in this thing that increases token spend and makes us more sticky what should we do?"

"Not sure man, we already tried opt-out instead of opt-in and that didn't work..."

"Oh, I know, what if ... what if we just glued them together and gave them no option?!"

I love this

Claude's mobile app wouldn't show any Cowork initiated conversations, even if those conversations didn't leverage cowork specific features