openclaw - 💡(How to fix) Fix [Feature]: Include retry/reset time in rate limit error messages [1 participants]

When the upstream model provider (e.g. Anthropic subscription) returns a rate limit error, the user-facing message is: OpenClaw already tracks cooldownUntil and retryAfterMs internally for auth profile failover. It would be helpful to surface this in the error message shown to the user, e.g.: Include retry/reset time in rate limit error messages

TL;DR

Update the rate limit error message to include the retry/reset time, such as "Try again in ~X minutes", where X is the value of retryAfterMs or cooldownUntil.

Guidance

• Review the current implementation of rate limit error handling to identify where the error message is constructed and returned to the user.
• Modify the error message construction to include the retryAfterMs or cooldownUntil value, which is already tracked internally.
• Consider formatting the retry time in a user-friendly way, such as converting milliseconds to minutes or seconds.
• Test the updated error message to ensure it is correctly displayed to the user when a rate limit error occurs.

Example

error_message = f":warning: API rate limit reached. Try again in ~{retryAfterMs /