[BUG] Control-c stopping claude prior to clearing input text
Status Closed — not planned
Reported on v2.1.5
Maintainer reply None cached
Workaround ✓ Mentioned in thread ↓
Activity 12 comments · opened Jan 12, 2026 · closed Feb 28, 2026
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
Previously, you could hit control-c and it would clear the input prior to stopping the agent. Same with escape.
Now when you do this, it stops claude unexpectedly, and then you can clear text then you have to tell claude oops continue
What Should Happen?
It should only stop claude if the input box is already clear, and then another time wouold trigger an exit to shell
Error Messages/Logs
Steps to Reproduce
- get claude to start doing something
- type some text
- hit control-c while claude is still "bopping..." or whatever
- claude stops unexpectedly, rather than clearing input.
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
1.96
Claude Code Version
2.1.5
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
iTerm2
Additional Information
_No response_
12 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Ctrl+C did not used to interrupt claude at all and I preferred that behavior. Escape for interrupt, ctrl+c for clearing the input buffer and exiting. Clear and logical semantics. But with how much behavior they're cramming into that simple looking interface, the complexity is beginning to creep in.
ctrl + c now is broken in my sessions often where I can't do anything but close my whole buffer. Also, if I hit ctrl + c as they designed it sometimes gets in a state where it does nothing at all.
Why is it
ctrl + cto clear you input, but double clickctrl + c + cto close the current claude session in a terminal window? The amount of times I have accidentally lost hours of a session because of this stupid design choice is inconceivable.Same here. Ctrl+C was clearing the input before now it does nothing (and pressing it twice exits the CLI)
Fyi - pressing
ctrl+Sis sort of a workaround (it stashes the input)OK you can actually just press double Escape and it clears the input
I have also noticed recently that this seems to have changed.
As a workaround for others reading this, ctrl+U clears from the cursor to the start of the line, and ctrl+K clear from the cursor to the end (standard terminal bindings, not claude-specific)
I noticed too! I understand that ctrl+c is usually used to interrupt the running program, so the change makes sense.
But often I type a prompt that i want to clear out, and i can no longer do this without stopping Claude too.
in the past we could press "down" arrow key to clear out the typed text, sort of like "up" arrow for history. pressing down with a typed prompt cleared it out. but now, the down arrow goes down to select the "background tasks" etc below the prompt.
+1
how to just clear text?
Esc -> Clears text AND interrupts
Ctrl+C -> Clears text AND interrupts
Closing for now — inactive for too long. Please open a new issue if this is still relevant.
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.