Skip to content

Update opencode config filename - #635

Open
x-n2o wants to merge 2 commits into
warpdotdev:mainfrom
x-n2o:patch-1
Open

Update opencode config filename#635
x-n2o wants to merge 2 commits into
warpdotdev:mainfrom
x-n2o:patch-1

Conversation

@x-n2o

@x-n2o x-n2o commented Aug 26, 2026

Copy link
Copy Markdown

Summary

Updated the OpenCode configuration filename reference in the documentation from opencode.json to opencode.jsonc to match support for JSON with comments.

Related issues

Closes #636

Validation

Verified that the documentation file src/content/docs/agents/cli-agents/opencode.mdx correctly reflects the opencode.jsonc filename used by the plugin configuration.

Screenshots

None

Follow-ups

None

@cla-bot

cla-bot Bot commented Aug 26, 2026

Copy link
Copy Markdown

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have the users @x-n2o on file. In order for us to review and merge your code, each contributor must visit https://cla.warp.dev to read and agree to our CLA. Once you have done so, please comment @cla-bot check to trigger another check.

@vercel

vercel Bot commented Aug 26, 2026

Copy link
Copy Markdown

@x-n2o is attempting to deploy a commit to the warpdotdev Team on Vercel.

A member of the Team first needs to authorize it.

@warp-for-oss

warp-for-oss Bot commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

@x-n2o

Every PR must be linked to a same-repo issue before Oz can review it.

Next step: open or find a same-repo issue describing this change, then link it to this PR by adding Closes #123 to the PR description (or using the "Development" sidebar on GitHub). A maintainer will mark the issue ready-to-implement when it is ready. Once it is marked, comment /warp-agent-review to re-trigger review.

See the contribution guidelines for the full readiness model.

Powered by Oz

@warp-for-oss warp-for-oss Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@x-n2o

Every PR must be linked to a same-repo issue before Oz can review it.

Next step: open or find a same-repo issue describing this change, then link it to this PR by adding Closes #123 to the PR description (or using the "Development" sidebar on GitHub). A maintainer will mark the issue ready-to-implement when it is ready. Once it is marked, comment /warp-agent-review to re-trigger review.

See the contribution guidelines for the full readiness model.

Powered by Oz

@x-n2o

x-n2o commented Aug 26, 2026

Copy link
Copy Markdown
Author

@cla-bot check

@cla-bot cla-bot Bot added the cla-signed label Aug 26, 2026
@cla-bot

cla-bot Bot commented Aug 26, 2026

Copy link
Copy Markdown

The cla-bot has been summoned, and re-checked this pull request!

@rachaelrenk

Copy link
Copy Markdown
Contributor

opencode.json and opencode.jsonc are both valid per OpenCode's own docs, so there's no factual error to fix here. Furthermore, the code sample right below the changed line is plain JSON with no comments ({"plugin": ["@warp-dot-dev/opencode-warp"]}), so .json is actually the more accurate filename to pair with that snippet. Switching to .jsonc without adding a comment to the example is inconsistent. I'd recommend closing unless there's a concrete argument for the change -- @hongyi-chen thoughts from an internal perspective?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Docs: correct OpenCode configuration filename to opencode.jsonc

2 participants