feat(vscode): exponential backoff retry with cancel button for rate limiting by catrielmuller · Pull Request #8435 · Kilo-Org/kilocode

catrielmuller · 2026-04-06T19:31:36Z

Context

Resolve Implement exponential backoff when the extension is being rate limited #8333
Resolve "Too Many Requests: Free model usage limit reached. Please try again later or upgrade to a paid model." not clearing on model change #8203

Implement exponential backoff retry with a cancel button for rate limiting (HTTP 429) and server errors in the VSCode extension. When the extension encounters rate limiting, it now automatically retries with increasing delays, and users can manually cancel the retry loop at any time.

This also addresses issue #8203 by clearing error messages when the user changes to a different model.

Implementation

Retry utility (packages/kilo-vscode/src/util/retry.ts): New module with backoff calculation functions
- retryable(): Checks if HTTP status should be retried (429, 5xx, etc.)
- backoff(): Calculates delay (5s -> 10s -> 30s -> 60s -> 300s)
- headerDelay(): Extracts Retry-After headers
KiloProvider (packages/kilo-vscode/src/KiloProvider.ts):
- Added withRetry() wrapper for SDK calls
- Sends sessionStatus messages with retry countdown
- Auto-stops after 5 failed attempts
WorkingIndicator (packages/kilo-vscode/webview-ui/src/components/shared/WorkingIndicator.tsx):
- Added Cancel button during retry status
- Button styled with error color for visibility
Session context (packages/kilo-vscode/webview-ui/src/context/session.tsx):
- selectModel() now clears error messages when model changes
i18n: Added translations for 18 languages

Screenshots

b540-d9914a046e41" />

How to Test

Trigger a rate limit (429) error by making many requests
Observe the retry countdown in the WorkingIndicator (5s -> 10s -> 30s -> 60s -> 300s)
Click "Cancel" to stop the retry loop
Send a message with a free model that hits the usage limit
Switch to a paid model
Verify the error message is cleared from the conversation

kilo-code-bot · 2026-04-06T19:39:18Z

