NeilandOrca 90d0d933ef fix(terminal): advertise kitty keyboard protocol for Shift+Enter ...

Orca's terminal already encodes Shift+Enter as the kitty CSI-u sequence
`\x1b[13;2u`, but without `vtExtensions.kittyKeyboard` xterm.js never
answers the `CSI ? u` probe. CLIs that gate enhanced input on that
handshake (Claude Code, Codex, etc.) therefore drop the extended bytes
and treat Shift+Enter as a plain Enter — most visibly when running
inside tmux, which strips extended-key encodings by default.

- Enable `vtExtensions.kittyKeyboard` in the default terminal options
  (matches VS Code's xtermTerminal).
- Lock in the flag with a regression test in pane-lifecycle.test.ts.
- Add docs/terminal-extended-keys.md explaining the Orca side and the
  tmux-side `set -s extended-keys on` + `terminal-features xterm*:extkeys`
  users need for nested Shift+Enter to reach a CLI.

Verified end-to-end in Electron: `cat -v` + Shift+Enter now prints
`^[[13;2u`, and `printf '\e[?u'` elicits the expected `CSI ? 0 u` reply
from xterm.js.

Co-authored-by: Orca <help@stably.ai>

2026-04-28 23:39:05 -07:00

..

cli

feat(orchestration): add inter-agent orchestration system (#1188)

2026-04-28 12:21:31 -07:00

main

Prefer upstream remotes for GitHub issue tasks (#1076)

2026-04-28 17:01:03 -07:00

preload

Prefer upstream remotes for GitHub issue tasks (#1076)

2026-04-28 17:01:03 -07:00

relay

refactor(search): share rg/git-grep logic between main and relay (#1157)

2026-04-27 00:06:00 -07:00

renderer

fix(terminal): advertise kitty keyboard protocol for Shift+Enter

2026-04-28 23:39:05 -07:00

shared

fix(mac): request media permissions dynamically (#1233)

2026-04-28 16:18:22 -07:00