[BUG] TUI: cmd+shift+enter does not enqueue message on VSCode or Ghostty terminals [Claude Code, Opencode, Github Copilot] [Dev, Production]

[flora131]

Description

The cmd+shift+enter keyboard shortcut, which is intended to enqueue a message, does not function correctly on VSCode integrated terminal or Ghostty (or other standalone terminals). Instead of enqueuing the message, it either creates a new line (VSCode) or acts as a no-op (Ghostty). This affects all coding agents.

Affected Agents

• Claude Code
• Opencode
• Github Copilot

Environment

• Dev (bun run / local development)
• Production (binary build)

Reproduction Steps

1. Launch Atomic with any coding agent in either VSCode integrated terminal or Ghostty
2. Type a message in the input box
3. Press cmd+shift+enter to attempt to enqueue the message

Expected Behavior

The message should be enqueued for processing by the coding agent, similar to how message enqueuing works in supported terminals.

Actual Behavior

• VSCode integrated terminal: cmd+shift+enter creates a new line in the input box instead of enqueuing the message
• Ghostty / standalone terminals: cmd+shift+enter results in no visible change — it behaves like a no-op

The message is never enqueued in either case.

Additional Context

• Tested on: VSCode integrated terminal, Ghostty
• Affects all coding agents (Claude Code, Opencode, Github Copilot)
• The issue likely affects other standalone terminals beyond Ghostty as well
• Regular Enter (submit) still works as expected

Investigation Notes

IMPORTANT: Do NOT assume or speculate on the root cause in the initial filing. The purpose of this section is to capture raw observations only. Root cause analysis happens during investigation.

• VSCode terminal and Ghostty handle the key combination differently (newline vs no-op), suggesting they may report the key event differently to the TUI
• The key binding may not be properly captured or mapped in these terminal environments