tui: notifications fire in every attached TUI for a single session completion #59386

Summary

With multiple TUI clients attached to the same opencode server, a single session completion produces one desktop notification per attached TUI. The built-in opencode.notifications plugin has no notion of which client owns the session, so every client fires its own notification.

Environment

• opencode version: v2.1.4
• OS: Darwin 25.6.0 (darwin arm64)
• Terminal: iTerm.app (TERM=xterm-256color, COLORTERM=truecolor)
• Shell: /bin/zsh
• Install/channel: latest
• Active plugins: none configured (only a local worktrunk.ts plugin)

Reproduction

1. Open three opencode TUI instances in three terminal tabs, all attached to the same server.
2. In one instance, send a prompt and let the session complete.
3. Observe desktop notifications.

Expected Behavior

A single "Session done" notification (or one per TUI that actually owns/initiated the session).

Actual Behavior

All three TUIs fire the same "Session done" notification — three notifications for one completion.

Additional Context

The built-in opencode.notifications plugin registers a handler per TUI process:

t.data.on("session.execution.succeeded", (f) => c(f.data.sessionID))

and calls:

t.attention.notify({
  title: i ?? u?.title,
  message: r,
  notification: c ? false : { when: "blurred" },
  sound: { name: o, when: "always" }
})

Every TUI subscribes to the same shared server event stream, and the plugin does not check whether the session belongs to the current client. So each attached TUI emits its own notification. With when: "blurred", every terminal that is not focused notifies — N attached TUIs produce N notifications.

Workaround: launch secondary TUIs with OPENCODE_CLI_CONFIG_CONTENT='{"plugins":["-opencode.notifications"]}' to disable the plugin in those instances.

Frequency: consistently reproducible.