[Bug] Cursor Movement Broken in Mac Terminal Input

[haltsir]

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

[]

[dicksontsai]

This does seem like a bug. However, you can always recover the text by using the shortcut Ctrl+_ to undo.

[github-actions[bot]]

Found 2 possible duplicate issues:

1. https://github.com/anthropics/claude-code/issues/1692
2. https://github.com/anthropics/claude-code/issues/6275

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[kopyl]

@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

1. Changes text
2. Goes to beginning of text instead of going to clicked place
3. It moves cursor character by character instead of doing it instantly

[haltsir]

@kopyl I think you misread @dicksontsai's comment.

[myarcana]

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

[github-actions[bot]]

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.

[haltsir]

Yes, the issue is still occurring.