You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
User feedback asks to set up SCM integrations (GitHub, GitLab, Bitbucket, Azure DevOps, etc.) with AI, i.e. from the CLI (feedback). The CLI has no integrations command; repo, code-mappings, and issue linking assume one is already installed.
Sentry already has an experimental API-driven install flow: POST /api/0/organizations/{org}/pipeline/integration_pipeline/ (action: initialize, then step through) — organization_pipeline.py.
Limitations / edge cases
Pipeline state lives in the Django session; bearer-token CLI requests have no session to persist it across steps.
OAuth steps return an oauthUrl; the callback is relayed to a browser window via postMessage, not to a CLI.
GitHub installs happen on github.com and come back with installation_id as initial data.
Endpoint is EXPERIMENTAL; POST needs org:write, org:admin, or org:integrations.
Pipeline is bound to the initiating user; providers behind feature flags return 404.
Providers without allow_multiple reject a second install.
Activity
linear-code commentedon Oct 16, 2026
MCP-1089
feat(cli): add integration list and delete commands (#1523)