Repository navigation
enhancement(core): add config resolve and doctor commands #17164
Description
Problem
OpenCode config can be composed from multiple sources, but there is no first-class CLI flow that shows the fully resolved runtime config or explains why a value won, was ignored, or is still unresolved. Downstream integrations end up building custom sync and debugging layers around config merge behavior.
Impact
This makes enterprise and generated-config setups harder to operate, especially when users mix global, project, inline, and generated config. It also turns troubleshooting into trial-and-error because there is no single source of truth for the effective config.
Fix
Add opencode config resolve and opencode config doctor.
resolveshould print the effective merged config in a machine-readable form.doctorshould report source precedence, unknown keys, deprecated keys, unresolved{env:...}and{file:...}refs, and ignored sections.- Both commands should work with custom config paths and eventually support selected profiles once profiles land.
File
docs/config/ L1
Activity
github-actions commentedon Mar 12, 2026
This issue doesn't fully meet our contributing guidelines.
What needs to be fixed:
[FEATURE]:prefix in the title (e.g.[FEATURE]: add config resolve and doctor commands)## Filefield with placeholder contentdocs/config/ L1). AI-generated walls of text are not acceptable per our guidelines — please rewrite this in your own words describing what you actually needPlease 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:
If you believe this was flagged incorrectly, please let a maintainer know.
github-actions commentedon Mar 12, 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.