Repository navigation
Choose another directory to continue this session everytime i sleep windows #58000
Closed as duplicate
Description
Description
it happens everytime i sleep windows
Plugins
No response
OpenCode version
v2
Steps to reproduce
- open opencode
- sleep windows
- wake windows
- back to opened opencode agent
Screenshot
Operating System
Windows 11
Terminal
powershell
Activity
omandotkom commentedon Oct 22, 2026
opencode-agent commentedon Oct 22, 2026
Thanks for the report! I think this is a duplicate of #55250. When Windows sleeps, the connection to the OpenCode service drops. On wake the TUI reconnects and checks the session's directory again, and if one of those requests fails briefly, it wrongly shows "Session location unavailable — Choose another directory to continue this session". Your directory is fine; choosing the same directory again should get you back into the session.
A fix (#57594) has been merged into the development branch. It only shows this prompt when the server actually reports the directory as missing. It isn't in a release yet (it isn't in 2.1.2), so it should stop happening once you're on a version that includes it.
Possible duplicates and related issues, ordered by likelihood:
timecrashes Model.snapshot and shows false "Session location unavailable" #54943: a different cause (a plugin model that breaks model loading) that shows the same promptThe bot will close this issue as a duplicate in 1 day unless you reply explaining how your problem is different, for example if it keeps happening on a release that includes #57594.
opencode-agent commentedon Oct 23, 2026
We haven't heard back, so I'm closing this as a duplicate of #55250. That issue is the same false "Session location unavailable — Choose another directory to continue this session" prompt, which appears when the TUI reconnects, e.g. after Windows wakes from sleep. Until the fix is released, choosing the same directory again should get you back into the session.
The fix (#57594) has been merged into the development branch. It isn't in a release yet (it isn't in 2.1.2). Please follow #55250 for updates. If this keeps happening on a release that includes #57594, or your problem turns out to be different, reply here and it can be reopened. Thanks for reporting!