Allow binding ctrl-t back to its traditional readline behavior
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
I long ago learned basic readline commands on the CLI and various claude TUI bindings conflict with those. Claude informs me that there is no way for me to edit claude keybindings to reinstate the normal shell/readline meaning of ctrl-t as "transpose characters". Please enhance the keybinding system to allow for this.
More generally, consider providing for as much of the common readline bindings (or at least common subset, e.g. what macOS has supported for decades) as you can.
I see that similar issues have been raised numerous times, and in every case there is a variety of user interest, but in every case either the bot auto-closes it or someone marks it as "complete" even though it clearly isn't.
Proposed Solution
Allow me to specify keybindings to make claude code less of a special snowflake.
Alternative Solutions
There do not appear to be real alternatives within claude, so the "honest answer" is use another product.
Priority
Low - Nice to have
Feature Category
Interactive mode (TUI)
Use Case Example
- I'm typing.
- I hit ctrl-t expecting it to do the thing it does everywhere else.
- Claude TUI does something different.
Additional Context
_No response_