Allow ChatGPT Pro users to create Codex access tokens for CI automation
What variant of Codex are you using?
Codex CLI, GitHub Actions / CI automation
What feature would you like to see?
Please allow ChatGPT Pro users to create and use Codex access tokens for non-interactive Codex CLI automation, including GitHub Actions.
Today, the documented Codex access token flow appears to be limited to ChatGPT Business and Enterprise workspaces. For individual Pro users, this makes it hard to run codex exec in CI with the same Codex entitlement model used locally. The current practical alternative is to use an OpenAI Platform API key, but that changes the billing/authentication model and does not match the way many individual Codex users work locally.
A useful implementation would be one of these:
- Allow ChatGPT Pro users to create a scoped Codex access token from ChatGPT settings.
- Support a CI-scoped Codex token with expiration, revocation, and least-privilege permissions.
- Document a supported GitHub Actions pattern for Pro users that does not require Business/Enterprise workspace administration.
Additional information
Use case: an individual Pro user wants to run Codex CLI in GitHub Actions to generate repository artifacts from checked-in prompts/skills, without using Claude Code or another agent runtime. The workflow is non-interactive and would run codex exec on a trusted runner.
Security controls that would make this workable:
- Required expiration date
- Manual revocation from ChatGPT settings
- Scope limited to Codex CLI/non-interactive execution
- Clear guidance for storing the token as a GitHub Actions secret
This would make Codex automation more accessible for solo developers and small teams that are not on Business/Enterprise but already use ChatGPT Pro for Codex locally.