CLI coding Agent Newline Hell: Mapping Shift+Enter to Ctrl+Enter

HELL = Shift+Enter => Enter Your writing a long prompt in you CLI coding agent tooling and you want to create a blank line for a new point, code code block, etc., and you accidently type Shift+Enter ... The Terminal did it - The Terminal hit Enter If you've started using AI coding assistants (like aider, gpt-me, or open-code) directly in your terminal, you've likely run into a frustrating muscle memory clash around Shift+Enter . In web chats, Teams, Slack, and VSCode Code Assistants, Shift+Enter gives you a New Line , while Enter sends the message. However, most CLI coding agent tools follow the Terminal keyboard standards/behaviors (if you are reading this, the Terminal standards were more than likely written before you were born: ASCII(1963), and VT100(1978) aka boomer old school) : Key Command Key Operation Enter Submit Shift+Enter Submit Ctrl+Enter New Line Often the CLI coding agent will remap the key command based on its editor setting exposed by its /editor command. But if you'r