Repository navigation
v2 Docs vs v1 Docs: v2's are outdated, miss information and nav is way worse #50624
Description
From opencode.ai's homepage > Docs, it now opens the v2 Docs. https://opencode.ai/v2/docs
These are way behind on v1 Docs though.
Information is completely missing, is outdated, and navigation makes things way harder to find compared to the v1 docs.
The v1 docs are still maintained as well, but you have to manually enter its url to get there. https://opencode.ai/docs/
Take for example the Go information.
In v1 docs, in the menu you immediately see Usage > Go. Easy to find. Once there, you see Muse amongst the models. And Where can i use it, including Validated Clients. Last maintained Sept 21. https://opencode.ai/docs/go/
In v2 docs, in the menu there's no mention of Go nor is there a category like Usage. No, you first have to somehow know or guess that you need to open Providers.https://opencode.ai/v2/docs/providers/
There you see Go mentioned. Then you have to click Go Documentation from there. To finally land in the Go docs which are categorized under Console? https://opencode.ai/v2/docs/console/go
But Muse models aren't in the models table. There are less headers and there is less information. There is no Where can i use it, no Validated Clients.
Are the v2 Docs simply the v1 Docs from May or June or so? Badly kept up-to-date? And now somehow supposed to be used as the most current Docs? While the actual v1 Docs are still maintained and way more up-to-date and way easier to navigate? How has this even been decided?
Activity
github-actions commentedon Sep 22, 2026
This issue doesn't fully meet our contributing guidelines.
What needs to be fixed:
_No response_): OpenCode version, Steps to reproduce, Operating System, and Terminal. These are required fields for bug reports.[FEATURE]:title prefix and the verification checkbox) or the Question template instead.Please edit this issue to address the above within 2 hours, or it will be automatically closed.
If you believe this was flagged incorrectly, please let a maintainer know.
github-actions commentedon Sep 22, 2026
Thank you for the detailed feedback about the documentation — it's clear and well-written. However, this issue still doesn't use one of our required issue templates.
What still needs to be fixed:
This issue needs to use one of the three required templates:
[FEATURE]:and must include the verification checkbox and a description of the problem/needYour issue reads as a feature request or feedback about improving the v2 documentation. If so, please:
[FEATURE]:Please update the issue to use the appropriate template. The
needs:compliancelabel will remain until this is resolved.github-actions commentedon Sep 22, 2026
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.