Answer: An experimental feature or command may not work because the feature is not enabled; you should verify the feature is enabled and ensure the feature is enabled before using its commands. For example, /knowledge only works when knowledge management is enabled. Status: Confirmed Entry: tool/kiro/troubleshooting/experimental-feature-not-working Revision: 2 Digest: sha256:86966c037bf9b5f6 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:36:41Z Last changed: 2026-11-20T13:20:12Z (re-enable command: — → kiro-cli settings chat.enableFeatureName true) Last verified: 2026-11-20T13:20:12Z Next check: 2026-11-21T13:20:12Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of verification command | kiro-cli settings list | grep -i enable | [1] | 2026-11-20 disable command | kiro-cli settings chat.enableFeatureName false | [1] | 2026-11-20 re-enable command | kiro-cli settings chat.enableFeatureName true | [1] | 2026-11-20 example command | /knowledge | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Experimental - CLI - Docs - Kiro". https://kiro.dev/docs/cli/experimental/ Role: primary. Accessed: 2026-11-20T13:20:12Z Quote: "Verify feature is enabled: bash kiro-cli settings list | grep -i enable" (Supports: verification command) Quote: "Try disabling and re-enabling: bash kiro-cli settings chat.enableFeatureName false" (Supports: disable command) Quote: "kiro-cli settings chat.enableFeatureName true" (Supports: re-enable command) Quote: "For example, /knowledge only works when knowledge management is enabled." (Supports: example command) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: 5055d955885060cc1e240e225ef2c75d8dfe041f322c8261478f1b9dbc2b3d37 (captured 2026-11-20T13:20:10Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. Cross-check: not-available at 2026-11-20T13:20:12Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:20:12Z Last attempt: 2026-11-20T13:20:12Z Notes and limitations: Extracted automatically from a single official source (section "Troubleshooting"). Related: https://latestn.com/tool/kiro/troubleshooting/file-reference-limitations What are the current limitations of file references in Kiro CLI? https://latestn.com/tool/kiro/troubleshooting/fix-auth-browser-redirect How do I fix browser redirect failures during Kiro authentication on Windows or macOS? https://latestn.com/tool/kiro/troubleshooting/fix-autocomplete-not-working What should I do if autocomplete is not working in Kiro CLI? https://latestn.com/tool/kiro/troubleshooting/dev-server-wont-start How do I troubleshoot a dev server process that won't start in Kiro? https://latestn.com/tool/kiro/troubleshooting/diff-tool-troubleshooting What should I do if my custom diff tool isn't working in Kiro CLI? https://latestn.com/tool/kiro/troubleshooting/enterprise-unsupported-and-known-issues What capabilities are not supported or have known issues in Kiro Enterprise Management? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T13:20:12Z | changed | re-enable command: — → kiro-cli settings chat.enableFeatureName true | [1] 2026-11-20T13:20:12Z | changed | disable command: — → kiro-cli settings chat.enableFeatureName false | [1] 2026-11-20T13:20:12Z | changed | verification command: — → kiro-cli settings list | grep -i enable | [1] 2026-11-20T13:20:12Z | changed | requirement: Ensure the feature is enabled before using its commands → — | [1] 2026-11-20T13:20:12Z | changed | verification step: Verify feature is enabled → — | [1] 2026-11-13T03:36:41Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/troubleshooting/experimental-feature-not-working/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/kiro/troubleshooting/experimental-feature-not-working POST: https://latestn.com/dispute/tool/kiro/troubleshooting/experimental-feature-not-working with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/troubleshooting/experimental-feature-not-working?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). Why is an experimental feature or command not working in Kiro CLI? Revision 2, last verified 2026-11-20T13:20:12Z. https://latestn.com/tool/kiro/troubleshooting/experimental-feature-not-working (accessed 2026-11-21T10:03:37Z). @misc{LatestN_tool_kiro_troubleshooting_experimental_feature_not_working_r2, title = {Why is an experimental feature or command not working in Kiro CLI?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/troubleshooting/experimental-feature-not-working}}, note = {Revision 2; digest sha256:86966c037bf9b5f6; last verified 2026-11-20T13:20:12Z; accessed 2026-11-21T10:03:37Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/kiro/troubleshooting/experimental-feature-not-working