Good tidings!

After investigating, it appears this behavior is the same "session limit" one you've seen prior. This behavior manifests as a "Project Error" because the upstream provider is rejecting the API request with a "Bad Request" response (i.e., the context provided is either too large and/or malformed).

Just to confirm, your project code is still present when restarting the session in this scenario, but I completely understand that having a good session with the AI Agent being cut off is extremely frustrating. Per earlier discourse, this is a UX issue that we're improving in the next iteration of Shakespeare.

We're also looking to improve this interaction in the current iteration as well (with credit to our friend nostr:nprofile1qy2hwumn8ghj7etyv4hzumn0wd68ytnvv9hxgqgnwaehxw309ahx2amn9e6hg7r09ehkuegqyzl8xkxylegpfrxv4lqzags9mqq5tcjn3zd289vd4tagvdcy0jzqu2katrd for working on changes as we speak). You should see some noticeable improvement with this exact scenario soon.

For the immediate moment though, I've credited $30 to your account to hopefully account for the lost progress between these recent sessions.