Repository navigation
[FEATURE]: Add a manual opencode plugin update command #18544
Description
Feature hasn't been suggested before.
- I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
Feature hasn't been suggested before.
- I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
I'd like to add a manual opencode plugin update command to refresh npm plugins declared in config.
Why this helps:
- users currently need to rely on startup behavior or manual cache cleanup to pick up plugin updates
- a dedicated command gives users an explicit and discoverable way to refresh plugin installs on demand
- this can land independently from broader plugin auto-update work
Proposed scope:
- add
opencode plugin update - update npm plugins declared in config
- skip pinned versions, local file plugins, and unsupported specifiers
- document the command behavior clearly
This is related to #6159, but scoped to the manual update command only.
Metadata
Metadata
Assignees
Labels
No labels
Activity
github-actions commentedon Jul 4, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.
niStee commentedon Aug 13, 2026
Reopened for reassessment: the linked contributor PR was closed by automated stale-PR cleanup rather than merged. The issue should be re-triaged against current
dev; a refreshed PR should follow the current contribution template and include current verification.niStee commentedon Aug 13, 2026
Correction: GitHub rejected my reopen request because this account lacks repository permission to reopen issues. The issue remains closed. The recommendation is a fresh issue or maintainer-assisted reopen only if the behavior is still reproducible on current
dev; the old PR should not be reopened unchanged.