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> |
||
|---|---|---|
| .. | ||
| assets | ||
| design | ||
| superpowers | ||
| README.es.md | ||
| README.ja.md | ||
| README.md | ||
| README.zh-CN.md | ||
| back-button-tasks-page.md | ||
| cmd-j-scoped-jump-palette-plan.md | ||
| codex-account-switching-design.md | ||
| create-from-start-field.md | ||
| design-379.md | ||
| design-preserve-scroll-position.md | ||
| file-explorer-external-drop.md | ||
| focus-follows-mouse-design.md | ||
| focus-follows-mouse-plan.md | ||
| performance-audit.md | ||
| performance-implementation-plan.md | ||
| preload-typecheck-hole.md | ||
| quickly-jump-to-worktree.md | ||
| remote-folder-picker-redesign.md | ||
| split-groups-rollout-pr1.md | ||
| split-groups-rollout-pr2.md | ||
| split-groups-rollout-pr3.md | ||
| split-groups-rollout-pr4.md | ||
| split-groups-rollout-pr5.md | ||
| split-groups-rollout-pr6.md | ||
| tab-group-model-follow-up.md | ||
| term-shortcut-fix.md | ||
| terminal-extended-keys.md | ||
README.md
Orca CLI Docs
Keep this folder focused on the durable references for Orca's public CLI and runtime model.
Keep These Docs
orca-cli-focused-v1-status.md- What is actually implemented and intentionally in scope now.
orca-cli-v1-spec.md- The public CLI contract, selector grammar, JSON envelope, and command semantics.
orca-runtime-layer-design.md- Why the runtime layer exists and which boundaries it owns.
orca-cli-bundled-distribution.md- How the bundled desktop-app distribution and PATH registration model works.
Why The Folder Is Small
Earlier design and implementation work produced several planning and evaluation docs. Those were useful while the feature was taking shape, but they were intentionally removed once the implementation converged so future readers are not forced to choose between multiple overlapping sources of truth.