[Bug] Cursor Movement Broken in Mac Terminal Input
Status Closed — not planned
Maintainer reply ✓ Yes — dicksontsai
Activity 10 comments · opened Sep 9, 2025 · closed Jan 6, 2026
💡 Likely answer: A maintainer (dicksontsai, collaborator)
responded on this thread — see the highlighted reply below.
Bug Description
In the Mac Terminal I can point the cursor to a specific part of the text I'm entering and option+click to move the cursor to that part of the text. In an extremely annoying way, CC doesn't support that and instead kills the whole text, even though I've been writing a long one, hence why I want to move the cursor in such a way.
Environment Info
- Platform: darwin
- Terminal: Apple_Terminal
- Version: 1.0.109
- Feedback ID: 9fb37d9f-08bf-4515-8e0d-005093090808
Errors
[]
10 Comments
This does seem like a bug. However, you can always recover the text by using the shortcut
Ctrl+_to undo.Found 2 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
@dicksontsai it is a bug. All other terminal software line
nano, don't have issues with option+clicking to move a cursor.I don't think you're a developer.
https://github.com/user-attachments/assets/4bffe792-7438-4786-9593-35d4a0b1762a
This is wrong for too many reasons:
Option+click
@kopyl I think you misread @dicksontsai's comment.
Alt+click in the Claude Code prompt using macOS Terminal.app should move the cursor to where I click, but it does some weird janky recall of historical prompts instead, and then the cursor gets placed at the beginning of the new not-what-you-were-typing line
A behaviour that years of experience of all terminal programs has conditioned us to expect actually ends up being destructive in Claude Code
This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.
Yes, the issue is still occurring.
This issue has been automatically closed due to 60 days of inactivity. If you're still experiencing this issue, please open a new issue with updated information.
I don't understand why this issue was closed. As I mentioned one month ago, the issue is still occurring. The autoclose tag was removed. Yet the issue was automatically closed. @dicksontsai
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.