Summary

The TUI's persisted tab state (~/.local/state/opencode/latest/tui/tabs.json) is keyed by working directory only, not by the connected server. Two TUI clients running from the same directory against different servers (local background service vs. a remote server via --server) write their session ids into the same key, so each TUI's tab strip lists the other server's sessions. Clicking such a tab fails with "session not found" because the id does not exist on the connected server.

Environment

• opencode version: 2.2.1
• OS: Linux 7.1.8-200.fc44.x86_64
• Terminal: TERM_PROGRAM=ghostty, TERM=xterm-ghostty, COLORTERM=truecolor
• Shell: /usr/local/bin/zsh
• Install/channel: latest
• Active plugins: ./plugins/opencode-secrets, ./plugins/rtk, ./plugins/sound-notify, @tarquinen/opencode-dcp@latest

Reproduction

1. From directory D, launch the local TUI (opencode) — it connects to the shared background service. Open or create a session; it appears in the tab strip.
2. Make a second opencode server reachable (e.g. opencode serve --port 49380 on another host, forwarded with ssh -L 49380:127.0.0.1:49380 <host>).
3. From the SAME directory D, launch a second TUI against that server: opencode --server http://127.0.0.1:49380 -s <session-id-on-that-server>.
4. Both TUIs now list each other's session ids as tabs in their tab strips.
5. Click the foreign tab in either TUI → error: "session not found".

Expected Behavior

Tab state should be scoped per connected server (include the server identity in the tabs.json key), and a tab whose session id does not exist on the connected server should be dropped from the strip rather than erroring when clicked.

Actual Behavior

The tabs.json cwd key accumulates session ids from whichever TUI last wrote it, regardless of server; foreign ids render as tabs that error "session not found" on click. Reproduces consistently.

Additional Context

tabs.json shape (ids and paths trimmed):

{"global":{"tabs":[],"unread":{}},"cwd":{"/home/<user>/dir":{"tabs":[{"sessionID":"ses_...","title":"..."}],"unread":{}}}}

• The tabs.scope setting (cwd|global) only changes the grouping key; neither value is scoped by server.
• Workaround: launch each TUI against a different server from a distinct working directory so the cwd keys never collide and the tab strips stay isolated.