Troubleshoot Plugins

To enable debug logging for the JFrog plugin:

1. In your terminal, run:

export JFROG_DEBUG_LOGS=true

Logs are written to <project-root>/.opencode/event-log.txt.

If you see a "bundled skills not found" error (a toast in the TUI and/or an ERROR line in the log), the installed package is incomplete or corrupted. Reinstall @jfrog/opencode-jfrog-plugin and restart OpenCode.

If the JFrog MCP shows 401 or an SSE error in opencode mcp list (or the TUI), the /mcp endpoint rejected the token. Make sure JFROG_ACCESS_TOKEN is a JWT access token (jf atc), not a 64-character reference token, and that it was issued for the same platform as JFROG_URL (check with jf c show).

MCP connection status is surfaced by OpenCode itself. This plugin only registers the server. With JFROG_DEBUG_LOGS=true, a non-JWT token also produces a WARNING line in the event log.

Symptoms

• claude plugin install jfrog@claude-plugins-official fails
• Error mentions SSH/port 22 or GitHub connection issues
• Installation hangs or times out when attempting to reach GitHub

Root Cause

Your network blocks SSH (port 22) to GitHub. Claude Code currently has a open issue in which it tries HTTP and not HTTPs. The plugin normally uses SSH by default, but can fall back to HTTPS (port 443) using the solutions below.

Solution 1: Use HTTPS (Recommended)

Requirements: Claude Code v2.1.144 or later. Check your version with claude --version

Set an environment variable before installing:

export CLAUDE_CODE_PLUGIN_PREFER_HTTPS=1
claude plugin install jfrog@claude-plugins-official

This forces the plugin download over HTTPS/443 instead of SSH/22.

Solution 2: Configure Git

If environment variables aren't practical in your setup:

git config --global url."https://github.com/".insteadOf [email protected]:
claude plugin install jfrog@claude-plugins-official

This globally configures Git to use HTTPS for all GitHub URLs instead of SSH.