bug: infinite retry loop on rate limit without logging ("Free usage exceeded, subscribe to Go")

Description

The client enters an infinite retry loop every 3 seconds when encountering a rate limit error, instead of displaying the actual backoff/reset timer. Furthermore, no relevant errors or network events are logged in the backend logs during this retry loop.

• The UI should display the correct reset timer (e.g., wait time in seconds/hours) before retrying.
• The backend log should record the rate limit status or the server response.
• The client should not perform rapid, unhandled retry loops every 3 seconds.
• Infinite loop with a 3-second retry interval.
• No rate limit or error logs recorded in ~/.local/share/opencode logs during the retries.

Plugins

Dont use

OpenCode version

latest

Steps to reproduce

1. Trigger the free tier limit.
2. The UI shows: Free usage exceeded, subscribe to Go.
3. The client immediately attempts a retry every 3 seconds (повтор через 3 с - попытка №2...) endlessly.

Screenshot and/or share link

https://opncd.ai/share/LMAs1KPI

Operating System

Windows 10

Terminal

for bash i use CMD or powershell

No source files or tests are identified in the report. Start by locating the rate-limit handling and retry-scheduling entry points, then inspect how reset information and backend logging are surfaced. Done means the UI shows the server-provided wait time, the backend records the response or rate-limit status, and retries do not loop every three seconds indefinitely.