# Set Up Workflow: Codex CLI: Automating Terminal Workflows with Natural Language
## What This Is
Codex CLI is a command-line tool from OpenAI that allows developers to execute complex coding tasks, like setting up projects or managing Git branches, using simple English commands directly in their terminal. It enhances productivity by automating multi-step processes and can be integrated into larger CI/CD pipelines for intelligent deployments.
Source: https://www.nxcode.io/resources/news/claude-code-vs-codex-cli-terminal-coding-comparison-2026
## 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://www.nxcode.io/resources/news/claude-code-vs-codex-cli-terminal-coding-comparison-2026) 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
- Install the Codex CLI globally on the user's machine by executing 'npm install -g @openai/codex-cli'.
- Configure the CLI by locating the user's OpenAI API key from their environment variables (e.g., OPENAI_API_KEY in .env) and setting it up for the tool. If no key is found, prompt the user to provide one.
- Demonstrate functionality by running a project-aware command. For example, if in a Git repository, execute 'codex "create a new feature branch named 'test-codex-integration', commit all current changes with a placeholder message, and print the git log"' to show its capabilities.
## Reference Implementation
```
$ codex "set up a new Next.js project with TypeScript, Tailwind, and Prisma"
→ npx create-next-app@latest my-app --typescript --tailwind --app
→ cd my-app && npm install prisma @prisma/client && npx prisma init
```
## 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