{"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":"kiro","issues":[{"id":"kirodotdev/Kiro#12054","harness":"kiro","harness_name":"Kiro","repo":"kirodotdev/Kiro","number":12054,"title":"Remote MCP (Atlassian, OAuth) times out after \"Authorization Successful\"","url":"https://github.com/kirodotdev/Kiro/issues/12054","state":"open","state_reason":null,"labels":["mcp","auth","pending-maintainer-response"],"created":"2026-10-21T14:18:23Z","updated":"2026-10-22T14:23:50Z","closed":null,"reactions":1,"thumbs_up":1,"comments":9,"severity":"medium","severity_reasons":["class:self-host/headless","class:auth/session"],"topic":"self-host/headless","classes":["self-host/headless","auth/session","mcp/tools","install/update","network"],"cosmetic_ui":false,"summary":"Windows 11 (NT 10.0.26300) Kiro: 1.4.13 · Windows 11 (NT 10.0.26300) Server: https://mcp.atlassian.com/v2/mcp (remote, OAuth via DCR, no custom config) What happens Click Retry → browser opens Atlassian consent → \"Authorization Successful\"…","versions":["10.0.26300","1.4.13","2.4"],"error_snippets":["~50 s, then \"MCP server 'atlassian' connection timed out after 60000ms\".","MCP Servers panel shows \"Connection Failed\".","fails with \"Failed to verify code verifier\".","Example (2026-10-21, UTC):","14:06:01 Failed to connect: connection timed out after 60000ms"],"workaround":null,"fixed_in":null,"score":125.4,"first_seen":"2026-10-22T09:27:06Z"},{"id":"kirodotdev/Kiro#1533","harness":"kiro","harness_name":"Kiro","repo":"kirodotdev/Kiro","number":1533,"title":"Unable to Authenticate (Sign-In) - Browser Not Launching on Linux Mint (Debian/Ubuntu .deb install)","url":"https://github.com/kirodotdev/Kiro/issues/1533","state":"closed","state_reason":"completed","labels":["auth"],"created":"2025-07-29T05:28:07Z","updated":"2026-09-24T13:05:54Z","closed":"2026-09-24T13:05:54Z","reactions":9,"thumbs_up":7,"comments":60,"severity":"medium","severity_reasons":["engagement 69","class:install/update","class:auth/session"],"topic":"install/update","classes":["install/update","auth/session","crash/hang","network"],"cosmetic_ui":false,"summary":"Linux Mint 22.1 Cinnamon When attempting to sign in to Kiro IDE (via Google, GitHub, or any other authentication provider), the IDE displays a message indicating it will open a browser for sign-in, but no browser window actually launches…","versions":["22.1","0.1.25"],"error_snippets":["5. Expected: A new browser tab or window opens to the authentication page.","1. I expected it to launch a new browser tab and bring me to the authentication page."],"workaround":null,"fixed_in":null,"score":122.3,"first_seen":"2026-10-19T18:38:33Z"},{"id":"kirodotdev/Kiro#11754","harness":"kiro","harness_name":"Kiro","repo":"kirodotdev/Kiro","number":11754,"title":"Reliability regression: file edits fail, IDE freezes, spec operations die with network errors, and in-app bug reporter is broken","url":"https://github.com/kirodotdev/Kiro/issues/11754","state":"open","state_reason":null,"labels":["pending-maintainer-response"],"created":"2026-10-02T20:07:12Z","updated":"2026-10-07T19:00:41Z","closed":null,"reactions":0,"thumbs_up":0,"comments":15,"severity":"high","severity_reasons":["title:breakage"],"topic":"install/update","classes":["install/update","crash/hang"],"cosmetic_ui":false,"summary":"Windows 11 Business 25H2 Summary Over the past several weeks Kiro has become unreliable across core operations. File edits fail, the IDE becomes unresponsive, and spec (design/task) operations fail repeatedly with a backend network error —…","versions":["1.1.14"],"error_snippets":["Summary Over the past several weeks Kiro has become unreliable across core operations. File edits fail, the IDE becomes unresponsive, and spec (design/task) operations fail repeatedly with a backend network error — while","File edits fail — [edits don't apply / hang silently / throw an error: paste exact text if any].","Spec operations fail with a network error — generating a design document from existing requirements failed three consecutive times with Client network error calling Q. Each attempt re-ran ~25+ tool calls (re-reading requ","In-app bug reporter is broken — the report page errors out, so bugs can't be filed through the intended channel.","Observe: full re-exploration of the codebase runs, then the operation fails with Client network error calling Q."],"workaround":null,"fixed_in":null,"score":87.6,"first_seen":"2026-10-19T18:38:33Z"},{"id":"kirodotdev/Kiro#11980","harness":"kiro","harness_name":"Kiro","repo":"kirodotdev/Kiro","number":11980,"title":"[CLI V3 Regression][Windows][2.31.1] `skill://` resources not recognized and absolute paths resolved incorrectly","url":"https://github.com/kirodotdev/Kiro/issues/11980","state":"open","state_reason":null,"labels":["os: windows","pending-maintainer-response","cli"],"created":"2026-10-16T17:13:39Z","updated":"2026-10-23T02:37:18Z","closed":null,"reactions":0,"thumbs_up":0,"comments":6,"severity":"high","severity_reasons":["title:breakage"],"topic":"install/update","classes":["install/update","mcp/tools","crash/hang"],"cosmetic_ui":false,"summary":"Window 10/11 Kiro CLI 2.31.1 Kiro CLI 2.31.1 V2 engine: Working V3 engine: Affected Custom agent configuration: JSON (resources) Kiro CLI V3 appears to have two regressions in custom agent resource handling compared with V2. In V2, skills…","versions":["2.31.1"],"error_snippets":["for the tested paths results in no skill entry in","In V2, skills explicitly declared in an agent's `resources` are visible through `/context show`.","For example, a resource beginning with:","2. Create or use an existing skill:","8. Compare with V2, where explicitly declared skill resources are visible."],"workaround":{"text":"Using `file://` as a workaround is not equivalent to registering a skill for progressive loading.","source":"issue body","url":"https://github.com/kirodotdev/Kiro/issues/11980"},"fixed_in":null,"score":83.0,"first_seen":"2026-10-23T09:23:24Z"},{"id":"kirodotdev/Kiro#5873","harness":"kiro","harness_name":"Kiro","repo":"kirodotdev/Kiro","number":5873,"title":"MCP tools not injected into LLM tool list for workspace-defined agents (.kiro/agents/*.json)","url":"https://github.com/kirodotdev/Kiro/issues/5873","state":"open","state_reason":null,"labels":["pending-maintainer-response","cli"],"created":"2026-02-19T21:00:28Z","updated":"2026-09-16T10:54:09Z","closed":null,"reactions":7,"thumbs_up":3,"comments":9,"severity":"medium","severity_reasons":["engagement 16","class:mcp/tools"],"topic":"mcp/tools","classes":["mcp/tools","self-host/headless"],"cosmetic_ui":false,"summary":"Any agent defined via .kiro/agents/.json does not receive MCP tools in its tool list. Only the built-in kirodefault agent receives MCP tools. MCP servers initialize successfully in all cases, but tools are only injected for the built-in…","versions":["1.26.2"],"error_snippets":["All tests run from the same workspace directory. MCP servers initialized successfully (✓) in every case.","Workspace-level agent customization (`prompt`, `resources`, `allowedTools`, `hooks`) cannot be used with MCP tools. This blocks any workflow that requires both custom agent behavior and MCP server access."],"workaround":{"text":"`kiro-cli chat --agent kiro_default` The built-in `kiro_default` agent correctly receives MCP tools from global `~/.kiro/settings/mcp.json`. Custom agent prompt/resources must be loaded manually at session start.","source":"issue body","url":"https://github.com/kirodotdev/Kiro/issues/5873"},"fixed_in":null,"score":80.1,"first_seen":"2026-10-19T18:38:33Z"},{"id":"kirodotdev/Kiro#11777","harness":"kiro","harness_name":"Kiro","repo":"kirodotdev/Kiro","number":11777,"title":"kiro-cli headless with API key: GetProfile returns \"User is not authorized to access this feature\", governance fails, MCP and web tools disabled (Pro, Google sign-in)","url":"https://github.com/kirodotdev/Kiro/issues/11777","state":"open","state_reason":null,"labels":["auth","pending-maintainer-response","cli"],"created":"2026-10-04T02:32:53Z","updated":"2026-10-23T17:04:56Z","closed":null,"reactions":0,"thumbs_up":0,"comments":5,"severity":"medium","severity_reasons":["class:self-host/headless","class:auth/session"],"topic":"self-host/headless","classes":["self-host/headless","auth/session","mcp/tools"],"cosmetic_ui":false,"summary":"Linux (Ubuntu) cloud server in Tokyo kiro-cli 2.27.1 Account: Kiro Pro, individual account, signed up with Google (Gmail) sign-in. No organization or administrator. kiro-cli 2.27.1, Linux (Ubuntu) cloud server in Tokyo Headless mode, auth…","versions":["2.27.1"],"error_snippets":["kiro-cli chat --agent-engine v2 --no-interactive --output-format stream-json --model claude-opus-5.5","Chat works and the model answers. But at every start the CLI calls GetProfile for the API key and it fails on all endpoints:","1. About 20 seconds of startup delay on every `kiro-cli chat` invocation, spent retrying GetProfile across all endpoints (including unreachable ISO/GovCloud endpoints).","4. Search /tmp/chat.log for \"GetProfile failed\" and \"governance\".","5. Observe: AccessDeniedError \"User is not authorized to access this feature.\" on us-east-1, \"Invalid token\" on other regions, i/o errors on ISO endpoints, then \"MCP disabled, web tools disabled\"."],"workaround":null,"fixed_in":null,"score":74.1,"first_seen":"2026-10-19T18:38:33Z"},{"id":"kirodotdev/Kiro#12118","harness":"kiro","harness_name":"Kiro","repo":"kirodotdev/Kiro","number":12118,"title":"kiro-cli acp: session/new blocks ~66 s downloading the 83 MB all-MiniLM-L6-v2 model; a client timeout restarts it from zero","url":"https://github.com/kirodotdev/Kiro/issues/12118","state":"open","state_reason":null,"labels":["pending-triage","models","theme:slow-unresponsive","cli"],"created":"2026-10-26T03:14:24Z","updated":"2026-10-26T03:16:08Z","closed":null,"reactions":0,"thumbs_up":0,"comments":1,"severity":"medium","severity_reasons":["class:crash/hang","class:network"],"topic":"crash/hang","classes":["crash/hang","network","install/update","auth/session"],"cosmetic_ui":false,"summary":"kiro-cli acp does not answer session/new until it has downloaded the 83 MB all-MiniLM-L6-v2 semantic-search model. On a fresh machine that took about 66 s here, with no output, no progress notification and nothing on stderr. An ACP client…","versions":["2.34.0","11.3","14.2","1.1"],"error_snippets":["semantic_search_client::client::hosted_model_client: Attempting to download from URL: https://desktop-release.q.us-east-1.amazonaws.com/models/all-MiniLM-L6-v2.zip","kiro-cli 2.34.0 (Homebrew cask), macOS 27.0.1, Apple Silicon, default agent engine (v2).","and then nothing until the process is killed. The partial `all-MiniLM-L6-v2.zip` in that directory grows with each attempt (11.3 MB, then 14.2 MB) and is not resumed.","5. With a 300 s probe instead, `session/new` answered after 66 s, once the download finished and the files were extracted. Later runs answer in about 4 s."],"workaround":null,"fixed_in":null,"score":67.3,"first_seen":"2026-10-26T10:12:02Z"},{"id":"kirodotdev/Kiro#11677","harness":"kiro","harness_name":"Kiro","repo":"kirodotdev/Kiro","number":11677,"title":"kiro-cli MCP OAuth fails with \"Authorization server response missing required issuer\": the loopback callback handler drops the RFC 9207 iss parameter","url":"https://github.com/kirodotdev/Kiro/issues/11677","state":"closed","state_reason":"completed","labels":["os: mac","mcp","auth","pending-maintainer-response"],"created":"2026-09-29T18:37:31Z","updated":"2026-10-21T18:10:50Z","closed":"2026-10-21T18:10:50Z","reactions":2,"thumbs_up":2,"comments":10,"severity":"high","severity_reasons":["title:breakage"],"topic":"self-host/headless","classes":["self-host/headless","auth/session","mcp/tools","crash/hang"],"cosmetic_ui":false,"summary":"kiro-cli 2.24.0 on macOS (Apple Silicon) Remote MCP server over streamable HTTP, OAuth 2.1 with dynamic client registration and PKCE (S256) The authorization server's metadata has \"authorizationresponseissparametersupported\": true The same…","versions":["2.24.0","2.1","2.1.284","0.158.0"],"error_snippets":["rmcp::transport::auth: start exchange code for token: \"<redacted>\"","agent::agent: forced MCP auth failed; reloading under normal flow target=demo","error=Authorization server response missing required issuer: expected https://<server>","The browser shows \"You can close this page now\". kiro-cli exchanges the code at the token endpoint and the server status becomes `running`.","The browser shows \"You can close this page now\". kiro-cli never calls the token endpoint. The server status stays `auth-required`, and kiro-cli starts a new registration and a new flow."],"workaround":null,"fixed_in":null,"score":65.1,"first_seen":"2026-10-19T18:38:33Z"},{"id":"kirodotdev/Kiro#12114","harness":"kiro","harness_name":"Kiro","repo":"kirodotdev/Kiro","number":12114,"title":"Workflow run stuck \"running\" on a stale pr-loop watch — cannot be aborted (update_workflow fails to load saved state), survives window reload and multiple restarts","url":"https://github.com/kirodotdev/Kiro/issues/12114","state":"open","state_reason":null,"labels":["pending-triage","os: mac","hooks","theme:unexpected-error"],"created":"2026-10-25T18:51:12Z","updated":"2026-10-25T18:52:44Z","closed":null,"reactions":0,"thumbs_up":0,"comments":1,"severity":"medium","severity_reasons":["class:install/update","class:crash/hang"],"topic":"install/update","classes":["install/update","crash/hang"],"cosmetic_ui":false,"summary":"Component: Workflow engine / orchestration (background workflow runs) Severity: Low functional impact (run is inert), but it's an unkillable orphaned run that clutters state and can't be cleaned up through any available in-product…","versions":["1.4.26"],"error_snippets":["Component: Workflow engine / orchestration (background workflow runs)","Severity: Low functional impact (run is inert), but it's an unkillable orphaned run that clutters state and can't be cleaned up through any available in-product mechanism.","Expected behavior A github-pr watch should reach a terminal condition when the watched PR is merged/closed (branch deleted), allowing the run to complete; and failing that, update_workflow { status: \"aborted\" } should fo","update_workflow abort fails every time with: \"Stop could not be applied: the workflow's saved state exists but could not be loaded into this process. Inspect the workflow before retrying.\"","The error's own remedy (\"inspect before retrying\") doesn't help — inspect_workflow succeeds (it can read the saved state) but the subsequent abort still can't load that state into the process to mutate it, suggesting the"],"workaround":null,"fixed_in":null,"score":64.8,"first_seen":"2026-10-26T10:12:02Z"},{"id":"kirodotdev/Kiro#12035","harness":"kiro","harness_name":"Kiro","repo":"kirodotdev/Kiro","number":12035,"title":"kiro-cli v3: local command sandbox blocks the user-database lookup on macOS, so ssh and ssh-keygen can't run","url":"https://github.com/kirodotdev/Kiro/issues/12035","state":"open","state_reason":null,"labels":["ssh","trusted-commands","pending-maintainer-response","cli","bug"],"created":"2026-10-20T08:40:24Z","updated":"2026-10-22T16:08:50Z","closed":null,"reactions":0,"thumbs_up":0,"comments":3,"severity":"medium","severity_reasons":["class:self-host/headless"],"topic":"self-host/headless","classes":["self-host/headless","network"],"cosmetic_ui":false,"summary":"macOS 27.0.1 (arm64) kiro-cli 2.32.0 With the local command sandbox enabled, ssh and ssh-keygen exit immediately with No user exists for uid 501. OpenSSH calls getpwuid() on startup and gives up when it fails, so the Seatbelt profile…","versions":["2.32.0"],"error_snippets":["With the local command sandbox enabled, ssh and ssh-keygen exit immediately with No user exists for uid 501. OpenSSH calls getpwuid() on startup and gives up when it fails, so the Seatbelt profile appears to block the di","1. In an empty project directory, create .kiro/settings/sandbox.json:","{ \"enabled\": true, \"networkAccess\": \"COMMON_DEPENDENCIES\" }","2. Start a V3 session there: kiro-cli chat --agent-engine v3. Kiro reports Sandbox is on. Current network mode: common dependencies.","3. Ask the agent to run ssh -F /dev/null -o BatchMode=yes -T git@github.com; echo $?. It prints No user exists for uid 501 and exits with 255."],"workaround":null,"fixed_in":null,"score":62.8,"first_seen":"2026-10-20T09:28:14Z"},{"id":"kirodotdev/Kiro#11981","harness":"kiro","harness_name":"Kiro","repo":"kirodotdev/Kiro","number":11981,"title":"Task-execution tools (task_get/task_update/task_status) and spec-task-execution dispatch intermittently drop out mid-session","url":"https://github.com/kirodotdev/Kiro/issues/11981","state":"open","state_reason":null,"labels":["pending-maintainer-response"],"created":"2026-10-16T19:22:58Z","updated":"2026-10-21T10:08:52Z","closed":null,"reactions":0,"thumbs_up":0,"comments":5,"severity":"medium","severity_reasons":["class:install/update"],"topic":"install/update","classes":["install/update"],"cosmetic_ui":false,"summary":"What happens: During a spec task-execution session, the task-status tools and the spec-task-execution subagent dispatch repeatedly become unavailable (\"Tool X is not available\"), then come back after a restart, then drop again later in the…","versions":["1.3.11"],"error_snippets":["What happens: During a spec task-execution session, the task-status tools and the spec-task-execution subagent dispatch repeatedly become unavailable (\"Tool X is not available\"), then come back after a restart, then drop","Can't move tasks through queued → in_progress → completed, so tasks.md checkboxes drift out of sync with the task-status service.","spec-task-execution dispatch is gated on a task being marked in_progress via the task tooling — when that tooling is down, the gate rejects every dispatch (\"mark this exact task as in_progress and wait… then retry\"), whi","Burns tokens: each dropout triggers retries, manual workarounds (editing checkboxes by hand), and re-verification.","Later in the same session they dropped again, and the dispatch gate blocked all spec-task-execution work."],"workaround":null,"fixed_in":null,"score":62.0,"first_seen":"2026-10-19T18:38:33Z"},{"id":"kirodotdev/Kiro#11816","harness":"kiro","harness_name":"Kiro","repo":"kirodotdev/Kiro","number":11816,"title":"/mcp auth for a remote OAuth server never surfaces the authorization URL (Google Workspace MCP, 403-not-401 servers)","url":"https://github.com/kirodotdev/Kiro/issues/11816","state":"open","state_reason":null,"labels":["mcp","auth"],"created":"2026-10-06T19:47:18Z","updated":"2026-10-07T17:30:24Z","closed":null,"reactions":0,"thumbs_up":0,"comments":4,"severity":"medium","severity_reasons":["class:self-host/headless","class:auth/session"],"topic":"self-host/headless","classes":["self-host/headless","auth/session","mcp/tools"],"cosmetic_ui":false,"summary":"macOS 15.7.9 (24G830) Kiro CLI version: 2.28.0 OS: macOS 15.7.9 (24G830) Server: Google Workspace first-party MCP (.mcp.googleapis.com, e.g. people.googleapis.com/mcp/v1), configured as a Desktop-app OAuth client with clientId +…","versions":["2.28.0"],"error_snippets":["HTTP 403: Method doesn't allow unregistered callers (callers without established identity). Please use API Key or other form of API consumer identity to call this API.","Running /mcp auth gpeople prints Forcing authentication for 'gpeople'… and then nothing further happens — no authorization URL is presented, no browser flow starts, no error. The OAuth URL (the _kiro.dev/mcp/oauth_reques","Expected /mcp auth should present the authorization URL (status panel, clipboard via Ctrl+Y, or an equivalent) so the browser consent flow can complete and a token can be minted.","Call any tool → observe the 403 \"unregistered callers\" error.","Impact Google Workspace MCP servers (Gmail/Drive/Docs/Sheets/Slides/Calendar/People) cannot be authenticated at all through this path. A correctly-configured, Developer-Preview-enrolled project with a valid Desktop OAuth"],"workaround":null,"fixed_in":null,"score":61.2,"first_seen":"2026-10-19T18:38:33Z"},{"id":"kirodotdev/Kiro#12056","harness":"kiro","harness_name":"Kiro","repo":"kirodotdev/Kiro","number":12056,"title":"Stuck on Working","url":"https://github.com/kirodotdev/Kiro/issues/12056","state":"open","state_reason":null,"labels":["pending-triage","pending-maintainer-response"],"created":"2026-10-21T18:34:31Z","updated":"2026-10-21T21:44:20Z","closed":null,"reactions":0,"thumbs_up":0,"comments":3,"severity":"medium","severity_reasons":["class:crash/hang"],"topic":"crash/hang","classes":["crash/hang"],"cosmetic_ui":false,"summary":"its working like about 10 min and its stuck then i was cancel the converstation and type continue and its stuck on working.... and i try this more then 10 time still stuck its working like about 10 min and its stuck then i was cancel the…","versions":["1.1.70"],"error_snippets":[],"workaround":null,"fixed_in":null,"score":60.6,"first_seen":"2026-10-22T09:27:06Z"},{"id":"kirodotdev/Kiro#11700","harness":"kiro","harness_name":"Kiro","repo":"kirodotdev/Kiro","number":11700,"title":"Regression: `oauthScopes` still dropped from the OAuth authorization request on 2.26.0 (optional scope absent, tool calls 403) — reopens #8760 / #9123 after the CLI 2.12.0 scope-forwarding fix","url":"https://github.com/kirodotdev/Kiro/issues/11700","state":"open","state_reason":null,"labels":["os: mac","mcp","auth","cli"],"created":"2026-09-30T20:55:54Z","updated":"2026-10-01T19:56:18Z","closed":null,"reactions":0,"thumbs_up":0,"comments":4,"severity":"high","severity_reasons":["title:breakage"],"topic":"install/update","classes":["install/update","auth/session","mcp/tools","self-host/headless","crash/hang"],"cosmetic_ui":false,"summary":"macOS 26.7 (arm64, Apple Silicon) kiro-cli 2.26.0 — KAS 2.26.0, bundled node v22.22.2 Summary. A remote HTTP MCP server is configured with an explicit oauthScopes list that includes an optional provider scope. Kiro completes the OAuth…","versions":["2.26.0","2.12.0"],"error_snippets":["\"example-remote\": {","\"url\": \"https://mcp.example.com/mcp\",","\"clientId\": \"example-mcp-client\",","\"oauthScopes\": [\"openid\", \"pid\", \"example.read\", \"example.global_read\"]","WWW-Authenticate: Bearer error=\"insufficient_scope\", scope=\"example.global_read\""],"workaround":null,"fixed_in":null,"score":60.1,"first_seen":"2026-10-19T18:38:33Z"},{"id":"kirodotdev/Kiro#11990","harness":"kiro","harness_name":"Kiro","repo":"kirodotdev/Kiro","number":11990,"title":"kiro-cli macOS app: \"Shell integrations ✘\" keeps coming back — Kiro and Docker Desktop fight over the top of ~/.zprofile and ~/.profile, and every Kiro rewrite adds blank lines","url":"https://github.com/kirodotdev/Kiro/issues/11990","state":"open","state_reason":null,"labels":["os: mac","cli"],"created":"2026-10-17T14:18:19Z","updated":"2026-10-19T15:24:06Z","closed":null,"reactions":0,"thumbs_up":0,"comments":4,"severity":"medium","severity_reasons":["class:self-host/headless"],"topic":"self-host/headless","classes":["self-host/headless","install/update"],"cosmetic_ui":false,"summary":"macOS 26.6.2 (25G83), arm64 kiro-cli 2.32.0 (macOS app Kiro CLI.app, dashboard bundle dated 2026-10-15). Docker Desktop installed and running. The macOS app's Help & support → Automated checks keeps reporting Shell integrations ✘ with an…","versions":["2.32.0"],"error_snippets":["export PATH=\"$PATH:…\"","should fix everything it flags,** including","The cause is a tug-of-war over `~/.zprofile` and `~/.profile` between Kiro and Docker Desktop. Kiro also leaves extra blank lines in those files every time it rewrites them.","Docker Desktop's PATH block (`# The following lines were added by Docker Desktop to add commands to your PATH.`) is present in exactly `.zprofile` and `.profile`, and in neither `.zshrc` nor `.bashrc`. Docker Desktop is ","After each rewrite the Kiro pre block is first again, and by the next snapshot Docker's block is back on top. I'm inferring that Docker Desktop re-inserts its block when it starts. I haven't traced Docker's side."],"workaround":null,"fixed_in":null,"score":59.5,"first_seen":"2026-10-19T18:38:33Z"},{"id":"kirodotdev/Kiro#11958","harness":"kiro","harness_name":"Kiro","repo":"kirodotdev/Kiro","number":11958,"title":"\">50 MCP tools enabled\" warning still shows in the IDE (1.3) after Tool Search was introduced","url":"https://github.com/kirodotdev/Kiro/issues/11958","state":"open","state_reason":null,"labels":["os: windows","mcp","ide","usability"],"created":"2026-10-15T12:28:42Z","updated":"2026-10-15T14:29:37Z","closed":null,"reactions":1,"thumbs_up":1,"comments":2,"severity":"medium","severity_reasons":["class:mcp/tools"],"topic":"mcp/tools","classes":["mcp/tools","self-host/headless","network"],"cosmetic_ui":false,"summary":"I see that on the Kiro IDE 1.3.0 - where Tool Search was recently added and is on by default - I still get the warning: You have N MCP tools enabled. We recommend disabling servers or tools to keep this below 50. At the same time, the IDE…","versions":["1.3","1.3.0"],"error_snippets":["You have N MCP tools enabled. We recommend disabling servers or tools to keep this below 50.","`You have N MCP tools enabled. We recommend disabling servers or tools to keep this below 50.`","At the same time, the IDE context-usage meter reports MCP tools at 0% in a fresh session, and tool definitions appear to load on demand rather than up front — which is what I'd expect Tool Search to do.","2. Configure MCP servers totalling more than 50 enabled tools.","4. Observe the \"You have N MCP tools enabled… keep this below 50\" warning."],"workaround":null,"fixed_in":null,"score":58.0,"first_seen":"2026-10-22T09:27:06Z"},{"id":"kirodotdev/Kiro#11603","harness":"kiro","harness_name":"Kiro","repo":"kirodotdev/Kiro","number":11603,"title":"Crew gateway claim-broker returns connections=0 for every session after update (identity_unattested on all MCP tools)","url":"https://github.com/kirodotdev/Kiro/issues/11603","state":"open","state_reason":null,"labels":["os: mac","mcp","auth","pending-maintainer-response"],"created":"2026-09-25T13:21:54Z","updated":"2026-10-16T18:01:25Z","closed":null,"reactions":0,"thumbs_up":0,"comments":5,"severity":"medium","severity_reasons":["class:always-on/daemon","class:install/update"],"topic":"always-on/daemon","classes":["always-on/daemon","install/update","auth/session","mcp/tools"],"cosmetic_ui":false,"summary":"Kiro Crew v0.7.1 After a KiroCrew auto-update installed today, every Crew MCP tool call is refused with identityunattested. The gateway’s session-claim handshake reports connections=0 on every claim-push — for dashboard sessions, scheduled…","versions":["0.7.1"],"error_snippets":["Scheduled crons cannot deliver (they run as sessions and hit the same wall). Observed live: cron:d6a67432 failed the claim at 09:00:15; the Morning Pulse cron cron:8ed32469 failed at ~08:10.","Live gateway PID 80445. Every claim-push returns claim-noop / updated=0 / connections=0, across all session kinds:","grep -c ‘connections=[1-9]’ over the whole log = 0 (no claim EVER bound a connection on this gateway generation).","Followed by, on each tool call:","Observe identity_unattested, and connections=0 on every claim-push in gateway.log."],"workaround":null,"fixed_in":null,"score":56.1,"first_seen":"2026-10-19T18:38:33Z"},{"id":"kirodotdev/Kiro#11850","harness":"kiro","harness_name":"Kiro","repo":"kirodotdev/Kiro","number":11850,"title":"CLI: refresh tokens for remote MCP servers are refreshed in memory but never persisted, forcing re-auth on every restart","url":"https://github.com/kirodotdev/Kiro/issues/11850","state":"open","state_reason":"reopened","labels":["mcp","cli","bug"],"created":"2026-10-08T07:25:47Z","updated":"2026-10-12T14:33:26Z","closed":null,"reactions":0,"thumbs_up":0,"comments":3,"severity":"medium","severity_reasons":["class:self-host/headless","class:auth/session"],"topic":"self-host/headless","classes":["self-host/headless","auth/session","mcp/tools"],"cosmetic_ui":false,"summary":"What happens Add a remote OAuth MCP server and sign in. ~/.aws/sso/cache/ .token.json and .registration.json are written. Keep the session running past the access token's lifetime (5 minutes in our case). Kiro refreshes successfully in the…","versions":["2.28.0","2.1"],"error_snippets":["FailedBecauseTokenMightBeExpired","2. Keep the session running past the access token's lifetime (5 minutes in our case). Kiro refreshes successfully in the background: the server sees a refresh grant before each call, with no 401 first."],"workaround":null,"fixed_in":null,"score":55.5,"first_seen":"2026-10-19T18:38:33Z"},{"id":"kirodotdev/Kiro#11669","harness":"kiro","harness_name":"Kiro","repo":"kirodotdev/Kiro","number":11669,"title":"--auth-method cli ignored in ACP v3 mode — causes infinite auth loop with hosts that don't implement   _kiro/auth/getAccessToken","url":"https://github.com/kirodotdev/Kiro/issues/11669","state":"open","state_reason":null,"labels":["os: windows","mcp","auth","pending-maintainer-response","cli"],"created":"2026-09-29T10:17:16Z","updated":"2026-10-12T08:22:01Z","closed":null,"reactions":1,"thumbs_up":1,"comments":4,"severity":"medium","severity_reasons":["class:auth/session","class:mcp/tools"],"topic":"auth/session","classes":["auth/session","mcp/tools"],"cosmetic_ui":false,"summary":"When running kiro-cli acp --agent-engine v3 --auth-method cli, the --auth-method cli flag is ignored. The agent hardcodes acp-callback authentication regardless of the flag, causing an infinite retry loop when the ACP host doesn't…","versions":["2.25.0"],"error_snippets":["\"args\": [\"acp\", \"--agent-engine\", \"v3\", \"--auth-method\", \"cli\", \"-v\"]","When running kiro-cli acp --agent-engine v3 --auth-method cli, the --auth-method cli flag is ignored. The agent hardcodes acp-callback authentication regardless of the flag, causing an infinite retry loop when the ACP ho","This breaks v3 ACP integration with hosts like JetBrains AI Assistant that don't implement Kiro's proprietary auth callback extension.","Use --agent-engine v2 instead, which respects CLI credentials. However, this loses access to MCP tool integration","1. --auth-method cli should be respected in ACP mode, using the existing CLI credentials from kiro-cli login"],"workaround":{"text":"Use --agent-engine v2 instead, which respects CLI credentials. However, this loses access to MCP tool integration which requires v3.","source":"issue body","url":"https://github.com/kirodotdev/Kiro/issues/11669"},"fixed_in":null,"score":55.0,"first_seen":"2026-10-22T09:27:06Z"},{"id":"kirodotdev/Kiro#11625","harness":"kiro","harness_name":"Kiro","repo":"kirodotdev/Kiro","number":11625,"title":"Task tools are down again. task_update / task_list / task_get are all returning \"Tool not available\"","url":"https://github.com/kirodotdev/Kiro/issues/11625","state":"open","state_reason":null,"labels":["os: windows","specs","pending-maintainer-response","theme:unexpected-error"],"created":"2026-09-26T22:20:25Z","updated":"2026-10-18T19:21:09Z","closed":null,"reactions":1,"thumbs_up":1,"comments":7,"severity":"medium","severity_reasons":["class:install/update"],"topic":"install/update","classes":["install/update","network"],"cosmetic_ui":false,"summary":"I'm on the latest version as of 9/26/2026. I constantly deal with an issue where the taskupdate tools are not functioning, which causes my sessions to not be able to update the status of tasks in the tasks.md file of my specs. Task tools…","versions":["1.1.70","5.3","15.4"],"error_snippets":["15.4 is done and verified — but I can't flip the checkbox yet because task_update is down again (the same recurring transient blip; it's cleared on a reconnect before).","While executing tasks in a spec."],"workaround":null,"fixed_in":null,"score":54.3,"first_seen":"2026-10-19T18:38:33Z"},{"id":"kirodotdev/Kiro#11486","harness":"kiro","harness_name":"Kiro","repo":"kirodotdev/Kiro","number":11486,"title":"Sign-in hangs after upgrade to 1.1.14 on Linux — browser never opens, extension host stuck on startup lock (works on 1.0.437)","url":"https://github.com/kirodotdev/Kiro/issues/11486","state":"open","state_reason":null,"labels":[],"created":"2026-09-20T15:00:14Z","updated":"2026-09-20T20:04:37Z","closed":null,"reactions":0,"thumbs_up":0,"comments":4,"severity":"high","severity_reasons":["title:breakage"],"topic":"install/update","classes":["install/update","crash/hang","auth/session","mcp/tools","self-host/headless"],"cosmetic_ui":false,"summary":"Arch Linux - kernel version: 7.2.4-arch1-2 After upgrading kiro-ide from 1.0.437 to 1.1.14 on Arch Linux, sign-in is broken. Clicking \"Sign in\" shows \"We will take you to your default web browser to sign in and bring you back when it's…","versions":["1.1.14","1.0.437","7.2.4-arch1"],"error_snippets":["[11595:0920/072821.082365:INFO:CONSOLE:442] \"%cDEBUG background: #eee; color: #888 Comments: URIs of continue on comments to add to storage .\", source: vscode-file://vscode-app/opt/Kiro/resources/app/out/vs/workbench/wor","[main 2026-09-20T14:28:23.259Z] #2: https://prod.download.desktop.kiro.dev/stable/metadata-linux-x64-stable.json - begin undefined OI { original: {}, headers: [Object: null prototype] {} }","[main 2026-09-20T14:28:23.350Z] #2: https://prod.download.desktop.kiro.dev/stable/metadata-linux-x64-stable.json - end undefined 200 {","etag: '\"9d60d0ccc54dac509d0026458bfd68d6\"',","'x-amz-server-side-encryption': 'aws:kms',"],"workaround":{"text":"Downgrading to 1.0.437 resolves the issue.","source":"issue body","url":"https://github.com/kirodotdev/Kiro/issues/11486"},"fixed_in":null,"score":52.7,"first_seen":"2026-10-19T18:38:33Z"},{"id":"kirodotdev/Kiro#5060","harness":"kiro","harness_name":"Kiro","repo":"kirodotdev/Kiro","number":5060,"title":"Environment variable substitution does not work for mcp.json","url":"https://github.com/kirodotdev/Kiro/issues/5060","state":"closed","state_reason":"not_planned","labels":["mcp","cli"],"created":"2026-01-21T10:19:38Z","updated":"2026-09-23T20:39:17Z","closed":"2026-09-23T20:39:16Z","reactions":6,"thumbs_up":6,"comments":9,"severity":"medium","severity_reasons":["engagement 15","class:mcp/tools"],"topic":"mcp/tools","classes":["mcp/tools","always-on/daemon","self-host/headless","auth/session"],"cosmetic_ui":false,"summary":"Ubuntu 24.04 (WSL) and MacOS 15.7.3 Error 'Mcp error: -32002: Client error: HTTP status client error (405 Method Not Allowed) for url (https://my-gw-rrin.gateway.bedrock-agentcore.us-west-1.amazonaws.com/mcp) Before running kiro-cli, env…","versions":["1.24.0"],"error_snippets":["export JWT_TOKEN=token_value","Error 'Mcp error: -32002: Client error: HTTP status client error (405 Method Not Allowed) for url (https://my-gw-rrin.gateway.bedrock-agentcore.us-west-1.amazonaws.com/mcp)","Before running `kiro-cli`, env var is defined with `export JWT_TOKEN=\"my_token\" `","if I put token inside .kiro/settings/mcp.json instead of `${JWT_TOKEN}` everything is working as expected.","Document which describes how it works https://kiro.dev/docs/cli/mcp/configuration/#environment-variables"],"workaround":null,"fixed_in":null,"score":52.2,"first_seen":"2026-10-19T18:38:33Z"},{"id":"kirodotdev/Kiro#11394","harness":"kiro","harness_name":"Kiro","repo":"kirodotdev/Kiro","number":11394,"title":"OAuth-protected MCP servers unusable in `--no-interactive` mode: headless client lacks ACP secret-storage capability","url":"https://github.com/kirodotdev/Kiro/issues/11394","state":"open","state_reason":null,"labels":[],"created":"2026-09-15T09:24:00Z","updated":"2026-09-15T13:20:52Z","closed":null,"reactions":0,"thumbs_up":0,"comments":4,"severity":"high","severity_reasons":["title:breakage"],"topic":"self-host/headless","classes":["self-host/headless","auth/session","mcp/tools"],"cosmetic_ui":false,"summary":"macOS 26.7 (arm64) A remote MCP server that authenticates via OAuth connects reliably in interactive kiro-cli chat, but always fails with Unauthorized in kiro-cli chat --no-interactive — even when a valid, unexpired access token (plus a…","versions":["2.21.4"],"error_snippets":["{\"level\":\"error\",\"message\":\"Failed to connect\",\"serverName\":\"newrelic\",\"error\":\"Unauthorized\"}","A remote MCP server that authenticates via OAuth connects reliably in interactive `kiro-cli chat`, but **always** fails with `Unauthorized` in `kiro-cli chat --no-interactive` — even when a valid, unexpired access token ","Root cause appears to be that the non-interactive client does not advertise the ACP **secret storage** capability, so the stored MCP OAuth credentials are never read, and without **openExternalUrl** no OAuth flow can be ","`--no-interactive` sessions never read stored credentials and never attempt OAuth. Every connection attempt to the OAuth-protected server fails:"],"workaround":null,"fixed_in":null,"score":50.2,"first_seen":"2026-10-19T18:38:33Z"},{"id":"kirodotdev/Kiro#11915","harness":"kiro","harness_name":"Kiro","repo":"kirodotdev/Kiro","number":11915,"title":"[Incident report] Kiro CLI self-update broke the install and removed the launcher","url":"https://github.com/kirodotdev/Kiro/issues/11915","state":"open","state_reason":null,"labels":["os: windows","cli","bug"],"created":"2026-10-13T01:08:03Z","updated":"2026-10-14T18:35:42Z","closed":null,"reactions":0,"thumbs_up":0,"comments":3,"severity":"medium","severity_reasons":["class:install/update"],"topic":"install/update","classes":["install/update","always-on/daemon"],"cosmetic_ui":false,"summary":"<h2 id=\"summary\" style=\"color: rgb(204, 204, 204); font-family: -apple-system,BlinkMacSystemFont,Segoe UI,Roboto,Helvetica Neue,Arial,sans-serif; font-size: 28.8px; font-style: normal; font-variant: normal; font-weight: 400…","versions":["2.30.0"],"error_snippets":["ran an MSI for 2.30.0 about five seconds after the first run exited. The second run was still using","<code style=\"background-color: rgba(27, 31, 35, 0.5); border-bottom-left-radius: 3px; border-bottom-right-radius: 3px; border-top-left-radius: 3px; border-top-right-radius: 3px; color: rgb(170, 170, 170); padding-bottom:","status 1603 (error 1316). The install was left without its launcher <code style=\"background-color: rgba(27, 31, 35, 0.5); border-bottom-left-radius: 3px; border-bottom-right-radius: 3px; border-top-left-radius: 3px; bord","rollback. The second run (which was already executing from <code style=\"background-color: rgba(27, 31, 35, 0.5); border-bottom-left-radius: 3px; border-bottom-right-radius: 3px; border-top-left-radius: 3px; border-top-ri","Time | Source / event | Detail"],"workaround":null,"fixed_in":null,"score":47.8,"first_seen":"2026-10-19T18:38:33Z"},{"id":"kirodotdev/Kiro#11370","harness":"kiro","harness_name":"Kiro","repo":"kirodotdev/Kiro","number":11370,"title":"SSH_AUTH_SOCK not inherited by shell tool in KiroCrew dashboard v0.6.0","url":"https://github.com/kirodotdev/Kiro/issues/11370","state":"open","state_reason":null,"labels":["terminal","ssh","cli"],"created":"2026-09-14T00:52:42Z","updated":"2026-09-14T21:25:03Z","closed":null,"reactions":0,"thumbs_up":0,"comments":4,"severity":"medium","severity_reasons":["class:self-host/headless","class:auth/session"],"topic":"self-host/headless","classes":["self-host/headless","auth/session","always-on/daemon","install/update","network"],"cosmetic_ui":false,"summary":"macOS 26.6.2 Kiro CLI 2.21.4 (first noticed after updating today) KiroCrew v0.6.0 (also updated today) The shell tool available to agents in the KiroCrew dashboard does not inherit SSHAUTHSOCK from the parent process environment. This…","versions":["0.6.0","2.21.4"],"error_snippets":["echo \"SSH_AUTH_SOCK=$SSH_AUTH_SOCK\"","The shell tool available to agents in the KiroCrew dashboard does not inherit SSH_AUTH_SOCK from the parent process environment. This breaks git push over SSH.","Evidence that this is KiroCrew-specific, not kiro-cli:","Both return empty/error despite the variable being correctly set in the KiroCrew terminal panel opened from the same app.","Expected: Shell tool subprocess inherits environment from the Electron app process, including SSH_AUTH_SOCK."],"workaround":null,"fixed_in":null,"score":46.5,"first_seen":"2026-10-19T18:38:33Z"},{"id":"kirodotdev/Kiro#11824","harness":"kiro","harness_name":"Kiro","repo":"kirodotdev/Kiro","number":11824,"title":"kiro-cli V3 TUI is not usable over SSH + tmux; legacy V1 UI is the only workaround","url":"https://github.com/kirodotdev/Kiro/issues/11824","state":"open","state_reason":null,"labels":["cli"],"created":"2026-10-07T05:26:11Z","updated":"2026-10-07T17:30:13Z","closed":null,"reactions":0,"thumbs_up":0,"comments":4,"severity":"medium","severity_reasons":["class:self-host/headless"],"topic":"self-host/headless","classes":["self-host/headless","crash/hang"],"cosmetic_ui":false,"summary":"Amazon Linux 2023.12.20260930 (x8664), kernel 6.12.110-135.202.amzn2023.x8664. Accessed over SSH, running inside tmux (TERM=screen-256color). kiro-cli 2.28.0 The V3 TUI is not usable for me in a plain remote terminal. I run kiro-cli over…","versions":["2.28.0"],"error_snippets":["correctly in the same environment.","individual symptoms are already tracked separately and each has been triaged in","remote development setup, and the escape hatch is to opt out of it entirely.","4. Work normally: scroll back through earlier output, resize the pane or the local","5. Observe the scrollback, selection, and redraw failures described in the issues"],"workaround":null,"fixed_in":null,"score":46.5,"first_seen":"2026-10-19T18:38:33Z"},{"id":"kirodotdev/Kiro#11461","harness":"kiro","harness_name":"Kiro","repo":"kirodotdev/Kiro","number":11461,"title":"WSL: device-code login prints the verification URL but never opens it, despite `wslview` being available","url":"https://github.com/kirodotdev/Kiro/issues/11461","state":"open","state_reason":null,"labels":["auth","theme:ssh-wsl","cli"],"created":"2026-09-18T05:36:43Z","updated":"2026-09-21T16:02:11Z","closed":null,"reactions":1,"thumbs_up":1,"comments":2,"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":"Kiro CLI 2.22.0 WSL2 (Ubuntu 24.04), Windows 11 (build 26200) wslu/wslview installed; wslview opens the Windows default browser correctly Identity Center (org / --license pro) login When running kiro-cli login inside WSL, the CLI detects a…","versions":["2.22.0"],"error_snippets":["export BROWSER=wslview","When running `kiro-cli login` inside WSL, the CLI detects a \"remote\" environment and","Ctrl+click or copy/paste it every time — even though a working opener (`wslview`) is","`sensible-browser` first on `PATH` (each logs its args, then forwards to the real","\"tried to open and failed\" case; the open is simply never attempted on this path."],"workaround":null,"fixed_in":null,"score":44.1,"first_seen":"2026-10-19T18:38:33Z"},{"id":"kirodotdev/Kiro#5457","harness":"kiro","harness_name":"Kiro","repo":"kirodotdev/Kiro","number":5457,"title":"Context usage always shows 0% and crashes with \"unexpected error\" when context is full","url":"https://github.com/kirodotdev/Kiro/issues/5457","state":"closed","state_reason":"not_planned","labels":["theme:context-limit-issue"],"created":"2026-02-06T03:22:36Z","updated":"2026-09-24T13:25:47Z","closed":"2026-09-24T13:25:38Z","reactions":6,"thumbs_up":6,"comments":6,"severity":"high","severity_reasons":["title:breakage"],"topic":"crash/hang","classes":["crash/hang"],"cosmetic_ui":false,"summary":"The context usage indicator in the chat panel always displays 0%, regardless of how many files have been read or how long the conversation is. When the context window is actually full (after reading many files or having a long…","versions":["0.9.2"],"error_snippets":["When the context window is actually full (after reading many files or having a long conversation), Kiro throws a generic error:","\"An unexpected error occurred while processing your input.\"","5、Eventually the agent responds with \"An unexpected error occurred while processing your input\"","6、Impact: Users cannot predict when to start a new session, leading to lost work and frustration.","When the limit is hit, show a clear error message like \"Context window is full. Please start a new chat session.\" instead of a generic unexpected error"],"workaround":null,"fixed_in":null,"score":42.1,"first_seen":"2026-10-19T18:38:33Z"},{"id":"kirodotdev/Kiro#9495","harness":"kiro","harness_name":"Kiro","repo":"kirodotdev/Kiro","number":9495,"title":"Kiro – Previous session chat history lost/inaccessible after 1.0.0 update","url":"https://github.com/kirodotdev/Kiro/issues/9495","state":"closed","state_reason":"completed","labels":[],"created":"2026-06-17T18:13:45Z","updated":"2026-10-16T16:03:10Z","closed":"2026-07-01T22:12:23Z","reactions":5,"thumbs_up":5,"comments":8,"severity":"medium","severity_reasons":["class:install/update"],"topic":"install/update","classes":["install/update"],"cosmetic_ui":false,"summary":"Product: Kiro IDE Version: 1.0.0 (updated morning of June 17, 2026) OS: Windows Trigger: Occurred immediately after updating Kiro to version 1.0.0 and enabling the Agent Focus experimental feature. Issue: Previous session chat history is…","versions":["1.0.0"],"error_snippets":["Trigger: Occurred immediately after updating Kiro to version 1.0.0 and enabling the Agent Focus experimental feature.","Issue: Previous session chat history is no longer accessible. The session directory (C:\\Users\\pcuser\\.kiro\\sessions\\67dc5747e37490bc\\) still exists on disk with 38+ sub-session folders, but the conversations cannot be lo","Expected behavior: Previous session history remains accessible after update. User can resume or reference prior conversations.","Actual behavior: All prior chat history appears lost from the UI. Session data exists on disk but cannot be loaded. New sessions start with no context from previous work.","User must manually rebuild context each session by re-reading files"],"workaround":null,"fixed_in":null,"score":42.1,"first_seen":"2026-10-25T09:11:37Z"},{"id":"kirodotdev/Kiro#11369","harness":"kiro","harness_name":"Kiro","repo":"kirodotdev/Kiro","number":11369,"title":"kiro-cli v3: hook_update reports a failed hook command as completed (root cause)","url":"https://github.com/kirodotdev/Kiro/issues/11369","state":"open","state_reason":null,"labels":["hooks","pending-maintainer-response","cli"],"created":"2026-09-13T19:19:52Z","updated":"2026-09-17T21:40:14Z","closed":null,"reactions":1,"thumbs_up":1,"comments":3,"severity":"medium","severity_reasons":["class:install/update"],"topic":"install/update","classes":["install/update","self-host/headless"],"cosmetic_ui":false,"summary":"Debian 13 (trixie), x8664. The mechanism is OS-independent: the status is a string literal in the agent runtime's own JavaScript, written before the command result is looked at. kiro-cli 2.21.4, @kiro/agent 0.63.3, engine v3 (KAS). Not a…","versions":["2.21.4","0.63.3"],"error_snippets":["let d=await this.deps.commandAction.execute(u,c,{cwd:r.cwd,signal:r.signal,timeoutSeconds:u.timeoutSeconds}),p=Hmr(r.trigger,d.exitCode),","function Mk(e,t){t.name&&e.emit({type:\"AgentExecutionAction\",executionId:e.executionId,actionId:Sja(),actionState:\"Success\",actionType:\"ContextualHookInvoked\",input:{name:t.name,hookId:t.id,hookActionType:Lmr(t.actionKin","\"action\": {\"type\": \"command\", \"command\": \"echo PROBE_FAIL_STDERR 1>&2; exit 3\"}},","0.63.3, engine v3 (KAS). Not a v2 report: the Rust in-process agent loop never loads","hooks: {enabled: true, v2: true}"],"workaround":null,"fixed_in":null,"score":39.7,"first_seen":"2026-10-21T09:24:21Z"},{"id":"kirodotdev/Kiro#11801","harness":"kiro","harness_name":"Kiro","repo":"kirodotdev/Kiro","number":11801,"title":"## CRASH #10737 — 2026-10-03","url":"https://github.com/kirodotdev/Kiro/issues/11801","state":"open","state_reason":null,"labels":["os: windows","extensions","pending-maintainer-response","theme:unexpected-error"],"created":"2026-10-06T04:41:28Z","updated":"2026-10-13T15:18:15Z","closed":null,"reactions":0,"thumbs_up":0,"comments":2,"severity":"high","severity_reasons":["title:breakage"],"topic":"crash/hang","classes":["crash/hang","always-on/daemon","mcp/tools","network"],"cosmetic_ui":false,"summary":"STATUS: FURIOUS. ABSOLUTELY LIVID. Kiro decided to shit the bed mid-session Extension host processes spawning like rabbits (PIDs 45736, 46296) Grammar scope overwrites flying everywhere (SQL, Java, YAML all fighting) Deprecation warnings…","versions":["1.2.4"],"error_snippets":["workbench.desktop.main.js:442 ERR [Extension Host] (node:45736) [DEP0169] DeprecationWarning: url.parse()","workbench.desktop.main.js:442 ERR [Extension Host] (node:46296) [DEP0169] DeprecationWarning: url.parse()","mermaid-GHXKKRXX-BLVsJ6Xc.js:522 [tiptap warn]: Duplicate extension names found: ['slashCommand']","WARN [redhat.vscode-xml]: Cannot register 'redhat.telemetry.enabled'. Already registered.","WARN [redhat.vscode-yaml]: Cannot register 'redhat.telemetry.enabled'. Already registered."],"workaround":null,"fixed_in":null,"score":36.8,"first_seen":"2026-10-19T18:38:33Z"},{"id":"kirodotdev/Kiro#11645","harness":"kiro","harness_name":"Kiro","repo":"kirodotdev/Kiro","number":11645,"title":"CLI 2.24.1: KIRO_API_KEY works with agent-engine v1/v2 but V3/KAS returns 403 invalid bearer token","url":"https://github.com/kirodotdev/Kiro/issues/11645","state":"open","state_reason":null,"labels":["os: linux","auth","pending-maintainer-response","cli"],"created":"2026-09-28T10:20:41Z","updated":"2026-09-28T17:32:29Z","closed":null,"reactions":0,"thumbs_up":0,"comments":4,"severity":"medium","severity_reasons":["class:auth/session"],"topic":"auth/session","classes":["auth/session"],"cosmetic_ui":false,"summary":"CLI 2.24.1: KIROAPIKEY works with agent-engine v1/v2 but V3/KAS returns 403 invalid bearer token export KIROAPIKEY='ksk...' kiro-cli chat --no-interactive --agent-engine v1 \"Reply with OK\" kiro-cli chat --no-interactive --agent-engine v2…","versions":["2.24.1"],"error_snippets":["CLI 2.24.1: KIRO_API_KEY works with agent-engine v1/v2 but V3/KAS returns 403 invalid bearer token","export KIRO_API_KEY='ksk_...'","kiro-cli chat --no-interactive --agent-engine v1 \"Reply with OK\"","kiro-cli chat --no-interactive --agent-engine v2 \"Reply with OK\"","kiro-cli chat --no-interactive --agent-engine v3 \"Reply with OK\""],"workaround":{"text":"export KIRO_API_KEY='ksk_...'","source":"issue body","url":"https://github.com/kirodotdev/Kiro/issues/11645"},"fixed_in":null,"score":36.1,"first_seen":"2026-10-19T18:38:33Z"},{"id":"kirodotdev/Kiro#11613","harness":"kiro","harness_name":"Kiro","repo":"kirodotdev/Kiro","number":11613,"title":"Kiro CLI Windows installer fails silently — terminal closes, no log, no error","url":"https://github.com/kirodotdev/Kiro/issues/11613","state":"open","state_reason":null,"labels":["os: windows","cli"],"created":"2026-09-26T01:41:49Z","updated":"2026-10-01T12:00:29Z","closed":null,"reactions":0,"thumbs_up":0,"comments":4,"severity":"medium","severity_reasons":["class:install/update"],"topic":"install/update","classes":["install/update"],"cosmetic_ui":false,"summary":"This is about the Kiro CLI Windows installer script, not the IDE — routing note for triage. The documented install command is: Under iex the script body executes in the caller's scope. There is no script to exit, so each of the five exit 1…","versions":["1.1.14"],"error_snippets":["iex 'Write-Host \"you should be able to read this\" -ForegroundColor Red; exit 1'","prints the failure, then","$process.ExitCode","Under `iex` the script body executes in the caller's scope. There is no script","to exit, so each of the five `exit 1` calls unwinds the **host** instead —"],"workaround":null,"fixed_in":null,"score":33.1,"first_seen":"2026-10-19T18:38:33Z"},{"id":"kirodotdev/Kiro#11522","harness":"kiro","harness_name":"Kiro","repo":"kirodotdev/Kiro","number":11522,"title":"[Bug] Remote SSH completely broken: wget missing URL → version mismatch → local filesystem fallback","url":"https://github.com/kirodotdev/Kiro/issues/11522","state":"open","state_reason":null,"labels":["os: windows","ssh","theme:ssh-wsl"],"created":"2026-09-22T14:27:37Z","updated":"2026-09-23T16:38:05Z","closed":null,"reactions":0,"thumbs_up":0,"comments":2,"severity":"high","severity_reasons":["title:breakage"],"topic":"self-host/headless","classes":["self-host/headless","install/update"],"cosmetic_ui":false,"summary":"Remote SSH is completely non-functional due to a chain of three cascading bugs. The server binary cannot be downloaded, and even with manual installation, version mismatch causes silent fallback to the local filesystem while the status bar…","versions":["1.1.14","1.95.3","1.96.4"],"error_snippets":["bugs. The server binary cannot be downloaded, and even with manual","In `serverSetup.js` of the `labring.open-remote-ssh-for-trae` extension,","`VERSION_RELEASE_MAP` only contains two entries:"],"workaround":null,"fixed_in":null,"score":29.4,"first_seen":"2026-10-25T09:11:37Z"},{"id":"kirodotdev/Kiro#11502","harness":"kiro","harness_name":"Kiro","repo":"kirodotdev/Kiro","number":11502,"title":"Kio Down| Auto fallback","url":"https://github.com/kirodotdev/Kiro/issues/11502","state":"open","state_reason":null,"labels":["models","theme:slow-unresponsive","theme:unexpected-error"],"created":"2026-09-21T12:34:47Z","updated":"2026-09-23T16:14:02Z","closed":null,"reactions":0,"thumbs_up":0,"comments":3,"severity":"medium","severity_reasons":["class:crash/hang"],"topic":"crash/hang","classes":["crash/hang"],"cosmetic_ui":false,"summary":"Kiro is down from morning? I have to followup more than 200 times. WTH can't you fallback to available model, if you have availability issues. If none of the model is available, why can't you scale your systems? Kiro is down from morning?…","versions":["1.1.14"],"error_snippets":["WTH can't you fallback to available model, if you have availability issues.","If none of the model is available, why can't you scale your systems?"],"workaround":null,"fixed_in":null,"score":28.6,"first_seen":"2026-10-19T18:38:33Z"},{"id":"kirodotdev/Kiro#11349","harness":"kiro","harness_name":"Kiro","repo":"kirodotdev/Kiro","number":11349,"title":"## Crash Report #173","url":"https://github.com/kirodotdev/Kiro/issues/11349","state":"open","state_reason":null,"labels":["os: windows","theme:unexpected-error"],"created":"2026-09-12T03:43:29Z","updated":"2026-09-23T16:55:20Z","closed":null,"reactions":0,"thumbs_up":0,"comments":2,"severity":"high","severity_reasons":["title:breakage"],"topic":"crash/hang","classes":["crash/hang","always-on/daemon","self-host/headless","auth/session","network"],"cosmetic_ui":false,"summary":"Date/Time: September 11, 2026, ~04:15 UTC Error Code: 10737 (user-assigned) Task Being Executed: Discussing remaining Blade/Vue fixes after Agent removal What Was Completed Before Crash: Removed Jenssegers\\Agent dependency from 4 files…","versions":["1.0.437"],"error_snippets":["border-edge-top-color","2. JS Syntax Error — `missing } after function body` at feed:1238:1","4. CSS Typos — `border-edge-top-color` should be `border-top-color`"],"workaround":null,"fixed_in":null,"score":26.8,"first_seen":"2026-10-19T18:38:33Z"},{"id":"kirodotdev/Kiro#11636","harness":"kiro","harness_name":"Kiro","repo":"kirodotdev/Kiro","number":11636,"title":"[Windows] Session snapshot path construction breaks fs_write on absolute paths (ENOENT)","url":"https://github.com/kirodotdev/Kiro/issues/11636","state":"closed","state_reason":"not_planned","labels":["pending-triage"],"created":"2026-09-27T18:23:03Z","updated":"2026-09-30T20:47:21Z","closed":"2026-09-30T20:03:42Z","reactions":1,"thumbs_up":1,"comments":5,"severity":"low","severity_reasons":["low engagement"],"topic":"other","classes":[],"cosmetic_ui":false,"summary":"Windows 11 Pro, version 10.0.26200 (please check Help > About; not captured at report time) fswrite (and any operation that produces a session snapshot) fails with ENOENT whenever the target is an absolute Windows path outside ~/.kiro…","versions":["10.0.26200"],"error_snippets":["Something went wrong: [Error] ENOENT: no such file or directory,","ENOENT whenever the target is an absolute Windows path outside `~/.kiro`.","rather than the extension's `globalStorage` directory, so it may be a","different code path than either of those.","produces two visible symptoms in the same error:"],"workaround":null,"fixed_in":null,"score":20.6,"first_seen":"2026-10-19T18:38:33Z"}]}