TUI ! bash commands should surface non-zero exit codes #31935

Description

When running a direct shell command via the TUI's ! prefix (Bash commands), there is no visible warning or indicator when the command exits with a non-zero code. The exit code is silently absorbed.

Current behavior

User types !some-command in the TUI, it exits with code 1, and the user has no way to know the command failed unless they read every line of the tool output (which may be truncated). The output does not prominently flag the failure.

Expected behavior

When a ! bash command exits with a non-zero code, the output should include a visible warning, e.g.:

[WARNING] Command exited with code 1

This should be appended to or prepended to the tool output so the user can see it immediately.

Why this matters

• ! commands are direct user input — the user explicitly asked to run this command
• Users cannot tell if the command succeeded or failed without reading every line of output
• Long sessions with many commands make it easy to miss silent failures
• The output is added to the conversation as a tool result, but the non-zero exit code is not surfaced

Context

The ! prefix is documented under "Bash commands" in the TUI docs: https://opencode.ai/docs/tui/ — "Start a message with ! to run a shell command. The output of the command is added to the conversation as a tool result."

Related

• opencode run -s <missing-session-id> exits 0 with zero stdout instead of failing #27559 — opencode run -s exits 0 on missing session (similar class of silent failure)