← Back to AI Insights
Gemini Executive Synthesis

Codex plugin login status misreporting for Azure model provider

Technical Positioning
Flexible authentication support, enterprise integration.
SaaS Insight & Market Implications
This issue exposes a critical flaw in the Codex plugin's authentication status reporting, specifically for enterprise users leveraging Azure OpenAI. The `codex login status` command and the plugin's internal `getCodexLoginStatus()` function are rigidly tied to OAuth, failing to recognize valid API key-based authentication via custom `model_provider` configurations. This prevents Azure users from utilizing core plugin functionalities like `/codex:review` and `/codex:task`, despite the underlying CLI working correctly. This oversight significantly limits enterprise adoption and demonstrates a lack of foresight in accommodating diverse authentication strategies, a common requirement in B2B SaaS.
Proprietary Technical Taxonomy
Codex CLI Azure OpenAI model provider config.toml OAuth-based login env_key getCodexLoginStatus() /codex:review /codex:task

Raw Developer Origin & Technical Request

Source Icon GitHub Issue Mar 31, 2026
Repo: openai/codex-plugin-cc
`codex login status` reports "Not logged in" when using Azure model provider

Hi there! Thanks for the great plugin — really looking forward to using Codex from Claude Code.

## Description

I have Codex CLI configured with an Azure OpenAI model provider via `config.toml`, and everything works great with `codex -p`. However, I noticed that `codex login status` returns exit code 1 with "Not logged in" in this setup, which seems to only check for OAuth-based login.

**My config.toml:**
```toml
model = "gpt-5.4"
model_provider = "azure"

[model_providers.azure]
name = "Azure OpenAI"
base_url = ".openai.azure.com/openai/v1&quot
env_key = "AZURE_OPENAI_API_KEY"
wire_api = "responses"
```

```
$ codex login status
Not logged in # exit code 1

$ codex -p "hello"
# works perfectly fine
```

## Impact

The companion plugin uses `getCodexLoginStatus()` as a gate before running reviews or tasks. Since this check doesn't recognize Azure provider authentication, Azure users see:

> Codex CLI is not authenticated. Run `!codex login` and retry.

This prevents us from using `/codex:review` and `/codex:task` in Claude Code, even though the underlying Codex CLI works perfectly.

## Suggestion

Would it be possible for `codex login status` (or `getCodexLoginStatus()` in the plugin) to also consider non-OAuth authentication methods? For example, when a custom `model_provider` with an `env_key` is configured, the check could verify that the corresponding environment variable is set.

## Environment

- Codex CLI: 0.117.0
- codex-plugin-cc: 1.0.0
- OS: macOS...

Developer Debate & Comments

No active discussions extracted for this entry yet.

Adjacent Repository Pain Points

Other highly discussed features and pain points extracted from openai/codex-plugin-cc.

Extracted Positioning
Sandbox environment access failure for Codex reviews
Secure and functional code review environment.
Top Replies
SatyKrish • Mar 30, 2026
I get similar issue with sandbox environment. ``` The Codex reviewer couldn't access the shell in its sandbox. The review output is above — it was unable to execute due to sandbox restrictions in t...
dkundel-openai • Mar 30, 2026
Thanks for flagging. I'm looking into this!
dkundel-openai • Mar 30, 2026
@arvidkahl inside bash can you run `which codex` and `codex --version`? There might be a version mismatch happening here.
Extracted Positioning
Persistent multi-turn Q&A / consultation command
Enhanced developer workflow, contextual AI assistance, interactive code exploration.
Extracted Positioning
Codex plugin authentication failure within Claude Code
Seamless integration, reliable authentication across environments.

Engagement Signals

2
Replies
open
Issue Status

Cross-Market Term Frequency

Quantifies the cross-market adoption of foundational terms like Codex CLI and /codex:review by tracking occurrence frequency across active SaaS architectures and enterprise developer debates.