Answer: Kiro's configuration sync limits include uploading one supported top-level folder at a time, with each uploaded item up to 4,000,000 bytes, and Skills or custom Powers can contain up to 50 files. Skills and custom Powers support text files only, and selecting an Update replaces the cloud copy rather than merging file contents. Status: Confirmed Entry: tool/kiro/pricing-and-limits/configuration-sync-limits Revision: 1 Digest: sha256:6dc96f5d3d387416 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:46:00Z Last changed: 2026-11-13T03:46:00Z Last verified: 2026-11-20T13:33:32Z Next check: 2026-11-21T13:33:32Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Unit | Source | As of Upload limit | one supported top-level folder at a time | | [1] | 2026-11-20 Item size limit | 4,000,000 bytes | bytes | [1] | 2026-11-20 Skill file limit | 50 files | files | [1] | 2026-11-20 Custom Power file limit | 50 files | files | [1] | 2026-11-20 Supported file types | text files only | | [1] | 2026-11-20 Update behavior | Selecting an Update replaces the cloud copy; uploads do not merge file contents. | | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Configuration Sync - Web - Docs - Kiro". https://kiro.dev/docs/web/cloud-configuration/ Role: primary. Accessed: 2026-11-20T13:33:32Z Quote: "Upload one supported top-level folder at a time." (Supports: Upload limit) Quote: "Each uploaded item can be up to 4,000,000 bytes." (Supports: Item size limit) Quote: "A Skill can contain up to 50 files." (Supports: Skill file limit) Quote: "A custom Power can contain up to 50 files." (Supports: Custom Power file limit) Quote: "Skills and custom Powers support text files only." (Supports: Supported file types) Quote: "Selecting an Update replaces the cloud copy; uploads do not merge file contents." (Supports: Update behavior) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: 1a975671b820beb973e1ba652512c8201386f18ba0e937ebd22c8b758d099d65 (captured 2026-11-20T13:33:29Z) 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:33:32Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:33:32Z Last attempt: 2026-11-20T13:33:32Z Notes and limitations: Extracted automatically from a single official source (section "Limits"). Related: https://latestn.com/tool/kiro/pricing-and-limits/credit-pooling What is credit pooling in Kiro enterprise? https://latestn.com/tool/kiro/pricing-and-limits/crew-credit-usage-forecast How do I see Kiro Crew's credit usage and estimated token forecast? https://latestn.com/tool/kiro/pricing-and-limits/crew-resource-limits-machine-full How do I check Kiro Crew's resource limits and what happens when the machine is full? https://latestn.com/tool/kiro/pricing-and-limits/cloud-sessions-limitations What are the current limitations of Kiro cloud sessions? https://latestn.com/tool/kiro/pricing-and-limits/compaction-limitations What are the limitations of compaction in Kiro? https://latestn.com/tool/kiro/pricing-and-limits/composer-limits-context-warnings What are the composer limits and context-window warnings in Kiro Crew chat? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:46:00Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/pricing-and-limits/configuration-sync-limits/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/pricing-and-limits/configuration-sync-limits POST: https://latestn.com/dispute/tool/kiro/pricing-and-limits/configuration-sync-limits with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/pricing-and-limits/configuration-sync-limits?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What are the limits of Kiro's configuration sync? Revision 1, last verified 2026-11-20T13:33:32Z. https://latestn.com/tool/kiro/pricing-and-limits/configuration-sync-limits (accessed 2026-11-21T10:01:19Z). @misc{LatestN_tool_kiro_pricing_and_limits_configuration_sync_limits_r1, title = {What are the limits of Kiro's configuration sync?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/pricing-and-limits/configuration-sync-limits}}, note = {Revision 1; digest sha256:6dc96f5d3d387416; last verified 2026-11-20T13:33:32Z; accessed 2026-11-21T10:01:19Z} } 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/pricing-and-limits/configuration-sync-limits