Error: 429: {"type":"FreeUsageLimitError","message":"Error from provider (Console): Rate limit exceeded. Please try again later."} #42029

Activity

1. MathieuT1508 commented on Aug 12, 2026

   

   MathieuT1508

   on Aug 12, 2026

   More actions

   I have the same problem , it's affect the sub agent for me
2. github-actions

   assigned

   MrMushrooooom

   on Aug 12, 2026
3. github-actions commented on Aug 12, 2026

   

   github-actionsBot

   on Aug 12, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue doesn't fully meet our contributing guidelines.

   What needs to be fixed:

   • Steps to reproduce is empty — please describe what you were doing when the error occurred (e.g., which model/provider you were using, what action triggered it)
   • OpenCode version is missing
   • Operating System and Terminal are missing
   • The description only contains the raw error message with no additional context

   Please edit this issue to address the above within 2 hours, or it will be automatically closed.

   ---

   This issue might be a duplicate of existing issues. Please check:

   • [URGENT] Zen paid balance still hits FreeUsageLimitError / daily free usage limit. #33318: Zen paid balance still hits FreeUsageLimitError / daily free usage limit
   • Free Tier Limit Hit ? #32971: Free Tier Limit Hit — FreeUsageLimitError despite having balance
   • [BUG] Zen balance does not remove free usage cap; paid users still hit 200-request/free usage limit #33495: Zen balance does not remove free usage cap; paid users still hit the free usage limit

   If you believe this was flagged incorrectly, please let a maintainer know.

   👎React with 👎2Reacted by 死神 and sourello666-glitch
4. github-actions

   added

   needs:complianceThis means the issue will auto-close after 2 hours.This means the issue will auto-close after 2 hours.

   on Aug 12, 2026
5. Dave147789 commented on Aug 12, 2026

   

   Dave147789

   on Aug 12, 2026

   More actions

   I have the same problem
6. github-actions commented on Aug 12, 2026

   

   github-actionsBot

   on Aug 12, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window.

   Feel free to open a new issue that follows our issue templates.

   👎React with 👎1Reacted by 死神
7. github-actions

   removed

   needs:complianceThis means the issue will auto-close after 2 hours.This means the issue will auto-close after 2 hours.

   on Aug 12, 2026
8. github-actions

   closed this as not plannedon Aug 12, 2026
9. 12errh commented on Aug 13, 2026

   

   12errh

   on Aug 13, 2026

   Last edited by 12errh

   More actions

   @MrMushrooooom @Dave147789 @palmamartin @MathieuT1508

   Root Cause

   The issue is triggered by the User-Agent header, not the API key or IP address. The upstream "Console" inference provider (which serves the -free models) gates anonymous free capacity strictly based on this header:

   • TUI request (User-Agent: opencode/<version>) → 200 OK
   • Custom request (User-Agent: curl/8.0 or any non-opencode UA) → 429 FreeUsageLimitError

   Testing confirmed that x-opencode-client, x-opencode-version, and session headers alone do not unlock the capacity. Only the User-Agent value matters.

   According to the source code (packages/opencode/src/session/llm/request.ts), the TUI always sends User-Agent: opencode/<version>. The gateway strips all x-opencode-* headers before forwarding upstream but passes the User-Agent through untouched, allowing the upstream provider to use it for free-pool validation.

   ---

   Fix

   Set the opencode User-Agent directly on your request:

   curl -s https://opencode.ai \
     -H "Authorization: Bearer <key-or-public>" \
     -H "Content-Type: application/json" \
     -H "User-Agent: opencode/1.18.16" \
     -d '{"model":"deepseek-v4-flash-free","messages":[{"role":"user","content":"hi"}],"max_tokens":5}'

   Verified: Including the opencode/ UA returns an HTTP 200 (including streaming). Excluding it results in a 429 error, regardless of IP or key.

   ---

   Notes

   • This restriction only affects -free models. Paid and balance-backed models are not gated by the User-Agent.
   • This is an anti-abuse gate designed to reserve free capacity for the official client. Because of this, it may change at any time. For long-term stability, it is better to Bring Your Own Key (BYOK) with a non-free model.
   • If you are writing a custom client, inject User-Agent: opencode/<version> into the request. Please also forward the user's real IP so per-IP quotas remain fair.
   • The solution i make is this simple proxy https://github.com/12errh/zen-proxy it just change the agent header line so it can work.

   👍React with 👍2Reacted by Rakib and Parsa - Im_Troller
10. augusto-romero-arango

    added a commit that references this issue on Sep 7, 2026

    Distinguir el limite de uso y la caida del proveedor como familias pr…

    ...

    3c3d040