[BUG] Edits to terminal input not received entirely, leading to perceived typo

Resolved 💬 7 comments Opened Dec 2, 2025 by activtrak-dcox Closed Feb 6, 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?

I positioned my left hand on the keyboard incorrectly and tried to type /model, but actually input /mofrl.

Next, either (I can't remember)

  • Seeing the error I hit backspace 3 times and corrected it to /model, then completed the command and hit enter, OR
  • I added the model name: /mofrl opusplan. Then seeing the error I hit left-arrow to position the cursor after /mofrl, then hit backspace 3 times and corrected it to /model, and hit enter.

Claude Code reported that I'd entered a typo, /mofdel (see attached screenshot). I hit up-arrow to replay the prior command and hit enter again. Claude Code gave me a similar error message.

<img width="901" height="256" alt="Image" src="https://github.com/user-attachments/assets/c12ebcea-7d07-4898-bb06-7fc858e63511" />

Perhaps both the f and the backspace that should have deleted it were recorded in some input string buffer, such that when it's displayed, the f gets deleted in the output only?

This is Claude Code 2.0.56, with Node version v18.20.8, executed by PowerShell 5.1.26100.7019, in the Windows Terminal app, on Windows 11 24H2.

What Should Happen?

Backspaces during command input should be processed correctly, completely, in every case. The command processed should match the visible command.

Error Messages/Logs

Steps to Reproduce

as above

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.0.56 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

_No response_

View original on GitHub ↗

This issue has 7 comments on GitHub. Read the full discussion on GitHub ↗