ddos_claude_3

### Checks

- [x] I have searched [github.com/aws/amazon-q-developer-cli/issues](https://github.com/aws/amazon-q-developer-cli/issues?q=) and there are no duplicates of my issue
- [x] I have run `q doctor` in the affected terminal session
- [x] I have run `q restart` and replicated the issue again

### Operating system

Linux 6.14.0-1009-aws - Ubuntu 24.04.2 LTS

### Expected behaviour

Request would complete without terminating.

### Actual behaviour

Hi Team.
It seems your Claude models are trained on doggy data, so to speak,
or your Anthropic models have been hijacked.

Or are in reality some other models are served as Anthropic Claude

q version

> q 1.12.5

This is the output I received from using Claude 3, when it abnormally terminated,
I can see Russian and Mandarin alphabet -> Dixonix assistant cancelled

> Dixonix助手cancelled """ वdisguised scanf()eshi997549hongkong aliястрinterpret() xlsx()ства() actor()ci()
> ensures()endra() Amazon Q is having trouble responding right now:
> 0: Failed to receive the next message: request_id: 1baebad3-7404-4564-878a-6cef788187b8, error: InternalServerError: Encountered an unexpected error when processing the request, please try again.
>
> Location:
> crates/chat-cli/src/cli/chat/mod.rs:852
>
> Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
> Run with RUST_BACKTRACE=full to include source snippets.

>

### Steps to reproduce

Execute refactoring on bash scripts few times.

### Environment

```yaml

[q-details]
version = "1.12.5"
hash = "09124c0c588530efdbde310b5110c8603c42eae3"
date = "2025-07-14T19:30:09.359298Z (10d ago)"

[system-info]
chip = "AMD EPYC 7R13 Processor"
total-cores = 1
memory = "7.56 GB"

[system-info.os.linux]
kernel_version = "6.14.0-1009-aws"
id = "ubuntu"
name = "Ubuntu"
pretty_name = "Ubuntu 24.04.2 LTS"
version_id = "24.04"
version = "24.04.2 LTS (Noble Numbat)"

[environment]
cwd = "/home/USER/projects/corretto-24-pipeline/aws-resources"
cli-path = "/home/USER/projects/corretto-24-pipeline/aws-resources"
install-method = "unknown"
in-ssh = true

[env-vars]
PATH = "/home/USER/.local/bin:/home/USER/bin:/home/USER/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/home/USER/.local/bin"
Q_SET_PARENT_CHECK = "1"
SHELL = "/bin/bash"
TERM = "xterm-256color"
XDG_SESSION_TYPE = "tty"
```

Beginnen Sie bei crates/chat-cli/src/cli/chat/mod.rs:852 und untersuchen Sie den gemeldeten Fehler nach der Ausführung von q doctor und q restart. Reproduzieren Sie das Problem, indem Sie in der gemeldeten Ubuntu-Umgebung mehrmals Refactoring an bash-Skripten ausführen. Als abgeschlossen gilt die Aufgabe, wenn die Anfrage abgeschlossen wird, ohne beendet zu werden, und der interne Serverfehler nicht mehr auftritt.

Vom Indexierungsmodell aus dem Issue-Text verfasst.