Repository navigation
Config hot-reload: apply opencode.json and plugin changes without restart #49569
Closed as not planned
Description
Problem
OpenCode loads opencode.json and initializes plugins exactly once at startup. Every config or plugin change (adding a plugin, pinning a version, tweaking permissions) requires a full quit + restart to take effect.
Why it matters
- Plugin authors iterating on a hook currently pay a full restart per change.
- Heavy plugin setups (12+ plugins) make each restart slower; users batch changes to avoid restarting, which delays feedback.
- A stale/shadowing second config file (e.g.
opencode.jsoncnext toopencode.json) is only discovered at the next restart.
Proposal
- Watch config files (
opencode.json/opencode.jsonc, project + global) and offer hot-reload (or a/reloadcommand) that re-merges config and re-initializes plugins in the running session. - If full hot-reload is unsafe (provider/auth changes), reload at least the safe subset (permissions, tool output limits, compaction) and clearly report which changes still need a restart.
Context
Running opencode 1.18.31 with a 12-plugin setup; cold start is fine (~4s), but the restart-per-tweak loop slows plugin development.
Metadata
Metadata
Assignees
Labels
No labels
Activity
github-actions commentedon Sep 17, 2026
This issue doesn't fully meet our contributing guidelines.
What needs to be fixed:
[FEATURE]:Please 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:
/reloadslash command with auto-resumeIf you believe this was flagged incorrectly, please let a maintainer know.
github-actions commentedon Sep 17, 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.