Application Panicked (crash)

### Checks

- [x] I have searched [github.com/aws/amazon-q-developer-cli/issues](https://github.com/aws/amazon-q-developer-cli/issues?q=) and there are no duplicates of my issue
- [x] I have run `q doctor` in the affected terminal session
- [x] I have run `q restart` and replicated the issue again

### Operating system

Linux 6.1.0-41-amd64 - Debian GNU/Linux 12 (bookworm)

### Expected behaviour

i expected swap agent can be done by the following command

### Actual behaviour

Usage: /agent

Commands:
list List all available agents
create Create a new agent with the specified name
edit Edit an existing agent configuration
generate Generate an agent configuration using AI
schema Show agent config schema
set-default Define a default agent to use when kiro-cli chat launches
swap Swap to a new agent at runtime
help Print this message or the help of the given subcommand(s)

Options:
-h, --help Print help (see more with '--help')

> /agent swap

The application panicked (crashed).
Message: index out of bounds: the len is 1 but the index is 1
Location: /home/codebuild-user/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/dialoguer-0.11.0/src/prompts/select.rs:284

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
➜ portfolio git:(main) ✗ kiro-cli
Welcome to Kiro!

### Steps to reproduce

please guide me to reproduce more log/error messages

### Environment

```yaml

[q-details]
version = "1.21.0"
hash = "dc54efd85f411d6b4347d192733ff40650d38dfb"
date = "2025-11-26T22:30:26.062904Z (13d ago)"
variant = "minimal"

[system-info]
chip = "Intel(R) Xeon(R) E-2324G CPU @ 3.10GHz"
total-cores = 4
memory = "62.64 GB"

[system-info.os.linux]
kernel_version = "6.1.0-41-amd64"
id = "debian"
name = "Debian GNU/Linux"
pretty_name = "Debian GNU/Linux 12 (bookworm)"
version_id = "12"
version = "12 (bookworm)"

[environment]
cwd = "/home/USER"
cli-path = "/home/USER"
os = "Linux"
shell-path = "/usr/bin/zsh"
shell-version = "5.9"
install-method = "unknown"
in-ssh = true

[env-vars]
PATH = "/run/user/1000/fnm_multishells/949215_1765287755689/bin:/home/USER/.local/share/fnm:/run/user/1000/fnm_multishells/949212_1765287755671/bin:/home/USER/.local/share/fnm:/run/user/1000/fnm_multishells/4130825_1765078628196/bin:/home/USER/.local/share/fnm:/run/user/1000/fnm_multishells/4130822_1765078628180/bin:/home/USER/.local/share/fnm:/usr/local/bin:/usr/bin:/bin:/usr/games:/home/USER/.local/bin:/home/USER/.local/bin:/home/USER/.local/bin:/home/USER/.turso:/home/USER/.local/bin:/home/USER/.local/bin:/home/USER/.turso"
Q_SET_PARENT_CHECK = "1"
SHELL = "/bin/zsh"
TERM = "tmux-256color"
XDG_SESSION_TYPE = "tty"
```

Inizia riproducendo `/agent swap` con Kiro CLI 1.21.0 su Debian 12, quindi eseguilo nuovamente con `RUST_BACKTRACE=1` per acquisire lo stack trace omesso. Ispeziona il flusso di agent swap e il prompt di selezione di dialoguer coinvolto dal panic. Il lavoro è completato quando il comando termina senza un crash di index-out-of-bounds.

Scritto dal modello di indicizzazione a partire dal testo della issue.