[BUG] Ctrl-B cursor movement stops working after using Ctrl-R or Ctrl-G
Status Fixed / completed
Reported on v2.1.29
Maintainer reply ✓ Yes — claude[bot]
Activity 5 comments · opened Feb 1, 2026 · closed Apr 20, 2026
💡 Likely answer: A maintainer (claude[bot], contributor)
responded on this thread — see the highlighted reply below.
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?
Ctrl-B (Emacs-style "move cursor backward") stops working after using Ctrl-R (history search) or Ctrl-G (open editor).
- Works fine immediately after startup
- After using Ctrl-R or Ctrl-G, Ctrl-B no longer moves the cursor backward
- Recoverable by resuming with
claude -c
What Should Happen?
The Emacs-style Ctrl-B cursor movement should work consistently, regardless of what operations were performed before.
Error Messages/Logs
None (no error output, the key simply doesn't respond)
Steps to Reproduce
- Open Terminal.app
- Run
bash --noprofile --norc - Run
npx @anthropic-ai/claude-code@2.1.29 - Type some text (e.g., "test")
- Press Ctrl-B → cursor moves left (OK)
- Press Ctrl-R to open history search, then ESC to close
- Press Ctrl-B → no response (NG)
Note: Ctrl-G (open external editor) also triggers the same issue.
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
2.1.2
Claude Code Version
2.1.29 (Claude Code)
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
- Last Working Version: 2.1.2
- First Broken Version: 2.1.3 (confirmed via bisect)
5 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
I was just trying to figure out why I can't move back, sounds about right.
That comment is just to say, this is happening to me too
This is a problem for me as well. Would be keen to have it fixed. At the moment I end up writing all my prompts outside Claude code and then paste them in or reference the prompts instead.
This issue was fixed as of version 2.1.83.
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.