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 Kiro CLI V3 Workflows and switch Classic sessions to the terminal UI Summary: Kiro 2.26.1 adds opt-in V3 Workflows for reusable multi-step tasks, Classic deprecation notices that name the flag/env/setting still launching Classic, and stricter V3 approvals for Hook/LSP writes, MCP tools, and shells in untrusted workspaces. Primary source: https://kiro.dev/changelog/#v2-26-1

Why it matters

Workflows are opt-in in V3: open /settings, enable Features > Workflows, then restart Kiro CLI before they apply. After that, capture recurring multi-step work as a Workflow (ask Kiro to create one from the outcome you want, or launch with /workflow run) and manage runs with /workflow instead of re-prompting. Classic sessions now show a deprecation notice that identifies the flag, environment variable, or saved setting that launched Classic and points to terminal-UI migration guidance—follow it so you are not still starting Classic. V3 also tightens approval checks for Hook and LSP file writes, for MCP tools and shell commands in untrusted workspaces, and for approvals that change while an action waits; treat those prompts as required gates rather than noise.

Suggested actions

1. In a Kiro CLI V3 session, open /settings, choose Features, enable Workflows, then restart Kiro CLI so reusable multi-step Workflows are available.
2. Ask Kiro: create a Workflow from this recurring multi-step outcome: [describe the outcome]. Then launch it with /workflow run and use /workflow commands to inspect and manage the run.
3. On the next Classic session start, read the deprecation notice for the flag, environment variable, or saved setting that launched Classic, then follow its guidance to switch to the terminal UI.
4. In untrusted workspaces, explicitly approve V3 checks for Hook and LSP file writes, MCP tools, and shell commands, and re-approve if the approval changes while an action is waiting.

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-26-1-enable-kiro-cli-v3-workflows-and-switch-classic-sessions-to and mark Applied, Skipped, or Failed. Proposal id: c8d17ead-d293-47ae-8257-5c806ab082e0

Your job

1. Restate the change in one sentence.
2. Propose a minimal plan for my repo (or a throwaway pilot).
3. Implement only what I approve; prefer small diffs and tests.
4. Call out risks (permissions, breaking APIs, cost).

Start by confirming you understood the proposal.