Answer: Kiro retrieves all spec files from the .kiro subfolder under each root folder and displays them as a unified list in the Specs section of the Kiro panel, with the containing root folder's name shown next to each spec. You can ask Kiro to work on a spec under any root folder, and when creating a new spec Kiro determines the appropriate root folder to place it into. Status: Confirmed Entry: tool/kiro/features/specs-in-multi-root-workspaces Revision: 2 Digest: sha256:aa5feb5f27bfaa85 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:42:49Z Last changed: 2026-11-20T13:29:37Z (Spec location: — → .kiro subfolder) Last verified: 2026-11-20T13:29:37Z Next check: 2026-11-21T13:29:37Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Spec location | .kiro subfolder | [1] | 2026-11-20 Display | unified list | [1] | 2026-11-20 Root folder label | The name of the containing root folder is displayed next to each spec. | [1] | 2026-11-20 Working on specs | any of the root folders | [1] | 2026-11-20 New spec placement | determine the appropriate root folder | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Multi-root workspaces - Editor - IDE 1.x - Docs - Kiro". https://kiro.dev/docs/ide/editor/multi-root-workspaces/ Role: primary. Accessed: 2026-11-20T13:29:37Z Quote: "Kiro will retrieve all spec files from the .kiro subfolder under each of the root folders" (Supports: Spec location) Quote: "display them as a unified list in the Specs section of the Kiro panel" (Supports: Display) Quote: "The name of the containing root folder is displayed next to each spec." (Supports: Root folder label) Quote: "You can ask Kiro to work on a spec defined under any of the root folders." (Supports: Working on specs) Quote: "When creating a new spec, Kiro will determine the appropriate root folder to place the spec into." (Supports: New spec placement) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: 0d110ce41914f19ac0fd7cc360c131ac687c1e501f1160ae6cb9f26b75930995 (captured 2026-11-20T13:29:38Z) 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:29:37Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:29:37Z Last attempt: 2026-11-20T13:29:37Z Notes and limitations: Extracted automatically from a single official source (section "Specs"). Related: https://latestn.com/tool/kiro/features/start-cloud-session How do I start a cloud session in Kiro? https://latestn.com/tool/kiro/features/start-dev-server How do I start a dev server in Kiro? https://latestn.com/tool/kiro/features/steer-vs-queue-vs-cancel What is the difference between steer mode, queue mode, and cancel in Kiro CLI? https://latestn.com/tool/kiro/features/shell-tools What shell tools does Kiro provide? https://latestn.com/tool/kiro/features/skills-vs-steering-powers How do Kiro skills differ from steering and powers? https://latestn.com/tool/kiro/features/snapshot-contents What is included in a Kiro Crew snapshot? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T13:29:37Z | changed | Spec location: — → .kiro subfolder | [1] 2026-11-20T13:29:37Z | changed | New spec placement: determine the appropriate root folder to place the spec into → determine the appropriate root folder | [1] 2026-11-20T13:29:37Z | changed | Root folder label: The name of the containing root folder is displayed next to each spec → The name of the containing root folder is displayed next to each spec. | [1] 2026-11-20T13:29:37Z | changed | Display: unified list in the Specs section of the Kiro panel → unified list | [1] 2026-11-20T13:29:37Z | changed | Spec source location: .kiro subfolder under each of the root folders → — | [1] 2026-11-13T03:42:49Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/features/specs-in-multi-root-workspaces/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/features/specs-in-multi-root-workspaces POST: https://latestn.com/dispute/tool/kiro/features/specs-in-multi-root-workspaces with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/features/specs-in-multi-root-workspaces?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do specs work across multiple roots in Kiro multi-root workspaces? Revision 2, last verified 2026-11-20T13:29:37Z. https://latestn.com/tool/kiro/features/specs-in-multi-root-workspaces (accessed 2026-11-21T10:00:27Z). @misc{LatestN_tool_kiro_features_specs_in_multi_root_workspaces_r2, title = {How do specs work across multiple roots in Kiro multi-root workspaces?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/features/specs-in-multi-root-workspaces}}, note = {Revision 2; digest sha256:aa5feb5f27bfaa85; last verified 2026-11-20T13:29:37Z; accessed 2026-11-21T10:00:27Z} } 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/features/specs-in-multi-root-workspaces