Return user-facing message if API reuturn 429 API rate limit reached #2202#10415

Merged

steipete merged 3 commits intoopenclaw:mainfrom

vincenthsin:fix/2202-response-user-facing-message-for-API-429

Feb 14, 2026

Contributor

vincenthsin commented Feb 6, 2026 •

edited by greptile-apps bot

Loading

Fix #2202 with Google Antigravity. Manually local tests have done and passed.
This PR only fix the case of API 429 error. The 402 error should be fixed in a separate branch.

Greptile Overview

Greptile Summary

Adds explicit handling for rate-limit (HTTP 429) assistant errors, formatting them into a friendlier user-facing message.
Threads config and sessionKey through embedded runner/subscribe plumbing so error formatting can use sandbox/tool policy context.
Tracks the last assistant message during streaming and emits a lifecycle:error event on agent_end when the final assistant message ended in error.
Adds/extends unit tests covering 429 formatting and lifecycle error emission.

Confidence Score: 4/5

This PR is likely safe to merge after addressing the user-facing error copy inconsistencies for 429 handling.
Core changes are localized and covered by tests, but there are two confirmed places where 429 errors can be mislabeled or described inaccurately (credits vs throttling; sanitizeUserFacingText mapping 429 to overload), which would regress UX for some error paths.
src/agents/pi-embedded-helpers/errors.ts

_{(2/5) Greptile learns from your feedback when you react with thumbs up/down!}

openclaw-barnacle bot added the agents label

greptile-apps bot reviewed

View reviewed changes

Contributor

greptile-apps bot left a comment

_{1 file reviewed, 2 comments}

_{Edit Code Review Agent Settings | Greptile}

src/agents/pi-embedded-helpers/errors.ts Show resolved Hide resolved

Contributor

greptile-apps bot commented Feb 6, 2026

Additional Comments (1)

src/agents/pi-embedded-helpers/errors.ts
Wrong message for 429

In sanitizeUserFacingText, the ERROR_PREFIX_RE branch collapses both overloaded and rate-limit errors into the overloaded message ("temporarily overloaded"). This means a user-facing Error: 429 ... string will be mislabeled as overload even though formatAssistantErrorText now has a specific rate-limit message. If sanitizeUserFacingText is used on these errors (e.g., for non-assistant/raw error paths), 429s won’t show the intended rate-limit copy.

Prompt To Fix With AI

This is a comment left during a code review.
Path: src/agents/pi-embedded-helpers/errors.ts
Line: 425:428

Comment:
**Wrong message for 429**

In `sanitizeUserFacingText`, the `ERROR_PREFIX_RE` branch collapses *both* overloaded and rate-limit errors into the overloaded message (`"temporarily overloaded"`). This means a user-facing `Error: 429 ...` string will be mislabeled as overload even though `formatAssistantErrorText` now has a specific rate-limit message. If `sanitizeUserFacingText` is used on these errors (e.g., for non-assistant/raw error paths), 429s won’t show the intended rate-limit copy.

How can I resolve this? If you propose a fix, please make it concise.

vincenthsin force-pushed the fix/2202-response-user-facing-message-for-API-429 branch 2 times, most recently from a384f4c to f7f276e Compare

February 6, 2026 14:17

vincenthsin mentioned this pull request

[Bug]: Gateway sends empty messages on persistent API errors (429/402) instead of user-facing explanation #2202

Closed

Contributor Author

vincenthsin commented Feb 9, 2026

Hi @mkbehr , can you please review this ?

openclaw-barnacle bot added the size: S label

steipete self-assigned this

steipete added a commit that referenced this pull request


          fix(agents): improve 429 user messaging (#10415) (thanks @vincenthsin)

c6ce808

steipete force-pushed the fix/2202-response-user-facing-message-for-API-429 branch from 643c466 to c6ce808 Compare

February 14, 2026 16:31

vincenthsin and others added 3 commits

February 14, 2026 17:32


          Return user-facing message if API reuturn 429 API rate limit reached

ea41798


          clarify the error message

e041631


          fix(agents): improve 429 user messaging (openclaw#10415) (thanks @vin…

5a4a509

…centhsin)

steipete force-pushed the fix/2202-response-user-facing-message-for-API-429 branch from c6ce808 to 5a4a509 Compare

February 14, 2026 16:33

steipete merged commit 478af81 into openclaw:main

23 checks passed

steipete mentioned this pull request

refactor(agents): dedupe transient error copy #16324

Merged

github-actions bot mentioned this pull request

📡 Upstream Digest — 2026-02-14 18:23 UTC curtismercier/openclaw-mods#25

Open

mverrilli pushed a commit to mverrilli/openclaw that referenced this pull request


          Return user-facing message if API reuturn 429 API rate limit reached o…

606bf2a

…penclaw#2202 (openclaw#10415)

* Return user-facing message if API reuturn 429 API rate limit reached

* clarify the error message

* fix(agents): improve 429 user messaging (openclaw#10415) (thanks @vincenthsin)

---------

Co-authored-by: Peter Steinberger <steipete@gmail.com>

akoscz pushed a commit to akoscz/openclaw that referenced this pull request


          Return user-facing message if API reuturn 429 API rate limit reached o…

f4ccc33

…penclaw#2202 (openclaw#10415)

* Return user-facing message if API reuturn 429 API rate limit reached

* clarify the error message

* fix(agents): improve 429 user messaging (openclaw#10415) (thanks @vincenthsin)

---------

Co-authored-by: Peter Steinberger <steipete@gmail.com>

GwonHyeok pushed a commit to learners-superpumped/openclaw that referenced this pull request


          Return user-facing message if API reuturn 429 API rate limit reached o…

087b25a

…penclaw#2202 (openclaw#10415)

* Return user-facing message if API reuturn 429 API rate limit reached

* clarify the error message

* fix(agents): improve 429 user messaging (openclaw#10415) (thanks @vincenthsin)

---------

Co-authored-by: Peter Steinberger <steipete@gmail.com>

snowzlm pushed a commit to snowzlm/openclaw that referenced this pull request


          Return user-facing message if API reuturn 429 API rate limit reached o…

c53d81c

…penclaw#2202 (openclaw#10415)

* Return user-facing message if API reuturn 429 API rate limit reached

* clarify the error message

* fix(agents): improve 429 user messaging (openclaw#10415) (thanks @vincenthsin)

---------

Co-authored-by: Peter Steinberger <steipete@gmail.com>

vincenthsin deleted the fix/2202-response-user-facing-message-for-API-429 branch

February 21, 2026 16:00

zooqueen pushed a commit to hanzoai/bot that referenced this pull request


          Return user-facing message if API reuturn 429 API rate limit reached o…

0d58ecd

…penclaw#2202 (openclaw#10415)

* Return user-facing message if API reuturn 429 API rate limit reached

* clarify the error message

* fix(agents): improve 429 user messaging (openclaw#10415) (thanks @vincenthsin)

---------

Co-authored-by: Peter Steinberger <steipete@gmail.com>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels