Repository navigation
Plugin updates: No way to get latest version after initial install #10546
Description
Problem
Once a plugin is installed, there's no way to update it to a newer version without manually clearing the cache.
Current behavior
- User adds
oc-sync(oroc-sync@latest) to their config - OpenCode installs latest version (e.g., 0.1.4), caches resolved version in
~/.cache/opencode/package.json - Plugin author publishes 0.1.5 with bug fixes
- User restarts OpenCode - still uses cached 0.1.4
- User has no way to know an update is available or how to get it
Root cause
In packages/opencode/src/bun/index.ts:
if (dependencies[pkg] === version && modExists) return modOnce installed, the cached version is used forever.
Suggested solutions
Option A: Add opencode update command
opencode update plugins # Update all plugins to latest
opencode update oc-sync # Update specific pluginOption B: Periodic version check
- On startup, check npm registry for newer versions
- Show notification: "Plugin updates available: oc-sync (0.1.4 → 0.1.5)"
Option C: TTL-based cache invalidation
- Re-check
@latestversions after X days (e.g., 7 days)
Workaround
Currently users must manually:
rm -rf ~/.cache/opencode/node_modules/oc-sync
# or
rm ~/.cache/opencode/package.jsonThis is not discoverable and plugin authors have no way to notify users of updates.
Metadata
Metadata
Assignees
Labels
No labels
Activity
github-actions commentedon Jan 25, 2026
This issue might be a duplicate of existing issues. Please check:
opencode upgradedoesn't update plugin dependencies in ~/.config/opencode/package.json #10441:opencode upgradedoesn't update plugin dependencies in ~/.config/opencode/package.json - Related to plugin update mechanismsFeel free to ignore if none of these address your specific case.
Tarquinen commentedon Jan 25, 2026
"plugin": ["opencode-plugin-here@latest"]authors can also notify users of updates with toasts by comparing npm version to cache version if needed
athal7 commentedon Feb 5, 2026
This also affects explicitly versioned plugins. If I have
myplugin@0.20.1cached and update my config tomyplugin@0.20.2, OpenCode still uses the cached 0.20.1 until I manuallyrm -rf ~/.cache/opencode/node_modules/myplugin.Expected: OpenCode should compare the requested version against the cached version and reinstall if they differ.
phazei commentedon Apr 8, 2026
I'm on opencode 1.3.17
I don't see how this was fixed.
I had:
"plugin": ["opencode-plugin-here"]and it didn't update. Then I changed it to:
"plugin": ["opencode-plugin-here@latest"]and restarted, but still no update.
agxs commentedon Sep 7, 2026
Same issue with 1.18.27