Can I use Claude Fable 5 in Kiro right now?

Mostly yes. Fable 5 was restored worldwide on July 1, 2026, and AWS Bedrock — which Kiro uses for Claude models — is being re-enabled as fast as possible. If claude-fable-5 does not yet appear in your Kiro model picker, your Bedrock region has not finished re-enablement; Opus 4.8 is the working fallback in the meantime.

How do I select Fable 5 as the model in Kiro?

Open Kiro settings, go to the model/agent configuration, and pick the Anthropic Bedrock model. Fable 5 shows as claude-fable-5 once your Bedrock account and region have it re-enabled post-restoration. If you do not see it, check Bedrock model access in the AWS console — it is not a Kiro bug.

Is Kiro free, and does it cost extra to run Fable 5?

Kiro itself has a free tier. Running Claude models routes through Amazon Bedrock, so you pay Bedrock token rates on top — and Fable 5 is the most expensive Claude at $10 / $50 per million tokens. Start on Opus 4.8 for everyday work and reserve Fable 5 for the hardest tasks.

What should I use in Kiro if Fable 5 is not yet re-enabled in my region?

Use Claude Opus 5 where your Bedrock region already offers it — same $5/$25 as Opus 4.8 and ahead of it on published benchmarks — or Claude Opus 4.8, which is long-established on Bedrock. Both share the Anthropic API and authorization, so either is a near drop-in. For free or local routing, GLM 5.2 works through compatible endpoints. Keep one portable system prompt so you can switch the moment your Bedrock region finishes re-enablement.

Back to blog

How to Use Claude Fable 5 in Kiro (AWS Agentic IDE)

Kiro is AWS’s agentic IDE, and people keep asking how to run Claude Fable 5 inside it. Fable 5 is restored as of July 1, 2026 — Bedrock re-enablement status, and the exact setup steps.

Jun 27, 2026

Fable5 Editorial

If you use Kiro, AWS\u2019s spec-driven agentic IDE, you have probably tried to pick Claude Fable 5 from the model list \u2014 and hit either a missing entry or an error. Here is exactly what is happening and how to set it up correctly.

Update — July 1, 2026: Fable 5 is back worldwide — the US export-control directive was withdrawn June 30, and the model was restored July 1 on the Claude API, Claude.ai, Claude Code, and Cowork. AWS Bedrock (which Kiro uses) is being re-enabled "as fast as possible" — if claude-fable-5 is missing from your Kiro picker, your Bedrock region likely hasn't finished re-enablement yet. Through July 7, Pro/Max/Team plans include Fable 5 in up to 50% of the weekly usage cap; after that it moves to usage credits. Live status: /is-fable-5-back · Full story: Claude Fable 5 is back.

Kiro Fable 5: the short answer

Kiro can run Claude Fable 5, but only through Amazon Bedrock — and Bedrock is still finishing post-restoration re-enablement. Kiro does not host models itself \u2014 it calls them through Bedrock. During the June 12 – July 1 suspension, Bedrock invocation was gated behind US-entity identity verification plus an Anthropic-approved use case (a late-June window mechanism). That gating ended with the July 1 restoration; the remaining bottleneck is Bedrock's region-by-region re-enablement. Until your region clears, Opus 4.8 is the working fallback.

How Kiro gets its Claude models

Kiro is built by AWS and wires its agent loop to Amazon Bedrock for Anthropic models. That means three things matter:

Layer	What it controls
Kiro app	The agent UI, spec workflow, and which model ID you select
Amazon Bedrock	The actual model hosting, region, and access approval
Post-restoration rollout	Whether `claude-fable-5` is re-enabled in your Bedrock region yet

If any layer below the app is not satisfied, the model picker either hides Fable 5 or the call fails. This is why "Fable 5 not showing in Kiro" is almost never a Kiro bug \u2014 it is the Bedrock layer, described in our AWS Bedrock access guide.

Step-by-step: selecting Fable 5 in Kiro

Confirm Bedrock access first. In the AWS console, open Bedrock \u2192 Model access and check that claude-fable-5 shows as access-granted (not just listed). If it is missing, your region's post-restoration re-enablement hasn't landed — see the Bedrock access guide before touching Kiro.
Match the region. Fable 5 access is region-scoped on Bedrock. Set Kiro\u2019s AWS profile/region to the region where your access was approved.
Open Kiro settings \u2192 model configuration. Choose the Anthropic Bedrock provider and select claude-fable-5. If it is absent, your account is not approved yet.
Set reasoning effort. Fable 5 has no temperature/top_p knobs \u2014 tune the effort level instead. Most coding work runs fine below max.
Drop in a spec. Kiro is spec-driven: put the full task specification in the first message rather than drip-feeding it. Fable 5 follows literal, complete specs best \u2014 build one on our prompt generator.

If your region isn't re-enabled yet: what to run in Kiro

During the June 12 – July 1 suspension this section was the workaround list; it still applies while Bedrock finishes its region-by-region rollout:

Claude Opus 5 \u2014 since July 24, 2026 this is the closest drop-in, same Anthropic authorization, same half price ($5 / $25 per M) as Opus 4.8 and ahead of it on published benchmarks. Select claude-opus-5 in Kiro if your Bedrock region already lists it; Bedrock rollout for a model this new is region-by-region, so check Bedrock model access first.
Claude Opus 4.8 \u2014 the same $5 / $25 and long-established on Bedrock, so it is the safer pick while Opus 5 propagates. Select claude-opus-4-8 in Kiro. (Note: even with Fable 5 live, the new safety classifiers occasionally fall back to Opus 4.8 on routine requests.)
GLM 5.2 \u2014 free, open-weights, routable through compatible endpoints if you want a no-cost path. See GLM 5.2 vs Fable 5.
Keep one portable prompt \u2014 a clear role, context, task, and output format port across all of them, so the switch to Fable 5 costs you nothing.

Track the real-time status on our Is Fable 5 back? page before assuming Kiro is broken.

Common Kiro + Fable 5 errors

"Model not available" / Fable 5 missing from picker \u2192 Bedrock re-enablement hasn't reached your region, or wrong region configured. Fix in the AWS console, not Kiro.
Call returns an authorization/region error \u2192 your Bedrock region isn't re-enabled yet; use Opus 4.8 until it lands.
Costs higher than expected \u2192 Fable 5 is $10 / $50 per M, double Opus. Run the cost math and escalate to Fable 5 only when quality demands it.

Bottom line

Fable 5 is restored as of July 1, 2026, and Kiro is ready the moment your Bedrock region is \u2014 the remaining bottleneck is AWS's re-enablement rollout, not the IDE. Check Bedrock model access, run Opus 4.8 in the meantime, and keep a portable prompt so the switch costs you nothing.

Independent guide. Check live availability on our status page and compare every fallback on the alternatives guide.