{"schema_version":1,"generated_at":"2026-10-26T10:18:14Z","issues_generated_at":"2026-10-26T10:12:02Z","lookback_days":45,"license_note":"Issue metadata from public GitHub repos.","harness":"amazon-q-cli","issues":[{"id":"aws/amazon-q-developer-cli#3695","harness":"amazon-q-cli","harness_name":"Amazon Q Developer CLI","repo":"aws/amazon-q-developer-cli","number":3695,"title":"Social login (Google) has no profileArn; chat fails with \"profileArn is required but no profiles are available","url":"https://github.com/aws/amazon-q-developer-cli/issues/3695","state":"open","state_reason":null,"labels":[],"created":"2026-03-27T23:24:33Z","updated":"2026-10-22T21:34:00Z","closed":null,"reactions":1,"thumbs_up":1,"comments":7,"severity":"medium","severity_reasons":["class:auth/session"],"topic":"auth/session","classes":["auth/session","install/update"],"cosmetic_ui":false,"summary":"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 include a resolved Profile section…","versions":["1.28.2","48.00","5.9","3.5"],"error_snippets":["[environment]","Chat should work for social login users without requiring an enterprise profile configuration.","Email address","→ Shows SocialGoogle and email, but no profile","Observe error:"],"workaround":null,"fixed_in":null,"score":61.3,"first_seen":"2026-10-23T09:23:24Z"},{"id":"aws/amazon-q-developer-cli#3684","harness":"amazon-q-cli","harness_name":"Amazon Q Developer CLI","repo":"aws/amazon-q-developer-cli","number":3684,"title":"bug: acp integration with intellij no longer works since update to kiro-cli 1.28.1","url":"https://github.com/aws/amazon-q-developer-cli/issues/3684","state":"closed","state_reason":"completed","labels":[],"created":"2026-03-25T10:15:56Z","updated":"2026-10-05T19:22:10Z","closed":"2026-10-05T19:22:10Z","reactions":11,"thumbs_up":11,"comments":3,"severity":"medium","severity_reasons":["class:install/update"],"topic":"install/update","classes":["install/update","always-on/daemon","self-host/headless","auth/session","mcp/tools"],"cosmetic_ui":false,"summary":"I have run q doctor in the affected terminal session I have run q restart and replicated the issue again https://kiro.dev/docs/cli/acp/ acp integration used to work as per above instructions until update this week get an error in intellij…","versions":["1.28.1"],"error_snippets":["2026-03-25 09:55:29,182 [5034641] INFO - #c.i.m.l.a.a.p.AcpProcessHandlerService - Reusing existing process handler for agent 'Kiro' in chat 8de94113-1d33-43ac-8d91-e5641e0b1e5e","2026-03-25 09:55:31,869 [5037328] WARN - #c.i.m.l.a.a.c.a.StandardAuthHandler - Standard authentication failed for method kiro-login","com.agentclientprotocol.protocol.JsonRpcException: Method not found","at com.agentclientprotocol.protocol.Protocol.handleResponse(Protocol.kt:465)","at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:906)"],"workaround":null,"fixed_in":null,"score":57.0,"first_seen":"2026-10-19T18:38:33Z"},{"id":"aws/amazon-q-developer-cli#2768","harness":"amazon-q-cli","harness_name":"Amazon Q Developer CLI","repo":"aws/amazon-q-developer-cli","number":2768,"title":"Amazon Q CLI not loading MCP servers despite correct configuration","url":"https://github.com/aws/amazon-q-developer-cli/issues/2768","state":"closed","state_reason":"not_planned","labels":[],"created":"2025-09-03T18:10:19Z","updated":"2026-09-29T16:46:46Z","closed":"2026-09-29T16:46:45Z","reactions":4,"thumbs_up":4,"comments":0,"severity":"medium","severity_reasons":["class:self-host/headless","class:mcp/tools"],"topic":"self-host/headless","classes":["self-host/headless","mcp/tools","install/update","auth/session","network"],"cosmetic_ui":false,"summary":"Can't use MCP anymore. Tool Permission executebash trust read-only commands fsread trusted fswrite not trusted introspect trusted reportissue trusted useaws trust read-only commands Servers still loading version = \"1.15.0\" hash =…","versions":["1.15.0","16.00","5.9","24.7.0"],"error_snippets":["Can't use MCP anymore.","[environment]","✔ Everything looks good!","• ~/.aws/amazonq/mcp-servers.json (563 bytes)","• ~/.aws/amazonq/mcpAdmin/mcp-state.json → {\"enabled\":true}"],"workaround":null,"fixed_in":null,"score":39.5,"first_seen":"2026-10-19T18:38:33Z"},{"id":"aws/amazon-q-developer-cli#3932","harness":"amazon-q-cli","harness_name":"Amazon Q Developer CLI","repo":"aws/amazon-q-developer-cli","number":3932,"title":"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. Please update the bundled runtime.","url":"https://github.com/aws/amazon-q-developer-cli/issues/3932","state":"open","state_reason":null,"labels":[],"created":"2026-10-23T11:43:46Z","updated":"2026-10-23T11:43:46Z","closed":null,"reactions":0,"thumbs_up":0,"comments":0,"severity":"medium","severity_reasons":["class:install/update"],"topic":"install/update","classes":["install/update"],"cosmetic_ui":false,"summary":"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 Version of note","versions":["2.33.1","36.00","5.9","3.13"],"error_snippets":["[environment]"],"workaround":null,"fixed_in":null,"score":38.0,"first_seen":"2026-10-24T08:54:58Z"},{"id":"aws/amazon-q-developer-cli#3923","harness":"amazon-q-cli","harness_name":"Amazon Q Developer CLI","repo":"aws/amazon-q-developer-cli","number":3923,"title":"macOS leaves Kiro CLI HFS+ installer volumes mounted after updates","url":"https://github.com/aws/amazon-q-developer-cli/issues/3923","state":"open","state_reason":null,"labels":[],"created":"2026-10-04T18:28:24Z","updated":"2026-10-04T18:29:02Z","closed":null,"reactions":0,"thumbs_up":0,"comments":1,"severity":"medium","severity_reasons":["class:install/update"],"topic":"install/update","classes":["install/update"],"cosmetic_ui":false,"summary":"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. I get a growing list of mounted disk images over…","versions":["2.0","1.9","1.4","1.3"],"error_snippets":["blocksize : 512","image-encrypted : false","2026-08-29T21:12:05.538120Z ERROR fig_desktop::install: 102: No update found","2026-09-01T03:21:55.018227Z ERROR fig_install::macos: 252: the update succeeded, but unmounting the dmg failed command=hdiutil: couldn't unmount \"disk4\" - Resource busy","2026-09-02T06:30:41.992268Z ERROR fig_install::macos: 252: the update succeeded, but unmounting the dmg failed command=hdiutil: couldn't unmount \"disk6\" - Resource busy"],"workaround":null,"fixed_in":null,"score":25.5,"first_seen":"2026-10-19T18:38:33Z"},{"id":"aws/amazon-q-developer-cli#829","harness":"amazon-q-cli","harness_name":"Amazon Q Developer CLI","repo":"aws/amazon-q-developer-cli","number":829,"title":"Login is not persistant","url":"https://github.com/aws/amazon-q-developer-cli/issues/829","state":"closed","state_reason":"completed","labels":["bug"],"created":"2025-03-14T16:44:32Z","updated":"2026-10-22T06:46:34Z","closed":"2026-10-22T06:46:34Z","reactions":2,"thumbs_up":2,"comments":0,"severity":"medium","severity_reasons":["class:auth/session"],"topic":"auth/session","classes":["auth/session","install/update"],"cosmetic_ui":false,"summary":"I have run q doctor in the affected terminal session I have run q restart and replicated the issue again macOS 15.3.2 (24D81) look like the last release introduced a bug in login session not being persisted. i keep getting asked about to…","versions":["1.7.0","64.00","5.9"],"error_snippets":["[environment]","i keep getting asked about to authenticate again every day, it is annoying, i noticed this because everyday the first thing i do is to open the terminal and expect to get autocomplete when typing commands. what i need to"],"workaround":null,"fixed_in":null,"score":24.9,"first_seen":"2026-10-22T09:27:06Z"},{"id":"aws/amazon-q-developer-cli#3915","harness":"amazon-q-cli","harness_name":"Amazon Q Developer CLI","repo":"aws/amazon-q-developer-cli","number":3915,"title":"● failed to retrieve governance settings — MCP and web tools disabled","url":"https://github.com/aws/amazon-q-developer-cli/issues/3915","state":"open","state_reason":null,"labels":[],"created":"2026-09-23T10:49:25Z","updated":"2026-10-09T06:25:18Z","closed":null,"reactions":0,"thumbs_up":0,"comments":1,"severity":"medium","severity_reasons":["class:mcp/tools"],"topic":"mcp/tools","classes":["mcp/tools","self-host/headless"],"cosmetic_ui":false,"summary":"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 retrieve governance settings — MCP and…","versions":["2.23.1","31.15","20.04","20.04.6"],"error_snippets":["[environment]","● failed to retrieve governance settings — MCP and web tools disabled"],"workaround":null,"fixed_in":null,"score":17.8,"first_seen":"2026-10-19T18:38:33Z"},{"id":"aws/amazon-q-developer-cli#3929","harness":"amazon-q-cli","harness_name":"Amazon Q Developer CLI","repo":"aws/amazon-q-developer-cli","number":3929,"title":"远程 SSH 连接 macOS (darwin-arm64)失败","url":"https://github.com/aws/amazon-q-developer-cli/issues/3929","state":"open","state_reason":null,"labels":[],"created":"2026-10-13T07:39:32Z","updated":"2026-10-13T07:39:32Z","closed":null,"reactions":0,"thumbs_up":0,"comments":0,"severity":"medium","severity_reasons":["class:self-host/headless"],"topic":"self-host/headless","classes":["self-host/headless","install/update"],"cosmetic_ui":false,"summary":"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 连接 macOS (darwin-arm64) 下载缺失…","versions":["2.30.0","32.00","5.9"],"error_snippets":["[environment]","Windows 客户端升级至 commit a9f293869e317e8f9e195227dffceb57fe52a847 后，远程 SSH 连接 macOS (darwin-arm64) 下载缺失 kiro-reh-darwin-arm64.tar.gz（返回 403 / AccessDenied）。需官方流水线补齐发布"],"workaround":null,"fixed_in":null,"score":17.0,"first_seen":"2026-10-19T18:38:33Z"},{"id":"aws/amazon-q-developer-cli#3358","harness":"amazon-q-cli","harness_name":"Amazon Q Developer CLI","repo":"aws/amazon-q-developer-cli","number":3358,"title":"bug: q login ignoring identity-provider/region flags","url":"https://github.com/aws/amazon-q-developer-cli/issues/3358","state":"closed","state_reason":"completed","labels":[],"created":"2025-11-04T16:06:28Z","updated":"2026-10-22T02:01:27Z","closed":"2026-10-22T02:01:27Z","reactions":1,"thumbs_up":0,"comments":0,"severity":"medium","severity_reasons":["class:auth/session"],"topic":"auth/session","classes":["auth/session","install/update"],"cosmetic_ui":false,"summary":"I have run q doctor in the affected terminal session I have run q restart and replicated the issue again macOS 15.6.1 If I pass in the --identity-provider or --region flag, I'd expect a browser window or automatic login. If I pass in the…","versions":["1.19.3","36.00","4.1.2"],"error_snippets":["$ q login --license pro --identity-provider https://x-1234567890.awsapps.com/start --region us-east-1","✔ Enter Start URL · https://x-1234567890.awsapps.com/start","✔ Enter Region · us-east-1","[environment]","If I pass in the `--identity-provider` or `--region` flag, I'd expect a browser window or automatic login."],"workaround":null,"fixed_in":null,"score":15.9,"first_seen":"2026-10-22T09:27:06Z"},{"id":"aws/amazon-q-developer-cli#3926","harness":"amazon-q-cli","harness_name":"Amazon Q Developer CLI","repo":"aws/amazon-q-developer-cli","number":3926,"title":"failed to retrieve governance settings — MCP and web tools disabled","url":"https://github.com/aws/amazon-q-developer-cli/issues/3926","state":"open","state_reason":null,"labels":[],"created":"2026-10-10T11:23:45Z","updated":"2026-10-10T11:23:45Z","closed":null,"reactions":0,"thumbs_up":0,"comments":0,"severity":"medium","severity_reasons":["class:mcp/tools"],"topic":"mcp/tools","classes":["mcp/tools","self-host/headless","install/update"],"cosmetic_ui":false,"summary":"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 should properly start with connecting mcp…","versions":["2.29.0","24.00","5.9","17.0.18"],"error_snippets":["[environment]","While the Kiro itself working on Kiro IDE tool but Cli throwing the error.","I open the terminal , type Kiro-cli command and it throws the error .I'm getting the following error:","failed to retrieve governance settings - MCP and web tools disabled","After that, any command I try fails with a \"failure dispatch\" error."],"workaround":null,"fixed_in":null,"score":15.0,"first_seen":"2026-10-19T18:38:33Z"},{"id":"aws/amazon-q-developer-cli#3914","harness":"amazon-q-cli","harness_name":"Amazon Q Developer CLI","repo":"aws/amazon-q-developer-cli","number":3914,"title":"Auth refresh fails with \"ACP connection closed\" — dispatch failure on every request (CLI 2.23.0, WSL)","url":"https://github.com/aws/amazon-q-developer-cli/issues/3914","state":"closed","state_reason":"completed","labels":[],"created":"2026-09-22T19:30:00Z","updated":"2026-09-23T04:16:52Z","closed":"2026-09-23T04:16:52Z","reactions":0,"thumbs_up":0,"comments":1,"severity":"medium","severity_reasons":["class:self-host/headless","class:auth/session"],"topic":"self-host/headless","classes":["self-host/headless","auth/session","install/update"],"cosmetic_ui":false,"summary":"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 24.04.4 LTS kiro-cli 2.23.0 WSL2 (Ubuntu) on a corporate/enterprise network (MDLZ)…","versions":["2.23.0","1.28.1","7.47","24.04"],"error_snippets":["[environment]","auth.refresh.host_callback_failed: \"Internal error: Failed to verify authentication. Please log in again to continue.\"","acp-peer.refreshToken.error { system: \"acp-peer\", durationMs: ~7000, errorType: \"RequestError\" }","[ActivityLogPublisher] flush failed { error: \"Auth refresh callback failed: Internal error...\" }","Auth refresh callback failed: ACP connection closed"],"workaround":null,"fixed_in":null,"score":13.2,"first_seen":"2026-10-19T18:38:33Z"},{"id":"aws/amazon-q-developer-cli#3921","harness":"amazon-q-cli","harness_name":"Amazon Q Developer CLI","repo":"aws/amazon-q-developer-cli","number":3921,"title":"Startup stalls ~2s before first frame: shim walks all of /proc, cost scales with machine thread count","url":"https://github.com/aws/amazon-q-developer-cli/issues/3921","state":"open","state_reason":null,"labels":[],"created":"2026-10-02T11:05:04Z","updated":"2026-10-02T11:11:11Z","closed":null,"reactions":0,"thumbs_up":0,"comments":0,"severity":"low","severity_reasons":["low engagement"],"topic":"install/update","classes":["install/update","network"],"cosmetic_ui":false,"summary":"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-cli chat launch takes super long and is…","versions":["2.21.0","2.21.4","2.23.0","2.25.0"],"error_snippets":["Linux Red Hat Enterprise Linux 8.10 (Ootpa)","During that stall the shim walks the entire `/proc` tree. The cost is","43913 open (38902 fail ENOENT)","open(\"/proc/ /task/ /task\", O_RDONLY) = -1 ENOENT","That path is one level deeper than exists; `task` is not nested under a thread."],"workaround":null,"fixed_in":null,"score":7.0,"first_seen":"2026-10-19T18:38:33Z"},{"id":"aws/amazon-q-developer-cli#3911","harness":"amazon-q-cli","harness_name":"Amazon Q Developer CLI","repo":"aws/amazon-q-developer-cli","number":3911,"title":"cloudConfig.getManifest and ActivityLogPublisher return 401 Unable to resolve user ID after upgrade to 2.21.4","url":"https://github.com/aws/amazon-q-developer-cli/issues/3911","state":"open","state_reason":null,"labels":[],"created":"2026-09-16T08:28:11Z","updated":"2026-09-16T08:28:11Z","closed":null,"reactions":0,"thumbs_up":0,"comments":0,"severity":"medium","severity_reasons":["class:install/update","class:auth/session"],"topic":"install/update","classes":["install/update","auth/session","self-host/headless"],"cosmetic_ui":false,"summary":"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 upgrading kiro-cli to 2.21.4, every session…","versions":["2.21.4"],"error_snippets":["[environment]","After upgrading kiro-cli to 2.21.4, every session logs a 401 Unauthorized from two backend calls, even when the session is otherwise authenticated","errorType: UnauthorizedException, statusCode: 401, message: \"Unable to resolve user ID\"","2. ActivityLogPublisher -> https://runtime.us-east-1.kiro.dev/agents/activity","Failed to publish to https://runtime.us-east-1.kiro.dev/agents/activity: 401 — {\"message\":\"Unauthorized\"}"],"workaround":null,"fixed_in":null,"score":0.0,"first_seen":"2026-10-19T18:38:33Z"}]}