I have just upgraded to Pro to get Codex. It looks like I can only connect my GitHub repos though.
I want to connect e.g. my Azure DevOps repos as well. Is this not possibe?
32 Likes
Azure DevOps not supported; GitHub only for now!
5 Likes
Is there a plan to support Azure DevOps as well?
9 Likes
Please support Bitbucket too
17 Likes
I’m excited about the potential of OpenAI Codex to streamline and enhance our coding workflows. However, I must express my disappointment at the current limitation of supporting only public GitHub repositories. Many enterprises, including ours, host proprietary codebases on Atlassian Bitbucket, and the inability to integrate these repositories directly with Codex limits its usefulness significantly for enterprise scenarios.
Given that Atlassian Bitbucket is widely used by enterprise teams, adding native support for Bitbucket would dramatically expand Codex’s usability and adoption in corporate environments.
I hope the OpenAI team considers prioritizing native Bitbucket integration soon. This enhancement would unlock tremendous value and enable enterprises to fully leverage Codex’s powerful capabilities.
Thanks for considering this request!
13 Likes
Our production repositories are in Atlassian Bitbucket as well. We would be more motivated to purchase a subscription if Codex could interact with our in-place repositories.
10 Likes
Support for GitLab would be great too.
11 Likes
It would be nice if it supports any git providers, for instance I use an internal version of GitHub enterprise so I cannot use codex
5 Likes
As a feedback +1 here for AzureDevops or at least “generic git” integration
10 Likes
Azure DevOps plz
My Unity 2D game repo put on there
3 Likes
+1 for Azure Devops.
We love what we’ve seen in testing, but cannot go live without ADO native support.
6 Likes
Would it be possible to add support to GitHub Enterprise please?
Guys, I saw a downloadable MCP to use in your Copilot (VS or VSCode → ChatGPT Agent) for DevOps
Ok, you don’t by Codex but in Agent mode in VS, it’s like codex… it can do everything too there (compile, build, fix, PR, …) !!!
1 Like
I’m not seeing a technical reason this must be GitHub-only. If Codex already runs code in a container, it can interact with any Git remote over HTTPS/SSH using standard Git commands (clone, pull, commit, push). Authentication can be handed into the container securely (e.g., SSH keys, PATs, OAuth device flow) via a short-lived tunnel or secret mount from the chat session. That would enable GitLab, Bitbucket, Azure DevOps, and self-hosted Git servers.
If certain features depend on GitHub APIs (PR creation, checks, reviews), say so—but the core VCS path should be provider-agnostic. A simple “SCM driver” abstraction would let you ship basic Git support now and light up provider-specific features progressively, covering far more of the developer community than the current GitHub-only approach.
3 Likes
How about local code reviews? I diff my current branch to remote develop and generate a code review artefact