Latest Claude model (Opus 4.8) not visible in Org Kiro Pro model selector

[sairaghava143]

Before opening, please confirm:

• I have searched for duplicate or closed issues

Operating System

win32

Kiro Version

0.12.263

Bug Description

I am using an organization Kiro Pro account, but the latest Claude model is not visible in the model selector.

Current behavior:

• In Org Kiro Pro, the latest available model shown is Claude Opus 4.6.
• Claude Opus 4.8 is not available in the model dropdown.
• I have restarted the Kiro IDE, but the model list still does not show Opus 4.8.

Expected behavior:

• Claude Opus 4.8 should be visible in the model selector for eligible Pro/Org users, or there should be clear information if it is not enabled for this organization yet.

Additional context:

• In normal/personal Kiro, Claude Opus 4.8 is available.
• The issue seems specific to the organization Kiro Pro account.
• Please confirm whether Opus 4.8 experimental/latest model rollout needs to be enabled for the org account, IAM Identity Center users, or subscription settings.

Steps to Reproduce

1. Open Kiro IDE and sign in using the organization Kiro Pro account.
2. Open any project/workspace.
3. Open the chat/model selector in Kiro.
4. Check the list of available Claude models.
5. Observe that the latest available model shown is Claude Opus 4.6.
6. Compare with normal/personal Kiro account, where Claude Opus 4.8 is available.

Expected Behavior

Claude Opus 4.8 should be visible in the model selector for eligible organization Kiro Pro users.

If Opus 4.8 is not yet available for organization/IAM Identity Center users, Kiro should clearly indicate that the model rollout is not enabled for this org account or requires admin/subscription enablement.

Conversation ID

8db9953f-6b50-4ebe-977c-2486a96612de
ee9533bc-a028-4e0b-b888-3d8d8cd66ebe
ee9533bc-a028-4e0b-b888-3d8d8cd66ebe
ee9533bc-a028-4e0b-b888-3d8d8cd66ebe
ee9533bc-a028-4e0b-b888-3d8d8cd66ebe

Additional Context

No response

[github-actions]

🤖 Potential Duplicate Detected

This issue appears to be similar to:

• #9008: Power plan user see some models, not all (85% similar)
• #8990: Paid user cannot access Opus 4.7 or Opus 4.8 in Kiro (85% similar)
• #8490: Invalid model ID. Please select a different model to continue. (85% similar)
• #7940: Claude models (Opus 4.6 / Sonnet 4.6) not appearing in model selector for IAM Identity Center user (85% similar)

What happens next?

• ⏰ This issue will be automatically closed in 3 days
• 🏷️ If this is not a duplicate, you can prevent automatic closure by adding a comment or reacting with 👎 to this message.
• 💬 Comment on the original issue if you have additional information

Why is this marked as duplicate?
Both issues report problems with model availability/visibility in the model selector - new issue reports Claude Opus 4.8 not visible in Org Pro account, while #9008 reports Power plan users not seeing all models

[sairaghava143]

Thanks for checking this.

I believe this is not an exact duplicate of #9008. That issue is about a Power plan user not seeing all models, while this issue is specifically about an organization Kiro Pro account / IAM Identity Center setup where Claude Opus 4.8 is not visible, even though the same model is visible in a normal/personal Kiro account.

The main clarification I’m looking for is whether Opus 4.8/latest experimental models need to be enabled separately for:

• Org Kiro Pro subscriptions
• IAM Identity Center users
• Organization/admin subscription settings

So this seems more related to org/IAM entitlement or rollout behavior rather than a general model selector issue. Could you please keep this issue open or confirm the exact expected behavior for Org Kiro Pro users?

[github-actions]

Thank you for your feedback! 🙏

The duplicate label has been removed and this issue has been sent back for maintainer review.

A maintainer will review this issue shortly.

[AnilMaktala]

Hi @sairaghava143,

For organization Kiro Pro accounts, model availability is controlled by your organization's admin. Opus 4.8 needs to be explicitly enabled in your org's Kiro admin settings (AWS Console → Kiro → Model governance).

Please ask your org admin to enable Opus 4.8 in the model governance settings. If it's already enabled and still not showing, let us know.