in Ink defaults to , which terminates the process at the framework level before ever fires. Our double-press Ctrl+C logic (clear input → show hint → exit on second press) was unreachable.
Fix
Pass to . The TuiApp handler now owns the full Ctrl+C lifecycle:
Input non-empty → clear it
Input empty, first press → show Press
## Problem
in Ink defaults to , which terminates the process at the framework level before ever fires. Our double-press Ctrl+C logic (clear input → show hint → exit on second press) was unreachable.
## Fix
Pass to . The TuiApp handler now owns the full Ctrl+C lifecycle:
- Input non-empty → clear it
- Input empty, first press → show Press
Ink's render() defaults to exitOnCtrlC:true, which terminates the
process before useInput ever fires. Pass exitOnCtrlC:false so the
double-press logic in TuiApp (clear → hint → exit) takes effect.
Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
in Ink defaults to , which terminates the process at the framework level before ever fires. Our double-press Ctrl+C logic (clear input → show hint → exit on second press) was unreachable.
Fix
Pass to . The TuiApp handler now owns the full Ctrl+C lifecycle: