codex-plugin-cc reports Codex as “not authenticated” when Codex CLI is already usable with Azure OpenAI

[powyncify]

First off: what a fantastic idea. This plugin will let us get much more done with Codex from inside Claude Code.

We ran into an authentication/setup issue in a Windows 11 + WSL environment.

Summary

Codex is already installed and usable in our WSL environment on Windows 11.

In our Codex setup, the model provider is:

Azure OpenAI

However, after installing this plugin and running setup, the plugin reports that Codex is installed but not authenticated, and suggests login methods that appear to require OpenAI authentication, not Azure OpenAI:

Codex is installed (v0.117.0) but not authenticated. To complete setup, run:

  !codex login

  If browser login is blocked, use !codex login --device-auth or !codex login --with-api-key instead.

The problem is that the suggested auth flows do not apply in our case, because Codex is configured to use Azure OpenAI rather than OpenAI-hosted authentication.

Expected behavior

One of these should happen:

1. If codex-plugin-cc supports Codex CLI when configured with Azure OpenAI, it should recognize the existing Codex setup as authenticated/usable and complete setup successfully.

2. If Azure OpenAI is not currently supported, the plugin should say that explicitly, e.g.:

   • “Azure OpenAI-backed Codex is not currently supported by this plugin”
   • rather than instructing the user to run OpenAI-specific login flows that cannot work in this configuration.

Actual behavior

The plugin says Codex is installed but not authenticated, even though Codex itself is already usable in WSL with Model provider: Azure OpenAI.

It then suggests:

• !codex login
• !codex login --device-auth
• !codex login --with-api-key

Those methods appear to assume OpenAI auth and are not usable with our Azure OpenAI-backed Codex setup.

Steps to reproduce

1. On Windows 11, open a WSL environment.
2. Install and configure Codex CLI so it is usable with:
   • Model provider: Azure OpenAI
3. Verify Codex is installed and usable in that WSL environment.
4. In Claude Code, install the plugin:

   /plugin marketplace add openai/codex-plugin-cc
   /plugin install codex@openai-codex
   /reload-plugins
   

5. Run:

   /codex:setup
   

6. Observe that the plugin reports:

   Codex is installed (v0.117.0) but not authenticated...
   

   and suggests only OpenAI-oriented login methods.

Environment

• OS: Windows 11
• Runtime environment: WSL
• Codex version: v0.117.0
• Codex provider: Azure OpenAI
• Plugin: openai/codex-plugin-cc

Why this matters

A lot of enterprise/dev environments use Azure OpenAI rather than direct OpenAI authentication. If the plugin is intended to reuse the local Codex CLI setup/config, it would be great if Azure-backed Codex worked too.

And if Azure-backed setups are out of scope for now, a clearer message would save users time and confusion.

Thanks again — excited about this plugin and happy to test further if helpful.

[dkundel-openai]

This should be fixed now in #177