SIGUSR2 theme reload interrupts an in-flight session

Description

Changing the desktop theme while opencode is working interrupts the run.

Omarchy signals opencode on every theme change — omarchy-restart-opencode runs killall -SIGUSR2 opencode. In the TUI, SIGUSR2 calls the worker's reload RPC (packages/opencode/src/cli/cmd/tui.ts:216), and that reload invalidates config and then disposes every instance (packages/opencode/src/cli/tui/worker.ts:63). Disposing an instance cancels the session runners it owns, so whatever is in flight — a model stream or a shell command — is aborted.

The theme itself does not depend on that reload: the TUI re-detects the terminal palette and re-scans theme files from its own SIGUSR2 handler in packages/tui/src/context/theme.tsx.

OpenCode version

1.18.18, also reproduced on dev @ e23586af2

Steps to reproduce

1. Start the TUI.
2. Start something long-running, e.g. !sleep 45.
3. From another terminal, kill -SIGUSR2 <tui pid> (this is what an Omarchy theme switch does).
4. The run is aborted immediately with "User aborted the command", and the log shows disposing all instances within milliseconds of the signal.

Operating System

Arch Linux (Omarchy), Hyprland

Terminal

foot