# Apply Technique: Codex CLI v0.116.0: TUI Updates, Dynamic JS REPL, and Realtime Websockets
## What This Is
The latest OpenAI Codex CLI update significantly enhances the developer experience with a refreshed terminal interface and easier plugin management. It introduces powerful new capabilities for developers, including real-time data streaming with websockets and the ability to dynamically use existing project code within the AI's JavaScript environment.
Source: https://openai.com/index/introducing-the-codex-app/
## 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://openai.com/index/introducing-the-codex-app/) 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 Technique** — a pattern or methodology for working with AI models.
- Explain how this technique applies to my current project and what benefit it provides
- Implement it in a way that fits my existing codebase — suggest concrete files to modify or create
- If it requires specific model capabilities (structured output, function calling, etc.), verify my current provider supports them
- Show me a working example I can test immediately
## Additional Context
- Execute the command `codex --version` to check the currently installed version. If it is less than 0.116.0, run the update command recommended by the user's package manager (e.g., `brew upgrade codex-cli` or `npm install -g @openai/codex-cli@latest`).
- Scan the current project for relevant `.js` or `.mjs` utility files. Initiate a `js_repl` session and demonstrate the new dynamic import functionality by importing a function from an existing project file and executing it. Also, display the values of `codex.cwd` and `codex.homeDir` to show the new context variables.
- Formulate a plan that requires a potentially sensitive file system modification (e.g., writing to a file in the user's home directory). Use the built-in `request_permissions` tool to explicitly ask for user approval before attempting the operation, demonstrating the new runtime permission model.
## 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