After 2026-05-06 update chat.defaultAgent corrupted

[AlexeySolonenko]

Before opening, please confirm:

• I have searched for duplicate or closed issues

Operating System

macOS

Kiro Version

2.2.2

Bug Description

Before:
chat.defaultAgent="custom_agent"

kiro-cli --agent "non-existent-agent" => custom_agent
kiro-cli --agent => custom_agent

After the kiro cli update:
kiro-cli --agent "non-existent-agent" => default_agent this stopped working
kiro-cli --agent => custom_agent

Steps to Reproduce

After the kiro cli update:
kiro-cli --agent "non-existent-agent" => default_agent this stopped working
kiro-cli --agent => custom_agent

Expected Behavior

kiro-cli --agent "non-existent-agent" => custom_agent
kiro-cli --agent => custom_agent

Conversation ID

No response

Additional Context

not known

[github-actions]

Thanks for reporting this issue! It sounds like the recent update changed how the CLI handles fallback behavior when a non-existent agent is specified, causing it to ignore your configured chat.defaultAgent setting. A maintainer will take a look at this shortly. We appreciate you providing the clear before/after comparison — that's really helpful for tracking down the regression! 🙏

[AnilMaktala]

We're doing a periodic backlog review and noticed this issue has been inactive for several months. Kiro has shipped a lot of changes since this was filed — we're now on IDE 1.0.309 and CLI 2.18.1 — and without any community uptake, we can't confidently prioritize it.

Closing to keep the backlog focused, but not as a dismissal. If you're still seeing this or others share the same experience, a new issue with your current version and any updated details would help us pick it back up. Issues with 👍 reactions from the community rise to the top fastest.