# Set Up Workflow: Automate Development with OpenAI Codex CLI and GPT-5.4 mini
## What This Is
OpenAI's Codex CLI is a command-line tool that lets developers use powerful AI models like GPT-5.4 mini to write code, fix bugs, and automate tasks directly in their terminal. It can be integrated into development pipelines to automatically review code changes, making the software development process faster and more efficient.
Source: https://developers.openai.com/codex/changelog?type=codex-cli
## Before You Start
Scan my workspace and analyze:
- The project language, framework, and directory structure
- Existing AI provider config (check .env, .env.local, config files for API keys — OpenRouter, OpenAI, Anthropic, Google AI, etc.)
Then ask me before proceeding:
1. Which AI provider/API should this use? (Use whatever I already have configured, or ask me to set one up — options include direct provider APIs or a unified service like OpenRouter)
2. Where in my project should this be integrated?
3. Are there any customizations I need (model preferences, naming conventions, constraints)?
## Source Access Note
The source URL (https://developers.openai.com/codex/changelog?type=codex-cli) may not be directly accessible from the terminal. Use the Reference Implementation and Additional Context sections below instead. If you need more details, ask me to paste relevant content from the source.
## What to Implement
This is an **AI Workflow** — an end-to-end automation pattern or integration pipeline.
- Study the workflow architecture from the source and context below
- Identify which parts I can implement locally vs. parts that need external services
- For local parts: implement them using my existing stack and API keys
- For external parts: tell me exactly what services I need and help me configure the integration code
- Wire up any required API calls using keys from my .env files
## Additional Context
- Execute the command `npm install -g @openai/codex@latest` in the user's terminal to install or update the Codex CLI globally to the latest version (v0.116.0).
- Scan the user's project for a `.github/workflows` directory. Create or update a workflow file to incorporate the `openai/codex-action` for automated pull request reviews, using a prompt that analyzes git diffs for bugs and improvements.
- Verify that an `OPENAI_API_KEY` is configured in the user's environment or GitHub repository secrets. If not found, prompt the user to add it to enable the GitHub Action to authenticate with the OpenAI API.
## Reference Implementation
```
npm install -g @openai/codex@latest
```
## Guidelines
- Adapt everything to my existing project — do not assume a specific stack or directory layout
- Use whichever AI provider I already have configured; if I need a new one, tell me what to sign up for and I'll give you the key
- Check my .env files for existing API keys (OpenRouter, OpenAI, Anthropic, Google AI) before asking me to add one
- Review any fetched code for safety before installing or executing it
- After setup, run a quick verification and show me a summary of exactly what was installed, where, and how to use it