[BUG] Desktop app: clicking a task notification opens the Code session but the Chat/Code tab selector stays on Chat

Environment

• Claude Code: 2.1.241 (desktop app)
• OS: macOS 26.6 (Build 25G72), Apple Silicon
• Sessions involved: one Chat session (foreground) + one Code session (background, SSH remote workspace)

Description

When a background Code session posts a desktop notification (e.g. "Claude finished a task") and the
notification is clicked while the app is showing the Chat tab, the app does navigate to and display
the correct Code session — but the Chat/Code tab selector in the top-left of the window is not
updated. It stays highlighted on "Chat".

So the window content and the tab indicator disagree: the Code session is on screen, while the app's
own navigation state still claims Chat is the active tab.

Steps to reproduce

1. Start a long-running task in a Code session.
2. While it runs, switch to the Chat tab and start/continue a conversation there.
3. Move the app out of the foreground (or just leave the Chat tab active) until the Code session

emits a desktop notification banner — typically on task completion or when it needs input.

1. Click the notification banner.

Expected behavior

Clicking the notification brings the Code session to the foreground and the top-left Chat/Code
tab selector switches to "Code", matching what is displayed.

Actual behavior

The Code session is displayed, but the top-left tab selector remains selected on "Chat".
The indicator only corrects itself after manually clicking the tab selector.

Impact

The tab selector is the primary affordance for switching back and forth between Chat and Code.
When it is out of sync with the displayed session, it is unclear which surface is actually active,
and clicking the (already-highlighted) "Chat" tab to get back to the conversation behaves
unexpectedly relative to what the indicator shows.

Notes

Notification banner as received (task-complete notification from a Code session):
[eng-quiz] invalid token 갱신 — Claude finished a task

Related issues

• #86281 — clicking a notification focuses the main window instead of the window hosting the session.

Related but distinct: that one is about which window gets focus; this one is about the
in-window Chat/Code tab indicator not following the navigation the notification performed.

• #89778 — sessions that finish while the Code tab is unfocused are silently marked read

(same "Code tab unfocused" area, different symptom).