Thank you for sharing!

There are two probable causes for this behavior. There is a bug I'm currently investigating regarding the service provider being restarted and affecting any pending/active sessions, which could be related.

The other behavior, which is more so 'expected', is that after interacting with an agent for a long duration, it will reach a limit within its context window. The only way to move forward from that state (at this time) is starting a new session (similar to what you have described).

This is a long-term item that I believe is being investigated, and the eventual outcome would ideally be that the user doesn't have to worry or handle any issues related to the context window being hit.

That being said, to your note, the actual project code is unchanged even if that immediate session is lost; the quickest way forward is to start your chat with "we were working with X/Y/Z feature, please review our progress in the codebase and continue".