Operating system
Windows
Orca version
No response
Details
The Projects sidebar keeps getting out of sync with what is actually in orca-data.json. Two things go wrong, sometimes one at a time, sometimes together: a worktree gets drawn under a different project's header than the one it belongs to and a project header goes completely missing even though the accessibility tree still has it in the right place with its worktree and session underneath.
Nothing gets lost. The data file is always correct when I check it, and the sessions keep running in the background. The practical problem is that the sidebar is the only way to get back to a session. If a project with a running agent disappears while I am working in a different project, I have no way to switch back to it. I can see in the Agent Dashboard that it is still working, I just cannot open it.
This has happened several times over the past few weeks, with different projects, and I have not found a reliable trigger. It shows up after normal use, not after any particular action. Below is the most recent instance, where I actually captured what was going on in the data file and the accessibility tree as it happened.
Operating system
Windows
Orca version
No response
Details
The Projects sidebar keeps getting out of sync with what is actually in orca-data.json. Two things go wrong, sometimes one at a time, sometimes together: a worktree gets drawn under a different project's header than the one it belongs to and a project header goes completely missing even though the accessibility tree still has it in the right place with its worktree and session underneath.
Nothing gets lost. The data file is always correct when I check it, and the sessions keep running in the background. The practical problem is that the sidebar is the only way to get back to a session. If a project with a running agent disappears while I am working in a different project, I have no way to switch back to it. I can see in the Agent Dashboard that it is still working, I just cannot open it.
This has happened several times over the past few weeks, with different projects, and I have not found a reliable trigger. It shows up after normal use, not after any particular action. Below is the most recent instance, where I actually captured what was going on in the data file and the accessibility tree as it happened.