[GH-ISSUE #53] Kiro 总是status: 400 #48

Closed
opened 2026-02-27 07:17:39 +03:00 by kerem · 5 comments
Owner

Originally created by @gogoyan on GitHub (Sep 18, 2025).
Original GitHub issue: https://github.com/justlovemaki/AIClient-2-API/issues/53

如题,请问是kiro的限制吗?

使用ccr用的时候提示这个

Originally created by @gogoyan on GitHub (Sep 18, 2025). Original GitHub issue: https://github.com/justlovemaki/AIClient-2-API/issues/53 如题,请问是kiro的限制吗? 使用ccr用的时候提示这个
kerem closed this issue 2026-02-27 07:17:39 +03:00
Author
Owner

@justlovemaki commented on GitHub (Sep 18, 2025):

是的,现在kiro开始收费了,免费额度很低。你可以多搞几个号,用账号池。

<!-- gh-comment-id:3308433846 --> @justlovemaki commented on GitHub (Sep 18, 2025): 是的,现在kiro开始收费了,免费额度很低。你可以多搞几个号,用账号池。
Author
Owner

@cosmaz commented on GitHub (Oct 31, 2025):

FYI: restarting Claude with --permission-mode bypassPermissions --continue using these keys often resolves the 400 errors for me. However, I still occasionally hit a 429. Sharing in case this helps with debugging.

<!-- gh-comment-id:3472132672 --> @cosmaz commented on GitHub (Oct 31, 2025): FYI: restarting Claude with --permission-mode bypassPermissions --continue using these keys often resolves the 400 errors for me. However, I still occasionally hit a 429. Sharing in case this helps with debugging.
Author
Owner

@justlovemaki commented on GitHub (Oct 31, 2025):

FYI: restarting Claude with --permission-mode bypassPermissions --continue using these keys often resolves the 400 errors for me. However, I still occasionally hit a 429. Sharing in case this helps with debugging.

After debugging, a 400 error is generally due to a context outage; claude codes can be handled with /compact. A 429 error is a server-side interface limitation, which is indeed unavoidable.

<!-- gh-comment-id:3472323821 --> @justlovemaki commented on GitHub (Oct 31, 2025): > FYI: restarting Claude with --permission-mode bypassPermissions --continue using these keys often resolves the 400 errors for me. However, I still occasionally hit a 429. Sharing in case this helps with debugging. After debugging, a 400 error is generally due to a context outage; claude codes can be handled with /compact. A 429 error is a server-side interface limitation, which is indeed unavoidable.
Author
Owner

@cosmaz commented on GitHub (Oct 31, 2025):

That lines up with what I’m seeing too — but it’s odd that a full Claude restart (--permission-mode bypassPermissions --continue) often clears it. I’ve also had 400s appear almost immediately with a minimal context (well under limits), so it doesn’t always look like a pure overflow case. Just adding this datapoint in case it’s useful.

<!-- gh-comment-id:3472421320 --> @cosmaz commented on GitHub (Oct 31, 2025): That lines up with what I’m seeing too — but it’s odd that a full Claude restart (--permission-mode bypassPermissions --continue) often clears it. I’ve also had 400s appear almost immediately with a minimal context (well under limits), so it doesn’t always look like a pure overflow case. Just adding this datapoint in case it’s useful.
Author
Owner

@justlovemaki commented on GitHub (Oct 31, 2025):

That lines up with what I’m seeing too — but it’s odd that a full Claude restart (--permission-mode bypassPermissions --continue) often clears it. I’ve also had 400s appear almost immediately with a minimal context (well under limits), so it doesn’t always look like a pure overflow case. Just adding this datapoint in case it’s useful.

I haven't encountered a situation where a 400 error occurs immediately with very little context, but thank you for your feedback.

<!-- gh-comment-id:3473317764 --> @justlovemaki commented on GitHub (Oct 31, 2025): > That lines up with what I’m seeing too — but it’s odd that a full Claude restart (--permission-mode bypassPermissions --continue) often clears it. I’ve also had 400s appear almost immediately with a minimal context (well under limits), so it doesn’t always look like a pure overflow case. Just adding this datapoint in case it’s useful. I haven't encountered a situation where a 400 error occurs immediately with very little context, but thank you for your feedback.
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/AIClient-2-API-justlovemaki#48
No description provided.