Skip to content

fix(tui): only close session tabs when the session is missing - #50826

Closed
rekram1-node wants to merge 2 commits into
devfrom
keep-tabs-reconnect
Closed

rekram1-node wants to merge 2 commits into
devfrom
keep-tabs-reconnect

Conversation

@rekram1-node

@rekram1-node rekram1-node commented Sep 23, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

The session route closed its tab whenever reloading the session failed. That includes a server that is still starting, one that is shutting down, or one that can't be reached at all. Because the TUI reloads the open session every time its event stream reconnects, restarting or updating the background service while TUIs are open could close tabs: each short-lived reconnect failed the reload, closed the current tab, and moved to the previous tab, which could then fail the same way.

Now the tab closes, or the TUI goes home when tabs are disabled, only when the server returns SessionNotFoundError. Other failures still show the error toast but keep the session open, and the next reconnect reloads it.

Evidence

In the service log from a real restart, TUI requests for open sessions got 503 from a service that was still starting, and those tabs disappeared from tabs.json. No tab-close tool calls, snoozes, or session deletions account for them.

Verification

  • Against the running service, a missing session ID gets 404 {"_tag":"SessionNotFoundError",...}, and the generated client's error passes isSessionNotFoundError. An existing session loads normally. An unreachable server throws ClientError("Transport"), which does not pass it.
  • bun run check

@thdxr
thdxr changed the base branch from v2 to dev October 10, 2026 19:15
@github-actions

Copy link
Copy Markdown
Contributor

Automated PR Cleanup

Thank you for contributing to opencode.

Due to the high volume of PRs from users and AI agents, we periodically close older PRs using automated criteria so maintainers can focus review time on the most active and community-supported contributions.

This PR was closed because it matched the following cleanup criteria:

  • The PR was created more than 1 month ago
  • The PR had fewer than 2 positive reactions
  • Positive reactions are counted as thumbs-up, heart, celebration, or rocket reactions on the PR

PRs created within the last month are not affected by this cleanup.

If you believe this PR was closed incorrectly, or if you are still actively working on it, please leave a comment explaining why it should be reopened. A maintainer can review and reopen it if appropriate.

Thanks again for taking the time to contribute.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant