✘ Kiro CLI terminal integrations: kiro-cli-term is not running in this terminal, please try restarting your terminal

### 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

macOS 26.6.0 (25G5043d)

### Expected behaviour

fix this

### Actual behaviour

help

### Steps to reproduce

_No response_

### Environment

```yaml

[q-details]
version = "2.10.0"
hash = "a5da029503141c8033a11d7ee6569583d915cd90"
date = "2026-06-25T20:10:07.272812Z (4d ago)"
variant = "full"

[system-info]
os = "macOS 26.6.0 (25G5043d)"
chip = "Apple M1"
total-cores = 8
memory = "8.00 GB"

[environment]
cwd = "/Users/USER"
cli-path = "/Users/USER"
os = "Mac"
shell-path = "/bin/zsh"
shell-version = "5.9"
terminal = "macOS"
install-method = "unknown"

[env-vars]
PATH = "/Users/USER/.antigravity-ide/antigravity-ide/bin:/Users/USER/.antigravity-ide/antigravity-ide/bin:/Users/USER/.kilo/bin:/Users/USER/google-cloud-sdk/bin:/Users/USER/.cargo/bin:/Users/USER/Library/pnpm/bin:/Users/USER/.antigravity-ide/antigravity-ide/bin:/Users/USER/.local/bin:/Users/USER/.local/bin:/Users/USER/.bun/bin:/Users/USER/.local/state/fnm_multishells/81162_1782778109865/bin:/Users/USER/.local/bin:/Users/USER/.npm-global/bin:/Users/USER/.opencode/bin:/opt/homebrew/bin:/opt/homebrew/sbin:/Users/USER/.local/bin:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin:/pkg/env/global/bin:~/.dotnet/tools"
SHELL = "/bin/zsh"
TERM = "xterm-256color"
__CFBundleIdentifier = "com.apple.Terminal"
```

Start by reproducing the failure in the affected macOS Terminal session, then run `q doctor` and `q restart` as reported. Trace the `kiro-cli-term` terminal integration from the CLI entry point; done means the integration starts normally and the error no longer appears.

Written by the indexing model from the issue text.