Error at offset 0: unexpected token '<'. Expected one of '{', '[', '"', 'null', 'true', 'false', <number>

### 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.6.87.2-microsoft-standard-WSL2 - Ubuntu 24.04.4 LTS

### Expected behaviour

get a proper answer

### Actual behaviour

1% > hi

⠋ Thinking...
WARNING: Retry #3, retrying within 5s..
Kiro is having trouble responding right now:
0: Failed to send the request: An unknown error occurred: service error
1: An unknown error occurred: service error
2: unhandled error
3: service error
4: unhandled error
5: Error at offset 0: unexpected token '<'. Expected one of '{', '[', '"', 'null', 'true', 'false',

Location:
crates/chat-cli/src/cli/chat/mod.rs:1717

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.

### Steps to reproduce

~$ kiro-cli chat --classic
✓ XXXXXXXXXXXXX loaded in 2.13 s

⠀⠀⠀⠀⠀⠀⠀
⠀⠀⠀⠀⠀⠀⠀ ⢀⣴⣶⣶⣦⡀⠀⠀⠀⢀⣴⣶⣦⣄⡀⠀⠀⢀⣴⣶⣶⣦⡀⠀⠀⢀⣴⣶⣶⣶⣶⣶⣶⣶⣶⣶⣦⣄⡀⠀⠀⠀⠀⠀⠀⢀⣠⣴⣶⣶⣶⣶⣶⣦⣄⡀⠀⠀⠀⠀⠀⠀⠀⠀⠀
⠀⠀⠀⠀⠀⠀⠀ ⢰⣿⠋⠁⠈⠙⣿⡆⠀⢀⣾⡿⠁⠀⠈⢻⡆⢰⣿⠋⠁⠈⠙⣿⡆⢰⣿⠋⠁⠀⠀⠀⠀⠀⠀⠀⠀⠈⠙⠻⣦⠀⠀⠀⠀⣴⡿⠟⠋⠁⠀⠀⠀⠈⠙⠻⢿⣦⠀⠀⠀⠀⠀⠀⠀
⠀⠀⠀⠀⠀⠀⠀ ⢸⣿⠀⠀⠀⠀⣿⣇⣴⡿⠋⠀⠀⠀⢀⣼⠇⢸⣿⠀⠀⠀⠀⣿⡇⢸⣿⠀⠀⠀⢠⣤⣤⣤⣤⣄⠀⠀⠀⠀⣿⡆⠀⠀⣼⡟⠀⠀⠀⠀⣀⣀⣀⠀⠀⠀⠀⢻⣧⠀⠀⠀⠀⠀
⠀⠀⠀⠀⠀⠀⠀ ⢸⣿⠀⠀⠀⠀⣿⡿⠋⠀⠀⠀⢀⣾⡿⠁⠀⢸⣿⠀⠀⠀⠀⣿⡇⢸⣿⠀⠀⠀⢸⣿⠉⠉⠉⣿⡇⠀⠀⠀⣿⡇⠀⣼⡟⠀⠀⠀⣰⡿⠟⠛⠻⢿⣆⠀⠀⠀⢻⣧⠀⠀⠀⠀
⠀⠀⠀⠀⠀⠀⠀ ⢸⣿⠀⠀⠀⠀⠙⠁⠀⠀⢀⣼⡟⠁⠀⠀⠀⢸⣿⠀⠀⠀⠀⣿⡇⢸⣿⠀⠀⠀⢸⣿⣶⣶⡶⠋⠀⠀⠀⠀⣿⠇⢰⣿⠀⠀⠀⢰⣿⠀⠀⠀⠀⠀⣿⡆⠀⠀⠀⣿⡆
⠀⠀⠀⠀⠀⠀⠀ ⢸⣿⠀⠀⠀⠀⠀⠀⠀⠀⠹⣷⡀⠀⠀⠀⠀⢸⣿⠀⠀⠀⠀⣿⡇⢸⣿⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⣠⣼⠟⠀⢸⣿⠀⠀⠀⢸⣿⠀⠀⠀⠀⠀⣿⡇⠀⠀⠀⣿⡇
⠀⠀⠀⠀⠀⠀⠀ ⢸⣿⠀⠀⠀⠀⠀⣠⡀⠀⠀⠹⣷⡄⠀⠀⠀⢸⣿⠀⠀⠀⠀⣿⡇⢸⣿⠀⠀⠀⠀⣤⣄⠀⠀⠀⠀⠹⣿⡅⠀⠀⠸⣿⠀⠀⠀⠸⣿⠀⠀⠀⠀⠀⣿⠇⠀⠀⠀⣿⠇
⠀⠀⠀⠀⠀⠀⠀ ⢸⣿⠀⠀⠀⠀⣾⡟⣷⡀⠀⠀⠘⣿⣆⠀⠀⢸⣿⠀⠀⠀⠀⣿⡇⢸⣿⠀⠀⠀⠀⣿⡟⣷⡀⠀⠀⠀⠘⣿⣆⠀⠀⢻⣧⠀⠀⠀⠹⣷⣦⣤⣤⣾⠏⠀⠀⠀⣼⡟
⠀⠀⠀⠀⠀⠀⠀ ⢸⣿⠀⠀⠀⠀⣿⡇⠹⣷⡀⠀⠀⠈⢻⡇⠀⢸⣿⠀⠀⠀⠀⣿⡇⢸⣿⠀⠀⠀⠀⣿⡇⠹⣷⡀⠀⠀⠀⠈⢻⡇⠀⠀⢻⣧⠀⠀⠀⠀⠉⠉⠉⠀⠀⠀⠀⣼⡟
⠀⠀⠀⠀⠀⠀⠀ ⠸⣿⣄⡀⢀⣠⣿⠇⠀⠙⣷⡀⠀⢀⣼⠇⠀⠸⣿⣄⡀⢀⣠⣿⠇⠸⣿⣄⡀⢀⣠⣿⠇⠀⠙⣷⡀⠀⠀⢀⣼⠇⠀⠀⠀⠻⣷⣦⣄⡀⠀⠀⠀⢀⣠⣴⣾⠟
⠀⠀⠀⠀⠀⠀⠀ ⠀⠈⠻⠿⠿⠟⠁⠀⠀⠀⠈⠻⠿⠿⠟⠁⠀⠀⠈⠻⠿⠿⠟⠁⠀⠀⠈⠻⠿⠿⠟⠁⠀⠀⠀⠈⠻⠿⠿⠟⠁⠀⠀⠀⠀⠀⠈⠙⠻⠿⠿⠿⠿⠟⠋⠁

