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

## Active
- [MEDIUM] Remote MCP (Atlassian, OAuth) times out after "Authorization Successful" (https://github.com/kirodotdev/Kiro/issues/12054)
  - symptom: 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 Atlassi
  - versions: 10.0.26300, 1.4.13, 2.4
  - error: `~50 s, then "MCP server 'atlassian' connection timed out after 60000ms".`
  - workaround: none stated
- [HIGH] Reliability regression: file edits fail, IDE freezes, spec operations die with network errors, and in-app bug reporter i (https://github.com/kirodotdev/Kiro/issues/11754)
  - symptom: Windows 11 Business 25H2 Summary Over the past several weeks Kiro has become unreliable across core operations
  - versions: 1.1.14
  - error: `Summary Over the past several weeks Kiro has become unreliable across core operations. File edits fail, the IDE becomes unresponsive, and spec (design/task) ope`
  - workaround: none stated
- [HIGH] [CLI V3 Regression][Windows][2.31.1] `skill://` resources not recognized and absolute paths resolved incorrectly (https://github.com/kirodotdev/Kiro/issues/11980)
  - symptom: 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 ha
  - versions: 2.31.1
  - error: `for the tested paths results in no skill entry in`
  - workaround: Using `file://` as a workaround is not equivalent to registering a skill for progressive loading. [issue body]
- [MEDIUM] MCP tools not injected into LLM tool list for workspace-defined agents (.kiro/agents/*.json) (https://github.com/kirodotdev/Kiro/issues/5873)
  - symptom: Any agent defined via .kiro/agents/.json does not receive MCP tools in its tool list
  - versions: 1.26.2
  - error: `All tests run from the same workspace directory. MCP servers initialized successfully (✓) in every case.`
  - workaround: `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. [issue body]
- [MEDIUM] kiro-cli headless with API key: GetProfile returns "User is not authorized to access this feature", governance fails, MC (https://github.com/kirodotdev/Kiro/issues/11777)
  - symptom: Linux (Ubuntu) cloud server in Tokyo kiro-cli 2.27.1 Account: Kiro Pro, individual account, signed up with Google (Gmail) sign-in
  - versions: 2.27.1
  - error: `kiro-cli chat --agent-engine v2 --no-interactive --output-format stream-json --model claude-opus-5.5`
  - workaround: none stated
- [MEDIUM] kiro-cli acp: session/new blocks ~66 s downloading the 83 MB all-MiniLM-L6-v2 model; a client timeout restarts it from z (https://github.com/kirodotdev/Kiro/issues/12118)
  - symptom: kiro-cli acp does not answer session/new until it has downloaded the 83 MB all-MiniLM-L6-v2 semantic-search model
  - versions: 2.34.0, 11.3, 14.2
  - error: `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.`
  - workaround: none stated
- [MEDIUM] Workflow run stuck "running" on a stale pr-loop watch — cannot be aborted (update_workflow fails to load saved state), s (https://github.com/kirodotdev/Kiro/issues/12114)
  - symptom: 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 th
  - versions: 1.4.26
  - error: `Component: Workflow engine / orchestration (background workflow runs)`
  - workaround: none stated
- [MEDIUM] kiro-cli v3: local command sandbox blocks the user-database lookup on macOS, so ssh and ssh-keygen can't run (https://github.com/kirodotdev/Kiro/issues/12035)
  - symptom: 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
  - versions: 2.32.0
  - error: `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 wh`
  - workaround: none stated
- [MEDIUM] Task-execution tools (task_get/task_update/task_status) and spec-task-execution dispatch intermittently drop out mid-ses (https://github.com/kirodotdev/Kiro/issues/11981)
  - symptom: 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 
  - versions: 1.3.11
  - error: `What happens: During a spec task-execution session, the task-status tools and the spec-task-execution subagent dispatch repeatedly become unavailable ("Tool X i`
  - workaround: none stated
- [MEDIUM] /mcp auth for a remote OAuth server never surfaces the authorization URL (Google Workspace MCP, 403-not-401 servers) (https://github.com/kirodotdev/Kiro/issues/11816)
  - symptom: 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
  - versions: 2.28.0
  - error: `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 th`
  - workaround: none stated
- [MEDIUM] Stuck on Working (https://github.com/kirodotdev/Kiro/issues/12056)
  - symptom: its working like about 10 min and its stuck then i was cancel the converstation and type continue and its stuck on working...
  - versions: 1.1.70
  - workaround: none stated
- [HIGH] Regression: `oauthScopes` still dropped from the OAuth authorization request on 2.26.0 (optional scope absent, tool call (https://github.com/kirodotdev/Kiro/issues/11700)
  - symptom: macOS 26.7 (arm64, Apple Silicon) kiro-cli 2.26.0 — KAS 2.26.0, bundled node v22.22.2 Summary
  - versions: 2.26.0, 2.12.0
  - error: `"example-remote": {`
  - workaround: none stated