Couldn't select session, then sessions were overwritten by blank sessions

[lawrencecushman]

Describe the bug

After taking the latest copilot update I tried using --resume to continue with one of my sessions. I hit enter on the session picker, and nothing happened - the session didn't resume. I hit enter a few more times before exiting copilot to restart it and try again to find this:

When I was hitting enter, all the sessions I had in my session history were being overwritten by blank sessions

Other notes:
I had run copilot using nvm exec 22 copilot --resume. This was the first time I had prepended nvm exec 22, since I got an error the latest copilot required node 22

Affected version

0.0.348, Commit: 946b5dc

Steps to reproduce the behavior

nvm exec 22 copilot --resume - observe that when selecting a session, nothing happens

Expected behavior

Either the session should resume, or an error should appear. Losing the sessions entirely is catastrophic data loss. This bug aside, it would be nice to be able to save any number of sessions as 8 is incredibly limiting

Additional context

No response

[lawrencecushman]

Is there any way to recover sessions outside the 8 presented by copilot?

[sergiou87]

Sorry about that!! I was able to reproduce this on 0.0.348, but not on 0.0.349. Could you double check it works fine on that version? 🙏

Is there any way to recover sessions outside the 8 presented by copilot?

If you have the session ID, you can do --resume <sessionID> 😅

[RyanHecht]

I believe our many session refactors since this issue was opened have fixed this bug. Let us know if you encounter similar problems in newer versions by opening a new issue!