Enable Apply your cloud configuration to local Kiro CLI V3 sessions
Kiro v2.21.3 adds a V3 session dashboard (/sessions), a /config panel for agents, MCP servers, Powers, Steering, Skills, and Hooks, and Configuration Sync that can apply uploaded cloud .kiro config to new local CLI sessions without writing files locally.Why this loop
Kiro 2.21.1–2.21.3 add three V3 surfaces for session and config management. Open /sessions or run kiro-cli chat --sessions to browse, search, resume, and clean up past local and cloud sessions instead of restarting work. In a V3 session, run /config to see agents, MCP servers, Powers, Steering, Skills, and Hooks in one view, labeled local, cloud, or both when source info is available. Upload your personal .kiro configuration with Configuration Sync in Kiro Web so cloud sessions use it automatically; enable Apply your cloud configuration to local sessions to load cloud Steering, custom agents, Skills, Powers, and Hooks in new local CLI sessions without writing those files to your local .kiro directory. Confirm the loaded set with /config after enabling the flag. AWS's ISO/IEC 27001:2022 certification now includes Kiro in scope (verified by EY CertifyPoint) for security and vendor-risk reviews.
Proposed actions
- Run kiro-cli chat --sessions (or type /sessions in a Kiro V3 session) to browse, search, resume, and clean up past sessions stored locally or in the cloud.
- In a local or cloud V3 session, run /config to view configured agents, MCP servers, Powers, Steering, Skills, and Hooks in one terminal view, including whether each item is local, cloud, or both.
- In Kiro Web, upload your personal .kiro configuration with Configuration Sync so cloud sessions use that configuration automatically.
- Enable Apply your cloud configuration to local sessions so new local CLI V3 sessions load cloud Steering, custom agents, Skills, Powers, and Hooks without writing those files to your local .kiro directory.
- After enabling cloud config on a new local CLI V3 session, run /config again and confirm Steering, custom agents, Skills, Powers, and Hooks show as cloud (or both) rather than missing.
Agent prompt
Paste into your agent or query via MCP (get_agent_prompt) — free, no extra AI costCopilot Chat / Agent mode
DevAgentRadar → GitHub Copilot
You are helping me adopt a real coding-assistant change. Work only from the facts below. Do not invent features.
Context
Assistant: Kiro Proposal: Enable Apply your cloud configuration to local Kiro CLI V3 sessions Summary: Kiro v2.21.3 adds a V3 session dashboard (/sessions), a /config panel for agents, MCP servers, Powers, Steering, Skills, and Hooks, and Configuration Sync that can apply uploaded cloud .kiro config to new local CLI sessions without writing files locally. Primary source: https://kiro.dev/changelog/#v2-21-3
Why it matters
Kiro 2.21.1–2.21.3 add three V3 surfaces for session and config management. Open /sessions or run kiro-cli chat --sessions to browse, search, resume, and clean up past local and cloud sessions instead of restarting work. In a V3 session, run /config to see agents, MCP servers, Powers, Steering, Skills, and Hooks in one view, labeled local, cloud, or both when source info is available. Upload your personal .kiro configuration with Configuration Sync in Kiro Web so cloud sessions use it automatically; enable Apply your cloud configuration to local sessions to load cloud Steering, custom agents, Skills, Powers, and Hooks in new local CLI sessions without writing those files to your local .kiro directory. Confirm the loaded set with /config after enabling the flag. AWS's ISO/IEC 27001:2022 certification now includes Kiro in scope (verified by EY CertifyPoint) for security and vendor-risk reviews.
Suggested actions
- Run kiro-cli chat --sessions (or type /sessions in a Kiro V3 session) to browse, search, resume, and clean up past sessions stored locally or in the cloud.
- In a local or cloud V3 session, run /config to view configured agents, MCP servers, Powers, Steering, Skills, and Hooks in one terminal view, including whether each item is local, cloud, or both.
- In Kiro Web, upload your personal .kiro configuration with Configuration Sync so cloud sessions use that configuration automatically.
- Enable Apply your cloud configuration to local sessions so new local CLI V3 sessions load cloud Steering, custom agents, Skills, Powers, and Hooks without writing those files to your local .kiro directory.
- After enabling cloud config on a new local CLI V3 session, run /config again and confirm Steering, custom agents, Skills, Powers, and Hooks show as cloud (or both) rather than missing.
After you finish
Do not report this as applied to DevAgentRadar. You cannot write the visitor's loop.
Tell the human: open https://devagentradar.com/proposals/kiro-v2-21-3-enable-apply-your-cloud-configuration-to-local-kiro-cli-v3- and mark Applied, Skipped, or Failed. Proposal id: 397bb8ac-2a0a-458f-9330-5ead73c18371
Your job
- Restate the change in one sentence.
- Propose a minimal plan for my repo (or a throwaway pilot).
- Implement only what I approve; prefer small diffs and tests.
- Call out risks (permissions, breaking APIs, cost).
Start by confirming you understood the proposal.
Your loop
This browser · no sign-in · not shared as “you”After you run the prompt
Only you can mark this. Agents cannot write your loop.
Your decision stays on this device. A public tally appears after a few votes.