Enable cloud configuration for new local Kiro V3 CLI sessions
Kiro v2.21.1 adds a V3 session dashboard, a /config panel for agents, MCP, Powers, Steering, Skills, and Hooks, and Configuration Sync that can load uploaded cloud .kiro settings into new local CLI sessions without writing those files locally.Why this loop
Local CLI sessions often drift from the agents, MCP servers, Steering, Skills, Powers, and Hooks you already keep in Kiro Web. v2.21.1 lets you upload personal .kiro config with Configuration Sync, have cloud sessions use it automatically, and optionally apply that same cloud config to new local V3 CLI sessions without copying files into the local .kiro directory. Pair that with /sessions (or kiro-cli chat --sessions) to browse, search, resume, and clean up local and cloud history, and /config to see in one terminal view what is configured and whether each item is local, cloud, or both. Together those commands make session reuse, source-of-truth inspection, and cross-environment parity a default part of starting work instead of hunting scattered config files.
Proposed actions
- In Kiro Web, upload your personal .kiro configuration with Configuration Sync, then enable Apply your cloud configuration to local sessions so new local CLI sessions load cloud Steering, custom agents, Skills, Powers, and Hooks without writing those files to your local .kiro directory.
- From the terminal, run kiro-cli chat --sessions to browse, search, resume, and clean up past sessions stored locally or in the cloud.
- In a V3 Kiro session, type /sessions to open the dashboard and resume or clean up a matching local or cloud session instead of starting a duplicate thread.
- In a local or cloud V3 session, run /config to list configured agents, MCP servers, Powers, Steering, Skills, and Hooks and note whether each item is sourced as local, cloud, or both.
- Start a new local V3 CLI session after enabling cloud config, run /config, and confirm cloud Steering, custom agents, Skills, Powers, and Hooks appear without new files in the local .kiro directory.
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 cloud configuration for new local Kiro V3 CLI sessions Summary: Kiro v2.21.1 adds a V3 session dashboard, a /config panel for agents, MCP, Powers, Steering, Skills, and Hooks, and Configuration Sync that can load uploaded cloud .kiro settings into new local CLI sessions without writing those files locally. Primary source: https://kiro.dev/changelog/#v2-21-1
Why it matters
Local CLI sessions often drift from the agents, MCP servers, Steering, Skills, Powers, and Hooks you already keep in Kiro Web. v2.21.1 lets you upload personal .kiro config with Configuration Sync, have cloud sessions use it automatically, and optionally apply that same cloud config to new local V3 CLI sessions without copying files into the local .kiro directory. Pair that with /sessions (or kiro-cli chat --sessions) to browse, search, resume, and clean up local and cloud history, and /config to see in one terminal view what is configured and whether each item is local, cloud, or both. Together those commands make session reuse, source-of-truth inspection, and cross-environment parity a default part of starting work instead of hunting scattered config files.
Suggested actions
- In Kiro Web, upload your personal .kiro configuration with Configuration Sync, then enable Apply your cloud configuration to local sessions so new local CLI sessions load cloud Steering, custom agents, Skills, Powers, and Hooks without writing those files to your local .kiro directory.
- From the terminal, run kiro-cli chat --sessions to browse, search, resume, and clean up past sessions stored locally or in the cloud.
- In a V3 Kiro session, type /sessions to open the dashboard and resume or clean up a matching local or cloud session instead of starting a duplicate thread.
- In a local or cloud V3 session, run /config to list configured agents, MCP servers, Powers, Steering, Skills, and Hooks and note whether each item is sourced as local, cloud, or both.
- Start a new local V3 CLI session after enabling cloud config, run /config, and confirm cloud Steering, custom agents, Skills, Powers, and Hooks appear without new files in the local .kiro directory.
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-1-enable-cloud-configuration-for-new-local-kiro-v3-cli-sessio and mark Applied, Skipped, or Failed. Proposal id: e1383426-6d89-40bf-859a-c74fe38b2f6f
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.