You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
fix(console): follow-up to #13108 — /docs/en still 404 and English locale does not persist #13606
I originally reported this issue in #13108, and a fix was merged, but the problem is still reproducible in production.
So I am opening this issue to track the remaining behavior that was not resolved.
This issue is not limited to Korean.
If oc_locale is set to any non-English locale (for example: ko, ja, fr, etc.), selecting English from the language selector may not stay in English.
Also, /docs/en still returns 404 in production.
Expected behavior
/docs/en should resolve to English docs consistently (or redirect to canonical English docs path, e.g. /docs).
Selecting English should persist English and should not revert to a previous non-English locale.
/docs/en/* paths should also resolve consistently for English docs.
Actual behavior
/docs/en returns 404 in production.
English selection can be overridden by existing non-English locale state (oc_locale).
In practice, English does not remain sticky in some docs navigation flows.
Reproduction (production)
Set oc_locale to a non-English locale (e.g. ko).
Open https://opencode.ai/docs.
Try either:
Directly navigate to https://opencode.ai/docs/en, or
Select English from the language selector in docs.
Observe current behavior.
Observed result
/docs/en returns 404.
English selection may fall back to the previous non-English locale.
Notes
Likely related to docs path canonicalization for /docs/en* and locale cookie synchronization in docs proxy routing.
Plugins
No response
OpenCode version
No response
Steps to reproduce
No response
Screenshot and/or share link
No response
Operating System
No response
Terminal
No response
Reacted by Maxime Brunet, ShanSanear, Alex Vorndran, dfk1352, bartek1470, Petter Søland, Sebastian and Beomsoo Kim
Activity
Seungjun0906 commentedon Feb 15, 2026
@jayair #13608
this is the follow up PR for this issue
jsancs commentedon Feb 18, 2026
Hey @Seungjun0906 thanks for the work! Do you know when can you merge this?
Seungjun0906 commentedon Feb 18, 2026
@jsancs
Hey! not sure since i am not maintainer of this repo :(
@jayair could you check this PR!