Added Shift+Enter support for Windows TerminalPublic

Agent

Model

Claude Opus 4.5 (latest)

Started

Jan 16, 11:10 PM

Messages32

Downloads0

Summary

Closed, Completed

Understand
Reviewed README and identified limitation with Shift+Enter.
Understand
Understand
Researched Windows Terminal sendInput feature.
Understand
Build
Created workaround using sendInput with Kitty protocol escape sequence.
Build
Edit
Updated README with Windows Terminal configuration.
Edit
Verify
Committed and pushed the change.
Verify

in 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

ReadREADME.md

The README shows that Windows Terminal is explicitly documented as not supporting the Kitty keyboard protocol:

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.

So the current workaround is to use Ctrl+Enter instead of Shift+Enter on Windows Terminal.

The user is asking if there's a way to configure Windows Terminal to support Shift+Enter. Let me search for more information using Brave Search to see if there are any workarounds or configuration options.

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 helpful. Windows Terminal supports sendInput action that can send arbitrary ANSI escape sequences. Let me search specifically for how to configure Shift+Enter in Windows Terminal to send a custom escape sequence.

The Kitty keyboard protocol sends \x1b[13;2u for Shift+Enter. VS Code's config in the README shows exactly this:

So in Windows Terminal, we could potentially do:

Let me verify this is the right approach.

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 confirms Windows Terminal supports sendInput with custom escape sequences. The solution is to add a keybinding in Windows Terminal settings.json that sends the Kitty protocol escape sequence for Shift+Enter.

The Kitty keyboard protocol for Shift+Enter is:

\x1b[13;2u which in Windows Terminal JSON format is \u001b[13;2u

The user should add this to their Windows Terminal settings.json actions array:

This should work! We should update the README with this information.

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):

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?

ReadREADME.md40 lines

EditedREADME.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.