Reviewed README and identified limitation with Shift+Enter.
UnderstandResearched Windows Terminal sendInput feature.
UnderstandCreated workaround using sendInput with Kitty protocol escape sequence.
BuildUpdated README with Windows Terminal configuration.
EditCommitted and pushed the change.
Verifyin windows terminal using git bash or any other shell really, shift + enter is not recognized by our shit.
could any of this help? can use brave search if you want to do more research on how we can configure shift + enter in windows terminal. read @packages/coding-agent/README.md on setups for other terminals
The README already documents this limitation:
Windows Terminal: Does not support the Kitty keyboard protocol. Shift+Enter cannot be distinguished from Enter. Use Ctrl+Enter for multi-line input instead. All other keybindings work correctly.
Let me search for potential workarounds:
This is promising. Windows Terminal supports sendInput with custom escape sequences. The Kitty protocol for Shift+Enter is \x1b[13;2u (which the VS Code config in our README already shows as \u001b[13;2u).
Let me search for confirmation this works:
This can be fixed. Windows Terminal supports sendInput to send custom escape sequences. The Kitty protocol for Shift+Enter is \x1b[13;2u.
Solution for Windows Terminal users:
Add to Windows Terminal settings.json (open with Ctrl+Shift+, or Settings → Open JSON file):
{ "actions": [ { "command": { "action": "sendInput", "input": "\u001b[13;2u" }, "keys": "shift+enter" } ]}This sends the Kitty keyboard protocol escape sequence that pi expects. Should work with Git Bash, PowerShell, or any shell in Windows Terminal.
Want me to update the README to replace the "use Ctrl+Enter" workaround with this actual fix?
can you add that to the README.md?
Done. Updated the Windows Terminal section with the sendInput configuration that sends the Kitty protocol escape sequence for Shift+Enter.
cool, commit and push
Done. Committed and pushed f3710693.
{ "actions": [ { "command": { "action": "sendInput", "input": "\u001b[13;2u" }, "keys": "shift+enter" } ]}