Answer: Powers sync by following one of two paths: Catalog Powers are installed by name when the Power name exactly matches a Power in the catalog, while Custom Powers that are not in the catalog upload as individual text files. Status: Confirmed Entry: tool/kiro/integrations/powers-sync Revision: 2 Digest: sha256:8f8eaa520d5fb70c (changes whenever the content changes) Timeline: Created: 2026-11-13T03:45:57Z Last changed: 2026-11-20T13:33:31Z (Case-only name differences: — → refused) Last verified: 2026-11-20T13:33:31Z Next check: 2026-11-21T13:33:31Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Catalog Powers sync | Kiro installs it by name | [1] | 2026-11-20 Custom Powers sync | upload as individual text files | [1] | 2026-11-20 Actionable file in upload review | POWER.md | [1] | 2026-11-20 Case-only name differences | refused | [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:31Z Quote: "If the Power name exactly matches a Power in the catalog , Kiro installs it by name" (Supports: Catalog Powers sync) Quote: "Powers that are not in the catalog upload as individual text files." (Supports: Custom Powers sync) Quote: "Only POWER.md is actionable in the upload review." (Supports: Actionable file in upload review) Quote: "Names that differ from catalog or Amazon-managed Powers only by letter case are refused." (Supports: Case-only name differences) 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:31Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:33:31Z Last attempt: 2026-11-20T13:33:31Z Notes and limitations: Extracted automatically from a single official source (section "How Powers sync"). Related: https://latestn.com/tool/kiro/integrations/remote-connection-methods What connection methods does Kiro support for adding a remote instance? https://latestn.com/tool/kiro/integrations/replace-aws-tool-with-mcp-server How do I replace the Kiro CLI 2.x AWS tool with an MCP server in V3? https://latestn.com/tool/kiro/integrations/set-up-mcp How do I set up MCP in Kiro? https://latestn.com/tool/kiro/integrations/mobile-git-providers How do I connect a Git provider in the Kiro mobile app? https://latestn.com/tool/kiro/integrations/open-pull-request How do I open a pull request from a Kiro web agent session? https://latestn.com/tool/kiro/integrations/persistent-ssh-tunnel-dashboard How do I set up a persistent SSH tunnel to access the Kiro Crew dashboard on a remote host? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T13:33:31Z | changed | Case-only name differences: — → refused | [1] 2026-11-20T13:33:31Z | changed | Actionable file in upload review: — → POWER.md | [1] 2026-11-20T13:33:31Z | changed | Custom Powers sync: — → upload as individual text files | [1] 2026-11-20T13:33:31Z | changed | Catalog Powers sync: — → Kiro installs it by name | [1] 2026-11-20T13:33:31Z | changed | case mismatch: Names that differ from catalog or Amazon-managed Powers only by letter case are refused → — | [1] 2026-11-20T13:33:31Z | changed | custom path: upload as individual text files → — | [1] 2026-11-20T13:33:31Z | changed | actionable file: Only POWER.md is actionable in the upload review → — | [1] 2026-11-20T13:33:31Z | changed | catalog path: Kiro installs it by name and the service supplies the reviewed file set → — | [1] 2026-11-20T13:33:31Z | changed | sync paths: Powers follow one of two paths → — | [1] 2026-11-13T03:45:57Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/integrations/powers-sync/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/integrations/powers-sync POST: https://latestn.com/dispute/tool/kiro/integrations/powers-sync with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/integrations/powers-sync?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do Kiro Powers sync with cloud configuration? Revision 2, last verified 2026-11-20T13:33:31Z. https://latestn.com/tool/kiro/integrations/powers-sync (accessed 2026-11-21T09:53:23Z). @misc{LatestN_tool_kiro_integrations_powers_sync_r2, title = {How do Kiro Powers sync with cloud configuration?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/integrations/powers-sync}}, note = {Revision 2; digest sha256:8f8eaa520d5fb70c; last verified 2026-11-20T13:33:31Z; accessed 2026-11-21T09:53:23Z} } 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/integrations/powers-sync