+      const status = result.response?.status ?? 0
+
+      // Check for non-retryable status codes — fail immediately without retry
+      if (!retryable(status) && attempt > 1) {


WARNING: Non-retryable errors still retry once

The immediate-fail guard is gated on attempt > 1, so a 400/401/403 response on the first call falls through to the backoff path and gets retried anyway. That adds an unnecessary second request for errors the user must fix locally.

kilo-code-bot · 2026-04-06T19:39:41Z

Code Review Summary

Status: 1 Issue Found | Recommendation: Address before merge

Overview

Severity	Count
CRITICAL	0
WARNING	1
SUGGESTION	0

Fix these issues in Kilo Cloud

Issue Details (click to expand)

WARNING

File	Line	Issue
`packages/kilo-vscode/src/KiloProvider.ts`	2188	Cancelling during the retry backoff only clears the timeout, so the pending promise never settles and the send remains stuck indefinitely.

Other Observations (not in diff)

Previously reported issues in packages/kilo-vscode/src/KiloProvider.ts (non-retryable errors retrying once, the off-by-one retry cap, and cancellation surfacing as sendMessageFailed) appear resolved in this revision.

Previously reported model-switch crash in packages/kilo-vscode/webview-ui/src/context/session.tsx also appears resolved in this revision.

Files Reviewed (2 files)

packages/kilo-vscode/src/KiloProvider.ts - 1 issue
packages/kilo-vscode/webview-ui/src/context/session.tsx - 0 issues

_{Reviewed by gpt-5.4-20260305 · 325,004 tokens}

kilo-code-bot · 2026-04-06T20:56:58Z

+          const timer = setTimeout(resolve, delay)
+          abortController.signal.addEventListener("abort", () => {
+            clearTimeout(timer)
+            reject(new Error("Retry cancelled"))


WARNING: Cancelling a retry is surfaced as a send failure

This Error("Retry cancelled") bubbles into handleSendMessage() / handleSendCommand(), which then emits sendMessageFailed. The result is that clicking Cancel shows a failure toast and restores the prompt back into the composer even though the request was already accepted by the server; cancellation should follow the abort path instead of the generic send-failed path.

kilo-code-bot · 2026-04-06T20:56:58Z

    applyModel(selectedAgentName(), { providerID, modelID })
+    const sid = currentSessionID()
+    if (sid) {
+      setStore("messages", sid, (msgs) => msgs.filter((m) => !m.error))


WARNING: Switching models can throw before messages finish loading

selectSession() sets currentSessionID before loadMessages populates store.messages[sid], so if the user changes models during that loading window msgs is still undefined here and .filter(...) crashes the webview.

Suggested change

setStore("messages", sid, (msgs) => msgs.filter((m) => !m.error))

setStore("messages", sid, (msgs = []) => msgs.filter((m) => !m.error))

…te limiting Implement retry with exponential backoff when the extension encounters rate limiting (HTTP 429) or server errors. Retries on: 5s -> 10s -> 30s -> 60s -> 300s, with a maximum of 5 attempts. - Add retry utility module (retry.ts) with backoff calculation - Add withRetry() wrapper for SDK calls in KiloProvider - Add Cancel button to WorkingIndicator during retry status - Clear error messages when model changes (issue #8203) - Add i18n translations for cancel button (18 languages) Users can manually cancel via the cancel button or the retry loop automatically stops after 5 failed attempts. Issues: #8333, #8203

kilo-code-bot · 2026-04-06T22:06:55Z

+        })
+
+        // Wait for delay or until aborted
+        await new Promise((resolve) => {


WARNING: Cancelling during backoff leaves the retry stuck

If abort fires while this sleep is pending, the handler only clears the timeout; it never resolves or rejects the surrounding promise. withRetry() then never reaches the next loop iteration or the finally block, so the cancelled send hangs indefinitely and the abort-controller entry is never cleaned up for that session.

imho it sounds like it makes sense

chrarnoldus · 2026-04-07T16:35:27Z

Isn't this already implemented here? https://github.com/Kilo-Org/kilocode/blob/main/packages/opencode/src/session/retry.ts

Yes, it's similar but works at different levels.

and we need it at multiple levels?

The new file handle the errors between the VSCode Backend HTTP Client and the CLI Backend Server . The opencode/src/session/retry.ts handle the errors from the AI SDK Providers.

feat(vscode): exponential backoff retry with cancel button for rate limiting

kilo-code-bot Bot reviewed Apr 6, 2026

View reviewed changes

catrielmuller force-pushed the catrielmuller/fix-8333 branch from 65fb86d to 7d2fbad Compare April 6, 2026 20:50

kilo-code-bot Bot reviewed Apr 6, 2026

View reviewed changes

catrielmuller force-pushed the catrielmuller/fix-8333 branch from 7d2fbad to 613606b Compare April 6, 2026 22:04

kilo-code-bot Bot reviewed Apr 6, 2026

View reviewed changes

lambertjosh mentioned this pull request Apr 7, 2026

Implement exponential backoff when the extension is being rate limited #8333

Closed

chrarnoldus reviewed Apr 7, 2026

View reviewed changes

kirillk approved these changes Apr 7, 2026

View reviewed changes

catrielmuller merged commit 2bca86c into main Apr 7, 2026
14 checks passed

catrielmuller deleted the catrielmuller/fix-8333 branch April 7, 2026 20:10

kilo-code-bot Bot mentioned this pull request Apr 9, 2026

Memory accumulation in VS Code extension webview risks renderer OOM (grey screen) #8607

Closed

This was referenced Apr 29, 2026

fix(vscode): preserve revert after model error switch #9670

Merged

feat(vscode): implement exponential backoff for 429 model fetch retries #8339

Closed

jliounis pushed a commit to jliounis/kilocode that referenced this pull request May 18, 2026

Merge pull request Kilo-Org#8435 from Kilo-Org/catrielmuller/fix-8333

b052001

feat(vscode): exponential backoff retry with cancel button for rate limiting

marius-kilocode mentioned this pull request Jun 12, 2026

Add Button to Continue / Stop for Provider returned error #8541

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat(vscode): exponential backoff retry with cancel button for rate limiting#8435

feat(vscode): exponential backoff retry with cancel button for rate limiting#8435
catrielmuller merged 1 commit into
mainfrom
catrielmuller/fix-8333

catrielmuller commented Apr 6, 2026 •

edited

Loading

Uh oh!

kilo-code-bot Bot Apr 6, 2026

Uh oh!

Uh oh!

Uh oh!

kilo-code-bot Bot commented Apr 6, 2026 •

edited

Loading

WARNING

Uh oh!

kilo-code-bot Bot Apr 6, 2026

Uh oh!

kilo-code-bot Bot Apr 6, 2026

Uh oh!

kilo-code-bot Bot Apr 6, 2026

Uh oh!

kirillk Apr 7, 2026

Uh oh!

chrarnoldus Apr 7, 2026

Uh oh!

catrielmuller Apr 7, 2026

Uh oh!

chrarnoldus Apr 7, 2026

Uh oh!

catrielmuller Apr 7, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

	setStore("messages", sid, (msgs) => msgs.filter((m) => !m.error))
	setStore("messages", sid, (msgs = []) => msgs.filter((m) => !m.error))

Conversation

catrielmuller commented Apr 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Context

Implementation

Screenshots

How to Test

Uh oh!

kilo-code-bot Bot Apr 6, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

kilo-code-bot Bot commented Apr 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Code Review Summary

Overview

WARNING

Uh oh!

kilo-code-bot Bot Apr 6, 2026

Choose a reason for hiding this comment

Uh oh!

kilo-code-bot Bot Apr 6, 2026

Choose a reason for hiding this comment

Uh oh!

kilo-code-bot Bot Apr 6, 2026

Choose a reason for hiding this comment

Uh oh!

kirillk Apr 7, 2026

Choose a reason for hiding this comment

Uh oh!

chrarnoldus Apr 7, 2026

Choose a reason for hiding this comment

Uh oh!

catrielmuller Apr 7, 2026

Choose a reason for hiding this comment

Uh oh!

chrarnoldus Apr 7, 2026

Choose a reason for hiding this comment

Uh oh!

catrielmuller Apr 7, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

catrielmuller commented Apr 6, 2026 •

edited

Loading

kilo-code-bot Bot commented Apr 6, 2026 •

edited

Loading