hermes - 💡(How to fix) Fix [Docs]: Auth checks should recognize Codex OAuth credentials, not only OPENAI_API_KEY [1 participants]

Summary

Some docs/skills/auth-check guidance appears to assume OpenAI access is primarily represented by OPENAI_API_KEY. For Codex/OAuth-based setups, valid credentials may instead live in an auth file such as ~/.codex/auth.json.

This can cause false-negative setup checks or misleading troubleshooting advice: the user is logged in and the provider works, but the check says OpenAI credentials are missing because no OPENAI_API_KEY is present.

Suggested improvement

Update auth-check documentation and any relevant setup diagnostics to distinguish between:

• OpenAI API-key auth via environment/config
• Codex OAuth auth via local auth file/session

For example, guidance could say to check the Codex OAuth auth file/session before reporting missing OpenAI credentials when the configured provider is Codex/OAuth-backed.

Expected behavior

If a deployment is configured to use Codex OAuth, auth diagnostics should verify the OAuth credential path/session rather than only looking for OPENAI_API_KEY.

Why this matters

It avoids unnecessary downstream documentation patches and prevents users from being told their OpenAI credentials are missing when their Codex OAuth setup is actually valid.