Problem
Standard terminal keybinds Ctrl+P (previous history) and Ctrl+N (next history) are not mapped in the TUI input. Only Up / Down arrow keys work for history navigation. There is also no /terminal command to configure terminal behavior or keybind presets.
Expected behavior
Ctrl+P should navigate to the previous input history entry (same as Up arrow)
Ctrl+N should navigate to the next input history entry (same as Down arrow)
- These are readline/emacs-standard keybindings that terminal-native users expect by default
Current behavior
Ctrl+P and Ctrl+N do nothing
- Only
Up / Down arrows work for history (documented in keybinds page)
- The keybinds are customizable via config, but
Ctrl+P / Ctrl+N should be defaults — not something users have to discover and manually configure
Additional context
- The keybinds docs list 85+ configurable keybindings but omit
Ctrl+P / Ctrl+N from defaults
- No
/terminal command exists in the built-in commands to adjust terminal behavior presets (e.g., emacs-style vs vi-style input)
Problem
Standard terminal keybinds
Ctrl+P(previous history) andCtrl+N(next history) are not mapped in the TUI input. OnlyUp/Downarrow keys work for history navigation. There is also no/terminalcommand to configure terminal behavior or keybind presets.Expected behavior
Ctrl+Pshould navigate to the previous input history entry (same asUparrow)Ctrl+Nshould navigate to the next input history entry (same asDownarrow)Current behavior
Ctrl+PandCtrl+Ndo nothingUp/Downarrows work for history (documented in keybinds page)Ctrl+P/Ctrl+Nshould be defaults — not something users have to discover and manually configureAdditional context
Ctrl+P/Ctrl+Nfrom defaults/terminalcommand exists in the built-in commands to adjust terminal behavior presets (e.g., emacs-style vs vi-style input)