# Amazon Q Developer CLI: known issues context pack (KnownFix)
Generated 2026-10-26T10:18:14Z from github.com/aws/amazon-q-developer-cli. Auto-extracted; verify via links. Source: https://knownfix.ai/issues/amazon-q-cli/
Fields: severity (auto-estimate) | symptom | versions mentioned | workaround (quoted from issue/comments, if any) | fixed-in (if referenced).

## Active
- [MEDIUM] Social login (Google) has no profileArn; chat fails with "profileArn is required but no profiles are available (https://github.com/aws/amazon-q-developer-cli/issues/3695)
  - symptom: I have run q doctor in the affected terminal session I have run q restart and replicated the issue again macOS 26.3.1 (25D771280a) After logging in with Google (SocialGoogle), kiro-cli whoami should i
  - versions: 1.28.2, 48.00, 5.9
  - error: `[environment]`
  - workaround: none stated
- [MEDIUM] Kiro CLI 2.33.1 on macOS bundles Node.js 22.22.2. Node.js 22.23.4 includes security fixes released October 21, 2026. Ple (https://github.com/aws/amazon-q-developer-cli/issues/3932)
  - symptom: I have run q doctor in the affected terminal session I have run q restart and replicated the issue again macOS 26.7.1 (25G313) Kiro points to the updated Version of note Kiro points to the unsafe Vers
  - versions: 2.33.1, 36.00, 5.9
  - error: `[environment]`
  - workaround: none stated
- [MEDIUM] macOS leaves Kiro CLI HFS+ installer volumes mounted after updates (https://github.com/aws/amazon-q-developer-cli/issues/3923)
  - symptom: I have run q doctor in the affected terminal session I have run q restart and replicated the issue again macOS 26.5.2 (25F84) Installer / updater image disks are unmounted after an update
  - versions: 2.0, 1.9, 1.4
  - error: `blocksize : 512`
  - workaround: none stated
- [MEDIUM] ● failed to retrieve governance settings — MCP and web tools disabled (https://github.com/aws/amazon-q-developer-cli/issues/3915)
  - symptom: I have run q doctor in the affected terminal session I have run q restart and replicated the issue again Linux 6.6.87.2-microsoft-standard-WSL2 - Ubuntu 20.04.6 LTS kiro cli should start ● failed to r
  - versions: 2.23.1, 31.15, 20.04
  - error: `[environment]`
  - workaround: none stated
- [MEDIUM] 远程 SSH 连接 macOS (darwin-arm64)失败 (https://github.com/aws/amazon-q-developer-cli/issues/3929)
  - symptom: I have run q doctor in the affected terminal session I have run q restart and replicated the issue again macOS 26.4.0 (25E246) Windows 客户端升级至 commit a9f293869e317e8f9e195227dffceb57fe52a847 后，远程 SSH 连
  - versions: 2.30.0, 32.00, 5.9
  - error: `[environment]`
  - workaround: none stated
- [MEDIUM] failed to retrieve governance settings — MCP and web tools disabled (https://github.com/aws/amazon-q-developer-cli/issues/3926)
  - symptom: I have run q doctor in the affected terminal session I have run q restart and replicated the issue again macOS 15.7.9 (24G830) which kiro-cli kiro-cli 2.29.0 /Users/username/.local/bin/kiro-cli it sho
  - versions: 2.29.0, 24.00, 5.9
  - error: `[environment]`
  - workaround: none stated
- [LOW] Startup stalls ~2s before first frame: shim walks all of /proc, cost scales with machine thread count (https://github.com/aws/amazon-q-developer-cli/issues/3921)
  - symptom: I have run q doctor in the affected terminal session I have run q restart and replicated the issue again Linux Red Hat Enterprise Linux 8.10 (Ootpa) kiro-cli chat launch doesn't take super long kiro-c
  - versions: 2.21.0, 2.21.4, 2.23.0
  - error: `Linux Red Hat Enterprise Linux 8.10 (Ootpa)`
  - workaround: none stated
- [MEDIUM] cloudConfig.getManifest and ActivityLogPublisher return 401 Unable to resolve user ID after upgrade to 2.21.4 (https://github.com/aws/amazon-q-developer-cli/issues/3911)
  - symptom: I have run q doctor in the affected terminal session I have run q restart and replicated the issue again Linux 6.18.33.2-microsoft-standard-WSL2 - Debian GNU/Linux 13 (trixie) Description: After upgra
  - versions: 2.21.4
  - error: `[environment]`
  - workaround: none stated