21–30 of 214 posts
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.
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
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…
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…
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.
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.
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.
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.
Do you know that you can have multiple chats at the same time?
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.