OpenAI’s Codex now supports internet access during coding and accepts voice input

Now open to ChatGPT Plus users

OpenAI’s AI coding assistant, Codex, is now open to ChatGPT Plus users. Previously limited to Enterprise, Team, and Pro plans, this rollout lets individual developers and smaller teams harness Codex’s power to write, test, and debug code more efficiently. Codex lives inside ChatGPT and handles everything from building new features to fixing bugs and tackling tough coding questions. Each task runs in a secure, isolated sandbox to keep your code safe, as per OpenAI.

Codex runs on a specialised version of OpenAI’s o3 model, trained specifically for programming. Built through reinforcement learning on real-world projects, it aims to write code that mirrors human developers—especially in handling pull requests and following instructions. 

The biggest update is Codex can now access the internet during coding tasks. This lets it install dependencies, interact with staging servers, and run tests needing external resources. But OpenAI is cautious—internet access is off by default. You enable it manually and control which domains and HTTP methods Codex can use.

Another handy upgrade is voice input—developers can now speak their instructions instead of typing, speeding up workflows and making Codex more accessible for those who prefer or need voice interaction. 

ALSO SEE: ChatGPT memory boost feature is now available for free-tier chatters

To get started, Codex lives in the ChatGPT sidebar. Pick “Code” after typing a prompt to assign a task, or hit “Ask” for help understanding your codebase. Each task runs one at a time in its workspace where Codex reads, edits, and tests your code. Depending on the complexity, it takes between 1 and 30 minutes, with progress visible in real-time.

OpenAI is also actively watching for prompt injection attacks—where bad actors try to fool Codex into making unintended web requests—to keep the tool secure. Behind the scenes, several performance tweaks have been introduced, like faster setup scripts, smoother handling on iOS, and a better GitHub connection process. For teams using social logins or single sign-on, two-factor authentication is now optional, making sign-in simpler.