BloopAI/vibe-kanban · error · Error
unsupported_provider
unsupported_provider
Error message
t('createWorkspaceFromPr.errors.unsupportedProvider') What it means
This error surfaces when workspacesApi.createFromPr returns { success: false, error: { type: 'unsupported_provider' } }. The backend does not support the git remote's forge provider for PR operations (only certain ProviderKinds are implemented). The dialog maps it to the localized createWorkspaceFromPr.errors.unsupportedProvider message.
Source
Thrown at packages/web-core/src/shared/dialogs/command-bar/CreateWorkspaceFromPrDialog.tsx:167
run_setup: runSetup,
remote_name: selectedRemote,
});
if (!result.success) {
switch (result.error?.type) {
case 'branch_fetch_failed':
throw new Error(result.error.message);
case 'auth_failed':
throw new Error(result.error.message);
case 'cli_not_installed':
throw new Error(
t('createWorkspaceFromPr.errors.cliNotInstalled', {
provider: result.error.provider,
})
);
case 'pr_not_found':
throw new Error(t('createWorkspaceFromPr.errors.prNotFound'));
case 'unsupported_provider':
throw new Error(
t('createWorkspaceFromPr.errors.unsupportedProvider')
);
default:
throw new Error(
result.message ||
t('createWorkspaceFromPr.errors.failedToCreateWorkspace')
);
}
}
return result.data;
},
onSuccess: (data) => {
queryClient.invalidateQueries({ queryKey: ['tasks'] });
queryClient.invalidateQueries({ queryKey: ['workspaces'] });
modal.hide();
appNavigation.goToWorkspace(data.workspace.id);
},
});View on GitHub (pinned to 4deb7eca8f)
Solutions
- Check the repo's remote URL points to a supported provider (GitHub/GitLab); update it with `git remote set-url` if wrong
- Use a repo hosted on a supported forge for PR-based workspace creation
- Upgrade the app/backend to a version that supports your provider, if support was added upstream
- Create the workspace directly from a branch instead of from a PR for unsupported providers
Example fix
// before git remote -v origin git@bitbucket.org:team/repo.git -> unsupported_provider // after git remote set-url origin git@github.com:team/repo.git
Defensive patterns
Strategy: validation
Validate before calling
const SUPPORTED = ['github.com', 'gitlab.com'];
function providerSupported(remoteUrl: string) {
return SUPPORTED.some((host) => /@|^https?:\/\//.test(remoteUrl) && remoteUrl.includes(host));
}
// before opening Create-from-PR, check the selected remote:
if (!providerSupported(remote.url)) show('This provider does not support PR-based workspace creation'); Type guard
function isUnsupportedProvider(e: CreateFromPrError | undefined): e is { type: 'unsupported_provider' } {
return e?.type === 'unsupported_provider';
} Try / catch
try {
await workspacesApi.createFromPr(input);
} catch (err) {
if (isUnsupportedProvider(err.cause ?? err)) {
show('Provider unsupported for PR import — create the workspace from a branch instead.');
switchToBranchFlow();
}
} Prevention
- Validate the remote host against supported providers before showing PR options
- Fall back to branch-based workspace creation for unsupported forges
- Keep ProviderKind support matrix documented for users
- Upgrade to newer versions that add providers you need
When it happens
Trigger: Create Workspace clicked on a repo whose remote host is not a supported provider (e.g. Bitbucket, self-hosted Gitea, generic git server); workspacesApi.createFromPr resolves success:false with error.type 'unsupported_provider'.
Common situations: Repo cloned from a provider other than GitHub/GitLab (Bitbucket, Azure DevOps, Gitea); SSH remote URL in a non-standard format the backend can't classify; enterprise/self-hosted forge not yet supported by this version.
Related errors
- Force push required. The remote branch has diverged.
- Failed to push changes
- result.message || 'Force push failed'
- result.message || 'Push failed'
- branch_fetch_failed
AI-assisted analysis of BloopAI/vibe-kanban@4deb7eca8f (2026-08-29).
Data as JSON: /api/errors/de882f17f09d4141.
Report an issue: GitHub.