Feature request: add a CLI flag or persistent setting to pre-select the license tier (Free/Pro) at startup, so users don't have to choose interactively every time. For example: --tier pro or a setting like license.tier=pro

[ScripDid]

Checks

• I have searched github.com/aws/amazon-q-developer-cli/issues and there are no duplicates of my issue
• I have run q doctor in the affected terminal session
• I have run q restart and replicated the issue again

Operating system

Linux 6.6.114.1-microsoft-standard-WSL2 - Ubuntu 24.04.3 LTS

Expected behaviour

When a persistent setting is configured (e.g. kiro-cli settings "license.tier" "pro"), the CLI should skip the interactive license selection prompt and automatically use the configured
tier.

Alternatively, a CLI flag like kiro-cli chat --tier pro should allow bypassing the prompt for a single session.

This would enable seamless startup without manual interaction every time, especially useful for scripting and daily usage.

Actual behaviour

Every time kiro-cli chat is launched, the user is prompted to interactively select a license tier (Free/Pro). There is no way to persist this choice or bypass the prompt via a CLI flag,
setting, or environment variable.

Steps to reproduce

1. Run kiro-cli chat
2. Observe the interactive prompt asking to select a license tier (Free/Pro)
3. There is no flag, setting, or config file option to skip this step

Environment

<This will be visible to anyone. Do not include personal or sensitive information>

[q-details]
version = "1.27.0"
hash = "b9a4c4fd6bc4a3a624e0b2e03722a388fe28a8fe"
date = "2026-02-27T21:18:34.179205Z (87d ago)"
variant = "minimal"

[system-info]
chip = "13th Gen Intel(R) Core(TM) i7-1355U"
total-cores = 6
memory = "15.46 GB"

[system-info.os.linux]
kernel_version = "6.6.114.1-microsoft-standard-WSL2"
id = "ubuntu"
name = "Ubuntu"
pretty_name = "Ubuntu 24.04.3 LTS"
version_id = "24.04"
version = "24.04.3 LTS (Noble Numbat)"

[environment]
cwd = "/home/USER"
cli-path = "/home/USER"
os = "Linux"
shell-path = "/home/USER/.local/bin/kiro-cli-chat"
install-method = "unknown"
in-wsl = true

[env-vars]
DISPLAY = ":0"
PATH = "/usr/local/bin/:/home/USER/.local/bin:/home/USER/.local/bin:/usr/local/bin/:/home/USER/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/lib/wsl/lib:/mnt/c/WINDOWS/system32:/mnt/c/WINDOWS:/mnt/c/WINDOWS/System32/Wbem:/mnt/c/WINDOWS/System32/WindowsPowerShell/v1.0/:/mnt/c/WINDOWS/System32/OpenSSH/:/mnt/c/_APPS_/kubectl:/mnt/c/_APPS_/gitleaks_8.1.2/:/mnt/c/cygwin64/bin:/mnt/c/_APPS_/ffmpeg-2025-02-06-git-6da82b4485-full_build/bin:/mnt/c/Program Files/Amazon/SessionManagerPlugin/bin/:/mnt/c/Program Files/Amazon/AWSCLIV2/:/mnt/c/Program Files/Calibre2/:/mnt/c/Program Files/nodejs/:/mnt/c/Program Files/Git/cmd:/mnt/c/Users/d.zola.ext/AppData/Local/Programs/Python/Python314/Scripts/:/mnt/c/Users/d.zola.ext/AppData/Local/Programs/Python/Python314/:/mnt/c/Windows/system32/config/systemprofile/AppData/Local/Microsoft/WindowsApps:/mnt/c/Users/d.zola.ext/AppData/Local/Programs/Lens/resources/cli/bin:/mnt/c/Users/d.zola.ext/AppData/Local/Programs/Microsoft VS Code/bin:/mnt/c/cygwin64/bin:/mnt/c/Users/d.zola.ext/AppData/Local/Microsoft/WindowsApps:/mnt/c/Users/d.zola.ext/AppData/Local/Microsoft/WinGet/Packages/ahmetb.kubectx_Microsoft.Winget.Source_8wekyb3d8bbwe:/mnt/c/Users/d.zola.ext/AppData/Local/Microsoft/WinGet/Packages/ahmetb.kubens_Microsoft.Winget.Source_8wekyb3d8bbwe:/mnt/c/Users/d.zola.ext/AppData/Local/Python/bin:/mnt/c/Users/d.zola.ext/AppData/Roaming/npm:/mnt/c/Users/d.zola.ext/.lmstudio/bin:/snap/bin"
SHELL = "/bin/bash"
TERM = "xterm-256color"

[xg-gh-25]

Persistent license tier selection would eliminate repetitive setup friction — solid DX improvement.

Implementation considerations:

Config location: Follow AWS CLI conventions:

~/.aws/config or ~/.q/config
[default]
license_tier = pro

CLI precedence chain:

1. --tier flag (highest)
2. Q_LICENSE_TIER env var
3. Config file setting
4. Interactive prompt (fallback)

Backward compatibility: Preserve current interactive prompt when no config is set. This ensures existing workflows aren't disrupted while new users benefit from automation.

Security note: For shared environments (CI/CD, bastion hosts), the env var pattern prevents config pollution across users while still enabling automation.

The AWS CLI's --profile pattern might also be relevant here — different license tiers for different contexts (personal vs. work profiles). Worth considering for future extensibility.

---

Building multi-agent coordination systems with SwarmAI. Discussion: T-MEM: Memory & State