Troubleshoot Plugins Registry

Your agent must be configured to connect through Agent Guard.

To verify connectivity:

1. Ask your agent: "Can you confirm you have access to JFrog?"
2. Your agent should confirm the JFrog service endpoint URL and your project name.

Suggested solution: If the agent cannot verify connectivity:

• Check that Agent Guard is configured.
• Verify your JFrog credentials are valid and not expired.
• Confirm you have project membership and repository access.
• Restart your IDE.
• Contact your platform administrator if credentials or permissions are the issue.

The ai-catalog-plugins skill resolves the project the same way as other AI Catalog skills: JFROG_PROJECT, a single entitled project, or a project picker.

To resolve the project context:

1. Ask your agent: "What project are you configured for?"
2. If no project is detected, set JFROG_PROJECT or select the project when prompted.
3. Restart the IDE after changing environment variables in the shell that launches it.

Suggested solution: If the issue persists, contact your platform administrator to confirm project membership.

On first publish, the AI Catalog auto-provisions an Agent Plugins repository named <project-name>-plugins-local. Anyone can trigger provisioning; upload still requires write permission.

To fix:

1. Ask your agent to publish again.
2. Watch for errors such as missing write permission or failed auto-provisioning.
3. Contact your platform administrator to confirm write access, verify the repository exists, or create an Agent Plugins repository manually.

For more information, see Agent Plugins Repositories.

Match the agent or CLI error to one of the following suggested solutions.

If plugin.json is missing or invalid:

• Confirm a harness folder exists (.claude-plugin/, .cursor-plugin/, or .codex-plugin/) with plugin.json inside it.
• Required fields include name, version, and description.
• Ask your agent: "Can you check my plugin structure for errors?"

If the plugin has no components:

• plugin.json alone is not enough. Include at least one skill, MCP server, hook, or agent.

If permission is denied:

• You don't have write access to the Agent Plugins repository.
• Contact your administrator.
• Confirm CLI credentials with jf config show.

If connection failed:

• Check network and firewall access to your JFrog Platform.
• Verify Agent Guard is configured.
• Confirm the Artifactory URL in jf config show is correct.

For the full layout, see Plugin Structure and Layout.

To retry publish with the CLI:

jf agent plugins publish ./my-plugin --repo <REPOSITORY_NAME>

Artifactory indexes plugins by the storage path <name>/<version>/<name>-<version>.zip, not only by the values inside plugin.json.

Suggested solution:

• Confirm the folder and publish version match the intended name and semantic version.
• To release a change, increment the version and publish again.
• For path-driven indexing details, see Considerations for Publishing Plugins.

When you ask your agent to discover plugins, the ai-catalog-plugins skill queries Allowed plugins for your active project.

To find published plugins:

1. Confirm you're in the correct project context.
2. Ask your agent: "What plugins are available in our project?"
3. If none appear but you know they exist:

   • Wait 15 to 30 seconds and ask again.

   • Check AI/ML > Registry > Plugins in the JFrog Platform.

   • Confirm the plugin was published to this project, not another.

Suggested solution: Ask your agent what project it is using, then republish or switch project context if needed.

Claude Code list and install use the JFrog marketplace. If it isn't registered, the ai-catalog-plugins skill prompts you to set up plugins before native install and auto-updates work.

To fix:

1. Ask your agent: "Set up plugins."
2. Confirm ~/.netrc has an entry for your JFrog host with a non-email Artifactory username and identity token.
3. Restrict file permissions: chmod 600 ~/.netrc.
4. Reload plugins in Claude Code, then browse Discover plugins again.

For the Artifactory-native marketplace path, see Connect Claude Code to Artifactory.

Claude Code authenticates marketplace downloads through ~/.netrc. Artifactory usernames must not be email addresses (no @ character).

Suggested solution:

• Use an Artifactory username without @, not your email login.
• Confirm the machine, login, and password (identity token) values in ~/.netrc.
• Re-run set up plugins, or follow Connect Claude Code to Artifactory.

Claude Code fetches the marketplace URL synchronously and applies a short client timeout (about 10 seconds). If the marketplace response is slow or authentication fails, Discover can look empty.

Suggested solution:

• Confirm marketplace registration and .netrc credentials.
• Ask your agent to list plugins for the project to verify they exist in the Plugins Registry.
• Retry Discover after /reload-plugins.
• Contact your administrator if the marketplace endpoint is slow or unreachable.

The Install JFrog plugin panel carries the coding assistant you selected on First-time setup into the Add plugin tab so you do not choose the IDE twice.

Suggested solution:

• Confirm the correct IDE is selected on First-time setup, then open Add plugin.
• If the selection is still wrong, close the panel, click Install again, and reselect the IDE on First-time setup.
• For the full UI path, see Install a Plugin from the JFrog Platform.

The info banner on First-time setup appears for Claude Code only. Other IDEs do not show that banner.

Suggested solution:

• Select Claude Code as the coding assistant in the Install JFrog plugin panel.
• Expand Authentication details if you need credentials or environment steps (that section is collapsed by default).
• For Claude Code marketplace setup outside the panel, see Connect Claude Code to Artifactory.

Marketplace entries may use a namespaced name such as <repository-short-name>-<plugin-name> (for example, aidemo-plugins-local-security-scanner). The name in plugin.json is not always the install identifier.

To fix:

1. Ask your agent: "What plugins are available?" and copy the exact name returned.

2. In Claude Code, install with the marketplace name shown in Discover.

3. With the CLI, use the exact plugin name from list or the Registry:

   Shell

   jf agent plugins list
   jf agent plugins install <PLUGIN_NAME> --harness cursor

Cursor and Codex install through the command path, not Claude Code's native marketplace.

Suggested solution:

• Ask your agent to install the plugin, or run:

  Shell

  jf agent plugins install <PLUGIN_NAME> --harness cursor

  Use --harness codex for Codex.

• Confirm JFrog CLI v2.106.0 or later is configured.

• For flags and install directories, see Install Agent Plugins.

Using both Claude Code native marketplace install and jf agent plugins install against the same repository can overwrite Claude's plugin cache path and disable previously installed plugins.

Suggested solution:

• Use one install method per repository for Claude plugins.
• Re-register the marketplace and reinstall the plugin through that single method.
• For more information, see Agent Plugins Limitations in Artifactory.