Set thinking and effort in /model; start V3 cloud sessions before /repo
Kiro 2.23 makes /model the place to switch models and set thinking/effort (model-supported options, saved for later). V2 deprecates bare /effort. V3 can start a cloud session before a repo; attach with /repo or leave the repo optional.Why this loop
Reasoning setup is no longer split across commands: /model is the primary interface to pick a model and configure that model's thinking and effort in one panel, which only shows supported options and persists them. On V2, bare /effort is legacy (deprecation warning, then Effort in /model) while /effort <level> still works, so default muscle memory should move to /model. On V3, /effort still opens its own picker, and you can start a cloud session before connecting a repository—run /repo when you want one, or continue from the connection screen with the repository marked optional if no source provider is linked. Adopting that order unblocks cloud work and keeps reasoning controls in one place. Do not infer extra behavior from the unnamed Improvements/Fixes/Patches sections.
Proposed actions
- In Kiro, run /model, select the model, then set thinking and effort in that same panel so only supported options appear and Kiro saves them for future sessions.
- On Kiro V2, stop using bare /effort (it warns and opens Effort in /model); use /model for reasoning settings, and keep /effort <level> only as an explicit shortcut.
- On Kiro V3, start a cloud session before connecting a repository, then run /repo when you are ready to attach one.
- If no source provider is connected and Kiro opens the connection screen, continue with the repository marked optional instead of blocking on a repo first.
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: Set thinking and effort in /model; start V3 cloud sessions before /repo Summary: Kiro 2.23 makes /model the place to switch models and set thinking/effort (model-supported options, saved for later). V2 deprecates bare /effort. V3 can start a cloud session before a repo; attach with /repo or leave the repo optional. Primary source: https://kiro.dev/changelog/cli/2-23#patch-2-23-1
Why it matters
Reasoning setup is no longer split across commands: /model is the primary interface to pick a model and configure that model's thinking and effort in one panel, which only shows supported options and persists them. On V2, bare /effort is legacy (deprecation warning, then Effort in /model) while /effort <level> still works, so default muscle memory should move to /model. On V3, /effort still opens its own picker, and you can start a cloud session before connecting a repository—run /repo when you want one, or continue from the connection screen with the repository marked optional if no source provider is linked. Adopting that order unblocks cloud work and keeps reasoning controls in one place. Do not infer extra behavior from the unnamed Improvements/Fixes/Patches sections.
Suggested actions
- In Kiro, run /model, select the model, then set thinking and effort in that same panel so only supported options appear and Kiro saves them for future sessions.
- On Kiro V2, stop using bare /effort (it warns and opens Effort in /model); use /model for reasoning settings, and keep /effort <level> only as an explicit shortcut.
- On Kiro V3, start a cloud session before connecting a repository, then run /repo when you are ready to attach one.
- If no source provider is connected and Kiro opens the connection screen, continue with the repository marked optional instead of blocking on a repo first.
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-2-23-1-set-thinking-and-effort-in-model-start-v3-cloud-sessions-bef and mark Applied, Skipped, or Failed. Proposal id: a47e8d5e-78ca-4492-9971-c3def8a15397
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.