Last checked: October 5, 2026. Codex Voice is a live voice interface in the ChatGPT desktop app. Open a Work or Codex task, start Voice, and speak to begin or steer work. OpenAI documents desktop Voice for macOS and Windows, subject to plan, rollout, and workspace access. Voice time and task-model usage follow separate billing rules; tool-specific costs depend on the plan and tool pricing.
Three distinctions prevent most setup and billing confusion: desktop Work/Codex Voice is not ordinary Chat Voice; Web and mobile support Voice in Work while Codex Cloud tasks are a separate documented surface; and the GPT-Live API is a developer product, not a way to turn on desktop Voice with an API key. The table below keeps those routes separate.
Codex Voice mode in one table
| Surface | What the current documentation says | How to interpret it |
|---|---|---|
| Work or Codex in the desktop app | Voice is available in the ChatGPT desktop app on macOS and Windows. Eligible plans include Plus, Pro, Business, Edu, and Enterprise; Enterprise and Edu have a two-week early-access period. Availability also depends on rollout and workspace settings. OpenAI Voice guide | Use this surface for live discussion around a Work or Codex task: start work, interrupt, check progress, or redirect it. Existing-task Voice is still rolling out. |
| Work on web, iOS, or Android | Voice in Work is available on web, iOS, and Android for accounts with both Voice and Work access. It can use the tools and connected apps available to that Work task, and unfinished work can continue in text after a call. Work and Codex access guide | This is Work Voice. The Help Center separately says Codex Cloud tasks can start and continue on web or mobile; it does not label the web/mobile Work Voice control as a dedicated Codex Voice surface for those tasks. |
| Codex Cloud on web or mobile | Codex Cloud lets you start and continue coding tasks from desktop, web, or mobile after a suitable environment is available. OpenAI Help Center | Cloud task access and Voice availability are documented separately. Do not infer that a desktop Codex Voice control is present in every Cloud task. |
| Regular Chat Voice | Chat Voice is the conversational Chat experience, with its own plan, platform, and usage limits. ChatGPT Voice Help | Do not use Chat Voice minute limits as the desktop Work/Codex Voice rate. |
| GPT-Live API | GPT-Live 1 is available to developers through the API. Voice sessions have separate API pricing and the backend model or tools are billed separately. GPT-Live 1 model docs | This is a build-your-own app path, not desktop Voice entitlement. |
What OpenAI actually launched
OpenAI’s release notes place “ChatGPT Voice in Work and Codex on desktop” in the July 23, 2026 entry. The current Voice guide describes the desktop experience as a live conversation powered by GPT-Live: you can speak, interrupt, check progress, and ask Voice to start or coordinate tasks using the tools and permissions available to the selected Work or Codex experience. The model handling the task is billed separately from the Voice conversation. July 23 release note · current Voice guide · current pricing.
Plan access is not the same as guaranteed control visibility. Enterprise and Edu access begins with a two-week early-access period, and workspace administrators can control feature access. The product guide also says Voice in existing Codex tasks is rolling out; if that control is missing, update both the desktop app and the Codex host running the task, then check account and workspace availability.
Codex Voice mode versus dictation, Chat Voice, and remote control
Live Voice keeps a conversation open while an agent works: you can interrupt, ask a follow-up, or redirect the task. Voice dictation turns speech into prompt text you can review and edit before sending. Chat Voice is for conversational Chat, while Work Voice and Codex Voice direct their respective task experiences. They share a familiar voice interface, but their tools, permissions, and usage rules differ. OpenAI distinguishes Voice from dictation.
OpenAI also documents ChatGPT Voice through Remote on a paired iOS device. That is remote access to a supported desktop task, not a native mobile Codex Voice surface; the cited Voice guidance does not establish equivalent Remote Voice access on Android. Codex Cloud tasks also run on web and mobile, but the Help Center describes that access separately from Work Voice. OpenAI Voice and Remote guidance.
How to start Voice in Work or Codex
- Open the right task. In the ChatGPT desktop app, choose Work or Codex and open the task you want to discuss, or start a new chat or task.
- Start Voice. In an existing task, select Start voice chat when it is available. In a new chat or task, select Start new voice chat. A shortcut you configured in Settings is also available; OpenAI does not specify a universal default desktop shortcut.
- Allow the requested access. The first time, grant microphone access and choose a preferred voice. Review optional Screen context on macOS; that may prompt for Screen & System Audio Recording and Accessibility permissions.
- Describe the outcome and boundaries. Say what you want done, which materials to use, and whether the task should inspect, draft, or make changes. Follow the live text, interrupt when needed, and review the written result. Select Stop voice chat when finished.
For an existing Codex task without a Voice control, OpenAI recommends updating the desktop app and the Codex host. Account eligibility, workspace settings, and the rollout can also affect availability. See OpenAI’s setup and troubleshooting steps.
Why you may not see Codex Voice yet
- Your plan or workspace does not have access. Voice and Work access may both be required; an administrator can limit workspace features.
- The feature has not reached your account or existing task. OpenAI describes rollout availability and says Voice in existing Codex tasks is still rolling out.
- The desktop app or Codex host needs an update. Update both when Voice is missing from an existing task, then reopen the task and check its settings.
- Another desktop Voice conversation is active. Only one Voice conversation can run at a time across the desktop app.
The current setup guidance does not name a minimum desktop version or a default Voice shortcut. Avoid relying on launch-era version numbers or a shortcut from another Codex interface.
How pricing and usage actually work
Separate the time spent in the Voice conversation from the Work or Codex task that follows your instructions. The published desktop rate covers Voice time; the task still uses the selected model, tools, and shared Work/Codex usage.
| Usage type | Published rate or rule | What it does not include |
|---|---|---|
| Desktop Work/Codex Voice | $0.05 per minute against the existing Codex usage budget. For Business, Edu, and Enterprise workspaces with credit-based billing, the rate is 1.25 credits per minute; it also applies when Plus or Pro users spend additional credits. OpenAI pricing | The selected task model uses its applicable Work/Codex allowance or rate. Any tool-specific charge depends on the plan and tool pricing; this Voice rate does not mean every tool call adds a separate fee. |
| Work/Codex task | Uses the selected experience’s model, tools, and agentic usage pool. A task costs the same whether you begin it by speaking or typing. Work and Codex usage | The desktop Voice-minute charge is separate where flexible pricing applies. |
| Work Voice on web or mobile | Uses minutes from the account’s daily Voice allowance; Work task usage still applies. | Do not substitute the desktop $0.05/minute line for this Voice allowance. |
| GPT-Live API session | $0.05 per minute, billed per second without rounding up to a full minute. GPT-Live API rate | Backend model and tool usage are charged separately at their normal API rates. |
As a simple rate-based estimate, a 10-minute desktop Voice conversation has a $0.50 Voice component before the task-model usage and any plan-specific tool charges; on a credit-based rate, the Voice component is 12.5 credits before task usage. Whether that comes from included usage or additional credits depends on the plan and workspace. It is not a total-task quote. Ordinary Chat Voice has its own plan limits, so do not use those caps to estimate desktop Work/Codex cost. Check your plan or workspace rate card before a long session.
Does Codex Voice work in the API, CLI, or IDE?
API: GPT-Live is available, but it is a separate product
GPT-Live 1 became generally available in the API on September 10, 2026. A developer can build an application using the documented live session endpoint and supported connection options; API Voice sessions are priced separately from desktop Voice. ChatGPT Voice in Desktop is not available through an API key. For implementation details, see DMT’s GPT-Live 1 API guide and OpenAI’s Live API quickstart and September 10 API changelog.
CLI: a separate terminal Voice feature is documented
The official Codex CLI 0.156.0 release entry, dated September 22, documents Voice conversations enabled by default, an F8 toggle, a /voice settings picker, and bundled audio runtimes for Linux and Windows. That is CLI/TUI behavior; it does not establish the desktop app’s shortcut. Codex CLI changelog.
IDE extensions: desktop parity is not established here
The sources above describe desktop Work/Codex Voice, the GPT-Live API, and a CLI release. They do not establish that a VS Code or other IDE extension exposes the same live Voice control. Check the documentation for the specific extension rather than inferring support from the desktop app or CLI.
What early users are asking – and what is actually known
A September 30 OpenAI Developer Community post describes one Windows user whose Dictate button was disabled while Voice worked in the same Codex app; another reply reports dictation working on a newer build. That is a limited community report, not a confirmed cause or a general product rule. It does show why a dictation-button problem should not automatically be treated as a Voice-session failure. Read the individual report.
Who Codex Voice is for: roles and realistic use cases
Voice is most useful when the work needs back-and-forth steering. These prompt patterns show where that can help:
- Plan before editing: “Inspect this project read-only. Summarize the goal, assumptions, and smallest test. Wait before editing.” This lets you correct scope while the task is still a plan.
- Steer a debug session: “Tell me what you have ruled out and what evidence is missing. Propose the next check before changing dependencies.” Use follow-up questions to keep the investigation on the evidence you care about.
- Review a research or marketing draft: “Separate source-confirmed facts from recommendations, point out unknowns, and preserve the current page’s reader intent. Do not publish or change the live account.” The voice conversation can help refine a brief; review the resulting text and sources before using it.
- Coordinate multiple tasks: “Ask one agent to inspect the documentation and another to run the tests. Have each return its owner, evidence, files touched, and next step; pause edits until I review their written results.” Confirm ownership and changed files before authorizing follow-up work.
OpenAI documents Voice for checking progress, redirecting work, and coordinating tasks. That makes it a conversational control for ongoing work, not a replacement for written acceptance criteria or review.
Where Voice is the wrong interface
Typing or dictation is usually better for exact code, filenames, URLs, account IDs, long structured data, and anything that must be copied verbatim. A noisy environment or a shared room may also make speech impractical. Use Voice to explain the outcome, then confirm exact strings and consequential changes in the written task before they are applied.
Privacy, screen context, and transcript accuracy
Voice uses the tools and permissions available to the selected Work or Codex experience. It does not create access that the task lacks. ChatGPT Voice Help distinguishes Live in Chat, which does not support video or screen sharing, from Advanced, which retains supported video and screen-sharing features on eligible mobile devices. Those Chat features do not establish camera or screen-sharing controls for desktop Work/Codex Voice. Separately, on macOS, optional Screen context is an on-demand appshot of the frontmost window. OpenAI says an appshot may include the window image and accessible text outside the visible scroll area; an organization can disable it. The cited desktop guidance does not establish Windows screen capture. Close or switch away from sensitive windows before requesting an appshot. ChatGPT Voice Help · desktop Screen context guidance.
OpenAI’s Voice Help says transcripts are not verbatim and may differ when people speak over one another, background noise is present, or the conversation moves quickly. Listen for possible errors in names, quantities, paths, and commands. Correct them before relying on the resulting task or document. ChatGPT Voice Help.
OpenAI’s Voice Help describes audio clips from Live and Advanced Voice conversations as stored with the chat transcript and retained for 30 days. It also says deleting a chat removes its associated clips within 30 days, subject to stated security, safety, legal, and prior-sharing exceptions. The same page says audio/video clips are not used to train models unless you opt to share those clips for model improvement; if “Improve the model for everyone” is on, transcripts and other Voice conversation files may be used depending on plan and settings. These statements describe Voice conversation data. They do not establish that every local file or task-created artifact has 30-day retention. Voice data controls.
For personal ChatGPT plans, the Data Controls guide says “Improve the model for everyone” also applies to Codex tasks, while a separate Include environments setting controls additional Codex environment context. Changing the ChatGPT setting does not change that separate environment setting. Managed workspaces do not use workspace content to train models by default, but organization retention and access policies still apply. Check Data controls in ChatGPT and your workspace policy before using sensitive content.
A practical safety checklist for voice-directed agents
- Before speaking: choose Work or Codex deliberately, limit the files and connected tools to what the task needs, and say whether the first step is read-only, draft-only, or allowed to edit.
- Before an important action: ask the agent to state the target, intended change, and evidence. Voice follows the same permissions as the selected task. In Work Voice on web or mobile, actions requiring approval must be approved or declined with on-screen controls; spoken approval is not supported.
- After the task: inspect the written answer and any files or changes. Verify external recipients, publication, spending, deletion, or production changes through their normal review path.
For a broader guide to app access, approval boundaries, and data safety, see DMT’s ChatGPT app-permissions checklist. Voice changes how you give instructions; it does not remove the selected experience’s access controls.
Frequently asked questions
Is Codex Voice available on Windows?
Yes. OpenAI documents desktop Voice in Work and Codex on macOS and Windows, subject to account rollout and workspace settings.
Can I use Codex Voice on iPhone or Android?
Work Voice is documented on web, iOS, and Android, and Codex Cloud tasks can run on web and mobile. OpenAI documents Voice through Remote on a paired iOS device for supported desktop chats; the cited pages do not establish equivalent Remote Voice access on Android. These are separate paths, not one native mobile Codex Voice mode.
Why is the Voice button missing in an existing Codex task?
Existing-task Voice is rolling out. Check plan and workspace access, then update the desktop app and Codex host. A Voice conversation already active elsewhere in the app can also prevent starting another one.
Is Codex Voice free, and does it use the API?
Desktop Voice is published at $0.05 per minute, or 1.25 credits per minute on credit-based billing, with task usage charged separately. Desktop Voice is not available by API key; GPT-Live 1 API sessions are a separate developer product.
Can Voice bypass approvals, and are transcripts exact?
No. Voice follows the selected task’s permissions, and Work Voice on web/mobile uses on-screen controls for approvals. Voice transcripts can differ from the words spoken, so review names, numbers, and commands before acting on them.
Bottom line
Use the desktop ChatGPT app for documented Codex Voice on macOS or Windows, and check your plan and workspace if the control is missing. Keep desktop Voice minutes separate from the model and tools used by the task; treat Work Voice, Codex Cloud, regular Chat Voice, the CLI, and GPT-Live API as distinct documented surfaces.
Disclosure: This guide was prepared with AI assistance and checked against the linked documentation on October 5, 2026. No first-hand desktop Voice, CLI, IDE, or API test is claimed.
