New registered Kiro pro users can only see partial models available

This is likely related to the CLI version or authentication method, not the admin model availability setting.

Here are the most common causes and steps to resolve:

1. CLI version — most common cause New users may have an older CLI version that doesn't include the latest model catalog. Have them update to the latest version: curl -fsSL https://cli.kiro.dev/install | bash Then restart the CLI. Per the Kiro CLI Models documentation: "If for some reason a model from the list above does not show up in the dropdown, restart your client and that should resolve the issue."

2. Authentication method Some models are only available with specific authentication methods. For example, certain frontier models (like Claude Opus 4.7) are currently available only to users signing in via AWS IAM Identity Center (IDC), while open weight models (GLM-5, DeepSeek, MiniMax, Qwen) are available with all authentication methods.

If your old users authenticated via IDC but new users are using a different method (e.g., Builder ID, GitHub, or Google), the new users will see a reduced model list. Ensure new users are authenticating through the same IAM Identity Center start URL.

You can verify the Auth column in the model availability table here: Kiro CLI Models

3. Geographic restrictions Model availability can vary by country or region based on each model provider's geographic requirements. If new users are in a different location, some models may be restricted for them. For more information, see each model provider's supported countries and regions, if relevant: Anthropic, Qwen, DeepSeek, Kimi, MiniMax, GLM.

4. About the admin "Model availability" toggle Disabling the admin model control means there is no organizational allow-list filtering. However, users still need to meet the platform-level requirements (correct CLI version, supported auth method, supported region) to see all models. The toggle only removes the admin governance layer and it doesn't override platform eligibility.

Recommended steps:

1. Have new users run kiro-cli --version and compare with existing users
2. Confirm all users are authenticating via the same method (IAM Identity Center)
3. Have new users log out and log back in, then restart the CLI
4. Verify new users are in a supported region for the models in question

References:

Kiro CLI — Models

Enterprise Model Governance

Authentication Methods

Hello.

Does the problem persist even after signing in again using Kiro CLI?
I tried it in my environment, but I couldn't reproduce the problem.

It's the same issue here https://github.com/kirodotdev/Kiro/issues/7813