Plugin marketplace does not support Azure DevOps git URLs (requires .git suffix)
Description
Claude Code's plugin marketplace system cannot connect to Azure DevOps git repositories because it requires all git URLs to end with .git, but Azure DevOps URLs do not use this suffix.
Azure DevOps URL format
Azure DevOps repos use this URL format:
https://dev.azure.com/{org}/{project}/_git/{repo}
There is no .git suffix. Appending .git causes Azure DevOps to look for a repo literally named {repo}.git, which doesn't exist.
What we tried
All of these fail:
/plugin marketplace add https://dev.azure.com/{org}/{project}/_git/{repo}
- Error:
Invalid marketplace schema from URL: : Invalid input: expected object, received string - Claude Code treats it as a URL to a JSON file instead of a git repo
/plugin marketplace add https://dev.azure.com/{org}/{project}/_git/{repo}.git
- Error:
TF401019: The Git repository with name or identifier {repo}.git does not exist - Azure DevOps doesn't recognize the
.gitsuffix
/plugin marketplace add https://{org}@dev.azure.com/{org}/{project}/_git/{repo}.git
- Same error as #2
extraKnownMarketplacesin settings.json with"source": "git":
- Without
.git: settings validation error:url: Invalid string: must end with ".git" - With
.git: passes validation but fails to clone (same Azure DevOps error as #2)
Environment
- Claude Code version: latest as of March 2026
- OS: Windows 11
- Git credentials: working (
git ls-remotesucceeds from terminal for the same repo URL) - Azure DevOps hosted repositories
Expected behavior
Claude Code should support Azure DevOps git URLs for marketplace sources, either by:
- Not requiring the
.gitsuffix for git URL detection - Adding an Azure DevOps-aware URL handler
- Allowing the
"source": "git"type in settings to accept URLs without.git
Impact
Organizations using Azure DevOps for source control cannot use the plugin marketplace system to distribute shared skills and plugins to their development teams. This blocks adoption of the plugin ecosystem for any team on Azure DevOps.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