[BUG] claude code cli bug

### Preflight Checklist

- [x] I have searched [existing issues](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20state%3Aopen%20label%3Abug) 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?

If I wait for a task to take a long time, the screen saver activates. After a while, when I click the mouse to check the status, a prompt appears in the terminal input field that I did not type, and frequently, this is transmitted as input even though I haven't pressed Enter. This is a clear defect in the Claude Code CLI, and it is absurd that such a basic flaw still exists. I hope this defect is fixed as soon as possible.

### What Should Happen?

Only prompts where the user explicitly enters and presses should be sent.

### Error Messages/Logs

```shell
Not applicable
```

### Steps to Reproduce

Not applicable

### Claude Model

Sonnet (default)

### Is this a regression?

I don't know

### Last Working Version

_No response_

### Claude Code Version

2.1.239

### Platform

Other

### Operating System

Ubuntu/Debian Linux

### Terminal/Shell

VS Code integrated terminal

### Additional Information

Not applicable

No source file, test, or reproducible steps are identified. Start by reproducing the behavior in the VS Code integrated terminal on Ubuntu/Debian after the screensaver activates, then trace the CLI's terminal input handling; it is done when clicking to resume never sends untyped input and only an explicit Enter submits a prompt.

Written by the indexing model from the issue text.