TUI: allow configurable newline/send keybindings (Shift+Enter alternative to Ctrl+J)

[ThePlenkov]

Problem

In cagent run (TUI), newline currently falls back to Ctrl+J when keyboard enhancements are unavailable. In practice this can be problematic in terminal workflows (especially inside VS Code), where Ctrl+J is often already bound.

Request

Please support customizable input keybindings in TUI, specifically for send and insert newline actions.

At minimum, please provide an option to choose an alternative newline shortcut besides Ctrl+J when Shift+Enter is not detected/supported.

Why this matters

• Ctrl+J conflicts with common editor/terminal shortcuts
• Some terminal/tmux combinations don’t reliably deliver Shift+Enter
• Users need a practical fallback they can control

Suggested approaches

• Config option(s), e.g. in user config, for:
  • editor.send_key
  • editor.newline_key
• Optional env var override for quick testing
• Runtime command/help to display active bindings

Thanks!

[Pnkcaht]

Ok, I will see

[joshbarrington]

@Pnkcaht @krissetto Wondering if I can pick this up as seems to have gone stale?

@krissetto I will follow the general configurable keybindings approach outlined in the previous closed MR. Have you considered how you would like the user configuration to be driven? e.g. Im a wezterm user and it utilises a lua file.