OpenCode: rate limit exceeded / 429 from provider
OpenCode itself doesn't rate limit — it's BYO-provider, so the 429 comes from whichever backend you configured: Anthropic/OpenAI per-minute caps, OpenCode Go's usage windows ($12/5-hour and $30/week), or OpenRouter's allowances. First identify which provider threw it; the fix is provider-specific, and the structural fix is a backend without per-minute caps or usage windows.
OpenCode's agent loop makes many provider calls per prompt — plan steps, tool results, edits. Limits sized for a human typing get consumed several times faster, which is why the same key that works fine in a chat UI 429s inside OpenCode.
OpenCode takes any OpenAI-compatible provider: set the base URL to https://api.stdcmpt.com/v1 with model "standardcompute" and there's no per-minute cap and no 5-hour or weekly window — under sustained load requests are paced smoothly instead of returning 429s, at one flat monthly price. Guide: /integrations/opencode.
No. OpenCode is bring-your-own-provider; every rate limit or usage window belongs to the configured backend (Anthropic, OpenAI, OpenCode Go, OpenRouter…). The same key hits the same limits in any tool — agents just get there faster.
OpenCode Go meters usage in rolling windows — roughly $12 of model usage per 5 hours and $30 per week. Great value inside the windows; heavy all-day agent use exhausts them, and then you wait for the roll or route work to another provider.
Either size your provider tier well above your agent's burst rate, or use a backend with no per-minute economics. Flat-rate OpenAI-compatible endpoints pace sustained load instead of rejecting it, so the 429 class disappears.