aws / aws/amazon-q-developer-cli
Unsupported terminal error in Kiro Editor (dev.kiro.desktop)
- Dominant language
- Rust
- Stars
- 2k
- Forks
- 439
- PR merge metrics
- No merged PRs in 30d
Description
### 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.5.1 (25F80)
### Expected behaviour
Kiro CLI doctor throws "Unsupported terminal" error when used inside the integrated terminal of the new Kiro Editor.
- Terminal Bundle Identifier: dev.kiro.desktop
- Expected behavior: Command completion and terminal support should work natively within Kiro's own IDE terminal.
### Actual behaviour
When running `q doctor` (or `kiro-cli doctor`) inside the Kiro Editor integrated terminal, it fails with an "Unsupported terminal" error. The auto-completion and suggestion features do not work at all.
### Steps to reproduce
1. Open Kiro Editor (IDE).
2. Open the integrated terminal inside the editor.
3. Run `kiro-cli doctor` (or `q doctor`).
4. See the unsupported terminal error for `dev.kiro.desktop`.
### Environment
```yaml
[q-details]
version = "2.10.0"
hash = "a5da029503141c8033a11d7ee6569583d915cd90"
date = "2026-06-25T20:10:07.272812Z (10d ago)"
variant = "full"
[system-info]
os = "macOS 26.5.1 (25F80)"
chip = "Apple M4 Pro"
total-cores = 12
memory = "24.00 GB"
[environment]
cwd = "/Users/USER/Documents/https/vodafone/voda-hub"
cli-path = "/Users/USER/Documents/https/vodafone/voda-hub"
os = "Mac"
shell-path = "/bin/zsh"
shell-version = "5.9"
install-method = "unknown"
[env-vars]
PATH = "/Users/USER/.antigravity-ide/antigravity-ide/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.local/bin:/Users/USER/.nvm/versions/node/v22.22.0/bin:/Users/USER/.antigravity-ide/antigravity-ide/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.local/bin:/Users/USER/.nvm/versions/node/v22.22.0/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:/Library/Apple/usr/bin:/opt/homebrew/bin:/Users/USER/Library/pnpm:/Users/USER/.antigravity-ide/antigravity-ide/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.local/bin:/Users/USER/.nvm/versions/node/v22.22.0/bin:/Users/USER/.cargo/bin:/Users/USER/Library/Application Support/JetBrains/Toolbox/scripts:/Users/USER/Library/Android/sdk/platform-tools:/Users/USER/.maestro/bin:/Users/USER/.dotnet:/Users/USER/Library/Application Support/JetBrains/Toolbox/scripts:/Users/USER/Library/Android/sdk/platform-tools:/Users/USER/.maestro/bin:/Users/USER/.dotnet:/Users/USER/Library/Android/sdk/platform-tools:/Users/USER/.maestro/bin:/Users/USER/.dotnet"
QTERM_SESSION_ID = "627471f066774245bd0d0aece23673c2"
Q_SET_PARENT_CHECK = "1"
Q_TERM = "2.10.0"
SHELL = "/bin/zsh"
TERM = "xterm-256color"
ZDOTDIR = "/Users/USER"
__CFBundleIdentifier = "dev.kiro.desktop"
```
Contributor guide
Research direction
Start by reproducing the failure with `q doctor` or `kiro-cli doctor` in Kiro Editor’s integrated terminal and inspect how the CLI handles the `dev.kiro.desktop` bundle identifier. Done means the terminal is recognized, doctor succeeds, and command completion and suggestions work there without the unsupported-terminal error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, rust, zsh
- Domain
- cli, developer-experience
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100