You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Restored archived session disappears from the frontend until OpenCode is restarted #29517
After I archive a session and then restore it, the frontend seems to enter an inconsistent state.
The restored session appears to be active or working on the page, but there is no corresponding session item in the sidebar/session list that I can select.
If I switch to another session, the restored session disappears from the frontend completely. I need to restart OpenCode before I can find it again.
Steps to reproduce
Open OpenCode.
Archive an existing session.
Restore the archived session.
Observe that the restored session appears to be active, but it does not appear properly in the session list.
Switch to another session.
The restored session disappears from the frontend until OpenCode is restarted.
Expected behavior
After restoring an archived session:
The session should appear in the session list immediately.
The restored session should be selectable.
Switching to another session should not make the restored session disappear.
Restarting OpenCode should not be required.
Actual behavior
The restored session seems to be partially loaded, but it does not appear properly in the frontend session list. After switching sessions, it cannot be found again until I restart OpenCode.
Additional suggestion
It may also be helpful to add a confirmation dialog before archiving a session, because it is easy to trigger the archive action accidentally and archived sessions can be hard to find again.
For example:
Are you sure you want to archive this session?
Notes
I noticed the permission prompt issue may already be tracked in another issue, so I am keeping this report focused on the archived session restore behavior.
Sorry if some of my terminology is inaccurate. I am not very familiar with the implementation details, but I hope this report is helpful.
No issue template was used. Please resubmit using one of the three required templates: Bug Report, Feature Request (title must start with [FEATURE]:), or Question. Each template has required fields that must be filled in.
This issue combines a feature request (confirmation dialog before archiving) and a bug report (restored session not appearing in sidebar). Please split these into separate issues using the appropriate templates.
Please edit this issue to address the above within 2 hours, or it will be automatically closed.
This issue might be a duplicate of existing issues. Please check:
changed the title [-]Archived sessions may disappear from the frontend after being restored until restart[/-][+]Restored archived session disappears from the frontend until OpenCode is restarted[/+]on May 27, 2026
Thank you for updating the issue! It now meets our contributing guidelines and has all the required information. We appreciate the detailed steps to reproduce and system information.
Activity
github-actions commentedon May 27, 2026
This issue doesn't fully meet our contributing guidelines.
What needs to be fixed:
[FEATURE]:), or Question. Each template has required fields that must be filled in.Please edit this issue to address the above within 2 hours, or it will be automatically closed.
This issue might be a duplicate of existing issues. Please check:
If you believe this was flagged incorrectly, please let a maintainer know.
[-]Archived sessions may disappear from the frontend after being restored until restart[/-][+]Restored archived session disappears from the frontend until OpenCode is restarted[/+]github-actions commentedon May 27, 2026
Thank you for updating the issue! It now meets our contributing guidelines and has all the required information. We appreciate the detailed steps to reproduce and system information.
github-actions commentedon Jul 27, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.