Repository navigation
docs: clarify plugin loading and config behavior - #21416
timrichardson wants to merge 1 commit into
Conversation
|
Thanks for updating your PR! It now meets our contributing guidelines. 👍 |
|
The language about what happens when both opencode.jsonc and opencode.json (or tui.jsonc and tui.jsonc) are present is a little unclear. You probably ought explicitly point out that these two configs are merged. Mentioning simply that "the jsonc file wins" might suggest that the jsonc file was not respected at all, which is not the case. |
52aadb5 to
18edb97
Compare
|
Automated PR Cleanup Thank you for contributing to opencode. Due to the high volume of PRs from users and AI agents, we periodically close older PRs using automated criteria so maintainers can focus review time on the most active and community-supported contributions. This PR was closed because it matched the following cleanup criteria:
PRs created within the last month are not affected by this cleanup. If you believe this PR was closed incorrectly, or if you are still actively working on it, please leave a comment explaining why it should be reopened. A maintainer can review and reopen it if appropriate. Thanks again for taking the time to contribute. |
Issue for this PR
Closes #21409
Type of change
What does this PR do?
Updates
/docs/pluginsso it matches the current plugin behavior.The main fixes are:
opencode.jsonc/tui.jsoncand.jsonvs.jsoncprecedencefile://plugin paths and directory requirementsfile://plugins are loaded directly and picked up on restartHow did you verify your code works?
This is a docs-only change. I verified the updated claims against the current code paths for plugin loading, config precedence, and plugin target resolution, and re-read the final
plugins.mdxcontent for consistency.Screenshots / recordings
Not applicable. Docs-only change.
Checklist