Plugin loader doesn't support GitHub URL installation #8646

Open
opened 2026-02-16 18:10:29 -05:00 by yindo · 1 comment
Owner

Originally created by @kj55-dev on GitHub (Feb 5, 2026).

Originally assigned to: @thdxr on GitHub.

Problem

The plugin loader appends @version to all package names, which breaks GitHub URL syntax.

When configuring a plugin like:

"plugin": ["github:user/repo#dev"]

The loader parses it as pkg=github:user/repo#dev, version=latest, then runs:

bun add github:user/repo#dev@latest  # Invalid syntax

Expected Behavior

GitHub URLs should work directly:

"plugin": ["github:code-yeongyu/oh-my-opencode#dev"]

This is standard bun behavior - bun add github:user/repo#branch works natively.

Use Case

Developers want to use development branches of plugins without:

  • Publishing to npm
  • Using file:// with local clones
  • Waiting for releases

Proposed Solution

Detect github:, git+, git:// prefixes and skip the @version suffix.

Originally created by @kj55-dev on GitHub (Feb 5, 2026). Originally assigned to: @thdxr on GitHub. ## Problem The plugin loader appends `@version` to all package names, which breaks GitHub URL syntax. When configuring a plugin like: ```json "plugin": ["github:user/repo#dev"] ``` The loader parses it as `pkg=github:user/repo#dev`, `version=latest`, then runs: ```bash bun add github:user/repo#dev@latest # Invalid syntax ``` ## Expected Behavior GitHub URLs should work directly: ```json "plugin": ["github:code-yeongyu/oh-my-opencode#dev"] ``` This is standard bun behavior - `bun add github:user/repo#branch` works natively. ## Use Case Developers want to use development branches of plugins without: - Publishing to npm - Using `file://` with local clones - Waiting for releases ## Proposed Solution Detect `github:`, `git+`, `git://` prefixes and skip the `@version` suffix.
Author
Owner

@github-actions[bot] commented on GitHub (Feb 5, 2026):

This issue might be a duplicate of existing issues. Please check:

  • #8763: Plugin loader incorrectly appends @latest to GitHub references (describes the exact same bug)
  • #12143: Plugin without version defaults to 'latest' causing semver parsing error (related root cause)
  • #8264: [FEATURE]: Allow plugins to be installed from github directly (the feature request this would address)

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Feb 5, 2026): This issue might be a duplicate of existing issues. Please check: - #8763: Plugin loader incorrectly appends @latest to GitHub references (describes the exact same bug) - #12143: Plugin without version defaults to 'latest' causing semver parsing error (related root cause) - #8264: [FEATURE]: Allow plugins to be installed from github directly (the feature request this would address) Feel free to ignore if none of these address your specific case.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#8646