[FEATURE] Support Azure DevOps repositories in Claude Code on the web (Cloud Sessions)

Open 💬 5 comments Opened Apr 27, 2026 by halajarin

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

Claude Code on the web (Cloud Sessions) currently requires GitHub for repository cloning and pushing branches back. Per the docs:

Platform restrictions: repository cloning and pull request creation require GitHub. [...] GitLab, Bitbucket, and other non-GitHub repositories can be sent to cloud sessions as a local bundle, but the session can't push results back to the remote.

This blocks the core async use case for anyone whose code lives on Azure DevOps: kick off a task from the mobile app or browser, let it run in a Cloud Session, come back later to a PR ready for review — without having to keep a workstation running.

The CCR_FORCE_BUNDLE=1 claude --remote fallback uploads a bundle but cannot push back, so I have to manually pull diffs and apply them locally to ADO. That negates the async benefit — I still need my machine on to rebase and push.

Azure DevOps is a major enterprise platform (Microsoft-stack, .NET, regulated industries) and is currently the only major source-control platform without a tracked feature request for Cloud Sessions support.

Proposed Solution

Allow Cloud Sessions to clone from and push to Azure DevOps repositories, the same way they do today for GitHub.

Concretely:

  • Connect an Azure DevOps organization at claude.ai/code (PAT to start, Entra ID OAuth ideally — Microsoft is already building the remote ADO MCP Server on this pattern)
  • Select an ADO repository when starting a Cloud Session
  • At task completion, Claude pushes a branch and (optionally) opens a PR on Azure Repos

Everything else (Routines, Code Review, Slack integration, Pipelines tasks) can come later as separate requests. This issue is scoped to the Cloud Sessions clone/push capability only.

Alternative Solutions

  • CCR_FORCE_BUNDLE=1 claude --remote — uploads a bundle but cannot push back, so I still need my workstation to rebase manually
  • Local Claude Code with the official Microsoft @azure-devops/mcp server — works fine, but requires my machine to stay on (the entire point of Cloud Sessions is to avoid this)
  • Mirroring code from ADO to GitHub — not viable for regulated environments where exporting proprietary code raises compliance concerns

Priority

High - Significant impact on productivity

Feature Category

Other

Use Case Example

I'm a developer at a mid-size enterprise running on Azure DevOps. I want to kick off a refactor task from my phone in the evening, let it run overnight in a Cloud Session, and review the resulting PR on Azure Repos in the morning — without keeping a workstation running.

Today this is impossible: Cloud Sessions can't push back to ADO, so I either keep my laptop on with a custom orchestrator script, or accept manually rebasing the bundle output every morning.

Additional Context

Related GitLab and Bitbucket requests that this issue mirrors:

  • #12346 — GitLab integration
  • #38179 — Bitbucket integration

The recent --from-pr extension added GitLab, Bitbucket, and GitHub Enterprise — Azure DevOps was the only major platform left out.

View original on GitHub ↗

This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