›_ Codex Issues
Codex Issues / #15030

Offer GitHub Copilot Enterprise sign-in for Codex agent

Open 💬 2 comments Opened Mar 18, 2026 by SentientMatt

What version of the IDE extension are you using?

26.5313.41514

What subscription do you have?

GitHub Copilot Enterprise

Which IDE are you using?

VS Code

What platform is your computer?

Windows 11

What issue are you seeing?

I am unable to use the Codex agent in VS Code with my GitHub Copilot Enterprise subscription because the extension does not provide any GitHub Copilot authentication option.

When I attempt to sign in, the only available options are:

  • Sign in with ChatGPT
  • Use an API key

There is no option to authenticate through GitHub Copilot Enterprise, so I cannot use the Codex agent via the subscription I already have.

What steps can reproduce the bug?

  1. Install the Codex VS Code extension.
  2. Open the extension and attempt to authenticate.
  3. Observe the available sign-in options.
  4. Try to use the extension with an existing GitHub Copilot Enterprise subscription.

What is the expected behavior?

One of the following should happen clearly:

  • the extension should allow sign-in with GitHub Copilot Enterprise if that subscription is supported for Codex in VS Code, or
  • the extension should clearly indicate that GitHub Copilot Enterprise is not supported for this flow.

Additional information

Actual behavior:

  • Only ChatGPT and API key authentication are offered.
  • No GitHub Copilot sign-in path is available.
  • This blocks use of Codex in VS Code through an existing Copilot Enterprise subscription.

Environment:

  • VS Code version: 1.111.0
  • OS: Windows 11
  • Also reproduced in WSL

Related context:
I also opened the corresponding integration-facing issue in the VS Code Copilot repository because it is not obvious whether this gap is owned by the Codex extension, the Copilot integration, or product support boundaries.

View original on GitHub ↗

2 Comments

HernandoR · 5 months ago

it feels like a bug, since i can find the feature discribed in https://docs.github.com/en/copilot/concepts/agents/openai-codex meaning that it was shipped out.

johnib · 2 months ago

@HernandoR fwiw native Copilot sign-in inside Codex isn't a thing today (Copilot's hosted by GitHub/MS so the harness doesn't offer it - see openai/codex#8361 where the Codex team explains it). but you can bridge it with a small local proxy, which is exactly your case: it lets Codex run on the Copilot Enterprise seat you already pay for, no ChatGPT login or separate API key.

I maintain a fork that exposes a full Responses API backed by your Copilot sub:

npx copilot-api-node20@latest start --codex

then point Codex at it in ~/.codex/config.toml:

model_provider = "copilot"

[model_providers.copilot]
name = "copilot"
base_url = "http://localhost:4141/v1"
wire_api = "responses"

the wire_api = "responses" bit is the key part - that's what makes Codex use the Responses API. in my testing it works out of the box with whatever codex models your seat is entitled to.

to be upfront it's my own fork, not official - been running it ~9 months for a few folks on my team, you're welcome to give it a try: https://www.npmjs.com/package/copilot-api-node20

p.s. one nuance - the extension's sign-in UI won't take a custom base_url, so this is the CLI/config route, not a button in the extension. :)