✨ What's New in Kiro CLI

2.0.1 (2026-04-16)
✔ Fixed: Fix --trust-all-tools being ignored in non-interactive mode

2.0.0 (2026-04-13)
✔ Added: Windows support. Native install with full access to Kiro agents directly in your terminal.
✔ Added: Headless mode. Run Kiro CLI programmatically with an API key — full access to all tools and agents, now scriptable. Get your access key from https://kiro.dev/
✔ Changed: UX refresh (GA). New UX is now the default with subagent monitoring (ctrl+g), real-time task lists, and stability fixes. Switch back anytime with kiro-cli --classic, or let us know /feedback.

💡 Run /changelog anytime to see the latest updates and features!

Model: auto (/model to change)

1% > hi

⠋ Thinking...
WARNING: Retry #3, retrying within 5s..
Kiro is having trouble responding right now:
0: Failed to send the request: An unknown error occurred: service error
1: An unknown error occurred: service error
2: unhandled error
3: service error
4: unhandled error
5: Error at offset 0: unexpected token '<'. Expected one of '{', '[', '"', 'null', 'true', 'false',

Location:
crates/chat-cli/src/cli/chat/mod.rs:1717

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.

### Environment

```yaml

[q-details]
version = "2.0.1"
hash = "4a41569da83e25b6ab94898d7c4c83fa18cb5216"
date = "2026-04-17T14:49:43.303879Z (5d ago)"
variant = "minimal"

[system-info]
chip = "11th Gen Intel(R) Core(TM) i5-1145G7 @ 2.60GHz"
total-cores = 4
memory = "15.47 GB"

[system-info.os.linux]
kernel_version = "6.6.87.2-microsoft-standard-WSL2"
id = "ubuntu"
name = "Ubuntu"
pretty_name = "Ubuntu 24.04.4 LTS"
version_id = "24.04"
version = "24.04.4 LTS (Noble Numbat)"

[environment]
cwd = "/home/USER"
cli-path = "/home/USER"
os = "Linux"
shell-path = "/usr/bin/bash"
shell-version = "5.2.21"
install-method = "unknown"
in-wsl = true

[env-vars]
DISPLAY = ":0"
PATH = "xxxxxxxxxxxxxxxx"
QTERM_SESSION_ID = "d10f4e6a940443b985ac3191e55511c2"
Q_SET_PARENT_CHECK = "1"
Q_TERM = "2.0.1"
SHELL = "/bin/bash"
TERM = "xterm-256color"
```

Reproduziere dies mit `kiro-cli chat --classic` in der gemeldeten WSL2-Ubuntu-Umgebung, nachdem du `q doctor` und `q restart` ausgeführt hast. Beginne bei `crates/chat-cli/src/cli/chat/mod.rs:1717` und verfolge den gemeldeten Fehler bei der Antwortverarbeitung. Erledigt ist die Aufgabe, wenn der Befehl eine korrekte Antwort statt des Parsing-Fehlers bei Offset 0 und der Wiederholungsschleife zurückgibt.

Vom Indexierungsmodell aus dem Issue-Text verfasst.