31–40 of 214 posts
To Anthropic: I hope you don't merge Claude Code and chat, I like keeping their memory separate.
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.
I guess this is a feature worth announcing
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
"Sure! And since you were asking me about lobsters yesterday, I'll make it red and seafood themed!"
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 t…
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.
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.
I see a version of that all the time and would never, ever do it.
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.
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.
Probably inevitable, but seems like a lot of disruption could happen there.
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.
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
Feels like the same "let us do _all_ of the thinking for you" messaging that Microsoft has with Copilot.