aws / aws/amazon-q-developer-cli

Amazon Q CLI doesn't work in Kiro IDE terminal despite being an Amazon IDE

Open
#2,306 3 comments 6 reactions 0 assignees View on GitHub
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.0.0 (25A5306g)

### Expected behaviour

Amazon Q for command line should work seamlessly in Kiro IDE terminal since Kiro is an Amazon-developed IDE. The `q doctor` command should pass terminal support checks and allow full functionality of the Q CLI within the Kiro terminal environment.

### Actual behaviour

When running `q doctor` in Kiro IDE terminal, it fails with "Unsupported terminal" error. The terminal is identified with `__CFBundleIdentifier: dev.kiro.desktop` but is not recognized as a supported terminal environment, preventing Amazon Q CLI from functioning properly.

```
[chat-transcript]
> the Amazon Q for command line does not work in Kiro IDE terminal. Kiro is an Amazon IDE, it should work. I'd like you to help write "Expected behaviour" and "Actual behaviour" for a GH issue. >
>
 ~/.kiro/extensions/ q doctor>
>
✘ Terminal support: Unsupported terminal, if you believe this is a mistake or would like to see support for your terminal, run q issue>
>
__CFBundleIdentifier: dev.kiro.desktop>
>
>
✘ Doctor found errors. Please fix them and try again.>
>
If you are not sure how to fix it, please open an issue with q issue to let us know!>
>
 ~/.kiro/extensions/ q issue

I'll help you write the expected and actual behavior for this GitHub issue. Based on the output, it's clear that Amazon Q for command line isn't recognizing Kiro IDE's terminal as supported, even though it should be.
[Tool uses: report_issue]
```

### Steps to reproduce

1. Open Kiro IDE
2. Open the integrated terminal
3. Run `q doctor`
4. Observe the "Unsupported terminal" error with CFBundleIdentifier: dev.kiro.desktop

### Environment

```yaml

[q-details]
version = "1.12.4"
hash = "c20df6ad252618bed22508b33914316ea204af26"
date = "2025-07-09T01:17:19.187047Z (6d ago)"

[system-info]
os = "macOS 26.0.0 (25A5306g)"
chip = "Apple M3 Ultra"
total-cores = 28
memory = "96.00 GB"

[environment]
cwd = "/Users/USER/.kiro/extensions"
cli-path = "/Users/USER/.kiro/extensions"
install-method = "unknown"

[env-vars]
PATH = "~/bin:/Users/USER/.opencode/bin:/Users/USER/go/bin:/opt/homebrew/opt/postgresql@15/bin:/Users/USER/.nvm/versions/node/v24.3.0/bin:~/bin:/Users/USER/.opencode/bin:/Users/USER/go/bin:/opt/homebrew/opt/postgresql@15/bin:/Users/USER/.nvm/versions/node/v24.3.0/bin:/opt/homebrew/bin:/opt/homebrew/sbin:/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:/Library/Apple/usr/bin:/usr/local/share/dotnet:~/.dotnet/tools:~/bin:/Users/USER/.opencode/bin:/Users/USER/go/bin:/opt/homebrew/opt/postgresql@15/bin:/Users/USER/.nvm/versions/node/v24.3.0/bin:/Users/USER/Library/pnpm:/Users/USER/.local/bin:/Users/USER/.lmstudio/bin:/Users/USER/.local/bin:/Users/USER/.local/bin:/Users/USER/.lmstudio/bin:/Users/USER/.local/bin:/Users/USER/.lmstudio/bin"
QTERM_SESSION_ID = "36773eb5331e4ee4815a5340e109ce3e"
Q_SET_PARENT_CHECK = "1"
Q_TERM = "1.12.4"
SHELL = "/bin/zsh"
TERM = "xterm-256color"
ZDOTDIR = "/Users/USER"
__CFBundleIdentifier = "dev.kiro.desktop"

[chat-settings]

[chat-trusted_tools]

[chat-failed_request_ids]
none

[chat-context]
current_profile=default
profiles=
default

global_context=
.amazonq/rules/**/*.md
README.md
AmazonQ.md

profile_context=none

files=none
```

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.