[BUG] Desktop (WSL2): session disappears from sidebar right after its linked PR is merged
Summary
In the Claude desktop app (Code tab, WSL2 project), a session disappears from the sidebar session list shortly after a pull request linked to that session is merged. The session transcript is intact on disk and claude --resume <id> still works; only the sidebar entry is gone. It happened twice on the same day with two different sessions.
Environment
- Claude desktop app, Code tab, project on WSL2 (Linux 6.18 microsoft-standard-WSL2)
- Claude Code 2.1.283
- Repository hosted on GitHub Enterprise Server; PRs created and merged via
ghfrom inside the session
What happened
- Session A ran for ~1.5h, opened two PRs, then merged them from inside the session (
gh pr merge). The transcript's last entries arepr-link/bridge-sessionrecords written right after the merge. - Shortly after, session A was no longer in the sidebar list (not in Recents). I had to open a new session to find it.
- Session B (the new one, renamed by me) continued the work, opened and merged two more PRs the same way. Again, right after the last merge (
pr-linkfor the merged PR at the end of the transcript), session B vanished from the sidebar.
In both cases:
~/.claude/projects/<project>/<session-id>.jsonlis complete and still being referenced; no crash, no app restart on my side that I noticed.- The last records in the transcript are
agent-name,atis-latch,pr-link(merged PR),bridge-session,last-prompt,cost-state. - The session was idle (task finished) at the time it disappeared.
Expected
The session stays in the sidebar list until I archive or delete it. If merged-PR sessions are archived automatically by design, the app should say so and show where to find them (I could not find an archived view that listed them).
Actual
The session silently disappears from the list; the only way back is claude --resume <session-id> from a terminal or knowing the session id.
Possibly related
#83826, #93040, #75712 (sessions missing from the sidebar while data is intact). This report differs in that there was no crash or sleep/wake; the common trigger in both cases was merging the session's linked PR.