In my experience non-technical folks quite dig the memory feature. For me that's kinda context poisoning as a service, but I know people that get value out of it (or at least strongly feel they do). Not sure how one would migrate that.

Regardless of whether there is value in chat history or not, for some people it is important.

Back in the day during the music streaming wars there were tons of "move your playlists from A to B" services. Streaming services could not hold on to customers because all their playlists were on there.

I'm sure that similar services will pop up for chatbots.

Also, you can always just ask your chatbot to generate a file with your chat history, given that it's all part of the context anyway.

I'm curious from the other direction, what are the conversations like if you feel they are easy to move?

Do you have the memory feature disabled? I have the feeling this in particular is doing absolutely loads behind the scene, e.g summarising all conversations and adding additional hidden context to every request.

I can start a new chat in the UI right now, ask it what my job is, what my current project is, how many kids I have, what car I drive etc. It'll know the answer already.

I think it's this conversation history - or maybe better yet if we think of it as this "relationship" - that people are saying is going to make it hard to move.

yeah the 'sessions' approach is probably going to be deprecated. one continuous chat is where it's at , perhaps with some bookmarks on the side for easy access

or perhaps a thread-based chat like reddit or HN, where you can branch off an older conversation with yourself