Repository navigation
SOS #20376
anuarzhitchaev-lab
started this conversation in
General
SOS
#20376
Replies: 1 comment
|
Hey @anuarzhitchaev-lab! Kiro started rejecting older client versions, and OmniRoute still identifies itself to Kiro with an old one, so every Kiro request gets that 400. It's tracked in #19607, and the fix is PR #19626, not merged yet. A contributor posted a hotfix script for 3.8.53 in #19607. I haven't reviewed it, so read it before you run it. If your Kiro account signs in with Builder ID, read @glud123's latest notes in #19748 first, because the earlier revisions of that script didn't work for Builder ID. Follow #19607 for the release. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Title: Kiro provider returns 400 "This version of Kiro is no longer supported"
OmniRoute version: 3.8.53 (npm global, latest)
OS: Windows
Node.js: 24 LTS (replace with your actual version)
Provider: Kiro (kr/claude-sonnet-5)
Steps to reproduce:
Actual result:
[400]: This version of Kiro is no longer supported. Please update
to the latest version of Kiro to continue.
Expected: request succeeds.
Looks like the Kiro client version OmniRoute sends is outdated
and rejected upstream. Could it be bumped to the current Kiro version?
All reactions