Skip to main content
AI Choice Engine
Back to blog

Comparison

ChatGPT Work vs Chat vs Codex — which OpenAI surface are you buying?

OpenAI's consumer plan page lists GPT-6 models for Plus and Pro, while its Work/Codex guide describes a different Chat availability picture. Keep surfaces and API billing distinct.

Published August 10, 2026Updated October 1, 20266 min readAI ToolsBy AI Choice Engine Editorial

Product availability checked on 1 October 2026. OpenAI's consumer pricing page lists GPT-6 models for Plus and Pro, while its Work/Codex model guide says GPT-6.1 Sol, GPT-6 Sol and GPT-6 Luna are not available in Chat. The current first-party pages conflict about the Chat rollout; check the account's actual model picker before buying for a specific model.

OpenAI's ChatGPT surfaces and plan descriptions can differ. The August consumer refresh announced GPT-5.6 defaults; the September GPT-6 launch initially described Work and Codex availability, and the October consumer pricing page now lists GPT-6 models for Plus and Pro. Keep Chat, Work, Codex and API usage distinct, and confirm current access on the relevant account.

This guide is for UK teams deciding whether to buy ChatGPT Chat, ChatGPT Work, OpenAI Codex / coding agents, or raw API — and how those choices relate to Free vs Plus after the Luna/Think refresh. Related reading: ChatGPT Free vs Plus 2026, Sol / Luna / Terra tiers, and the OpenAI Codex harness.

Three products, three jobs

SurfaceBest forWatch-out
ChatGPT ChatEveryday Q&A and draftingConsumer plan page lists GPT-6 models for Plus/Pro, but another OpenAI guide describes them as unavailable in Chat; verify in account.
ChatGPT WorkTeam knowledge and workplace workflowsAccess and model availability depend on plan, client, settings and rollout.
Codex / coding agentsDelegated coding against reposChatGPT plans include varying Codex access; check plan allowance and model access. API usage remains separately billed.

Chat is the consumer conversation product. OpenAI's August 2026 announcement described Free/Go Luna with Think and refreshed Sol with effort controls for paid users; its current consumer plan page lists GPT-6 models for Plus/Pro. These are dated product snapshots, and the current Work/Codex model guide describes a different availability picture. Check the relevant model picker.

Work is the workplace product: shared knowledge, admin, and team workflows. Buy Work when the job is organisational ChatGPT with controls — not when the job is “developers need an agent on the monorepo.” Expect feature and model lag versus consumer Chat after major Chat-only refreshes until OpenAI says otherwise.

Codex and related coding agents are for repository work. ChatGPT plans include varying levels of Codex access, so check the plan's current allowance and model availability. Compare Codex with Cursor, Claude Code, and GitHub Copilot on setup cost, review discipline, and metering. API billing remains separate from ChatGPT plan usage.

Raw API (gpt-6.1-sol, gpt-6-sol, gpt-6-luna, gpt-5.6-terra and older IDs) is a fourth meter entirely. Product features that call the API should budget tokens separately from Chat seats. See the current GPT-6.1 Sol, GPT-6 Sol and GPT-6 Luna profiles.

How teams usually get this wrong

The classic failure mode is a single spreadsheet cell labelled “OpenAI” that mixes:

  • Founder Plus subscriptions used for email drafts.
  • A Work rollout for customer support macros.
  • A quiet Codex or Cursor BYOK spike on Sol.
  • A backend feature calling the API on every page view.

When September pricing or weekly limits bite, nobody knows which surface to cut. Split the cell into Chat, Work, Codex/harness, and API before you renew anything.

GPT-6.1 Sol rollout in Work and Codex

OpenAI released GPT-6.1 Sol on 29 September after GPT-6 Sol and Luna launched on 22 September. As of 1 October, the consumer pricing page lists GPT-6.1 Sol, GPT-6 Astra, GPT-6 Sol and GPT-6 Luna for Plus, with expanded access on Pro. The separate model guide lists GPT-6.1 Sol, GPT-6 Sol and GPT-6 Luna as Work/Codex models and says they are not available in Chat. This is a first-party documentation conflict; confirm the exact account's current picker. API prices are separate: gpt-6.1-sol is $2/$10 per million standard tokens with $0.10 cached input; GPT-6 Sol is $2/$10 with $0.20 cached input; GPT-6 Luna is $0.10/$0.50.

For buyers this is a model-availability detail, not a guarantee that every paid account has the rollout. If the job is company knowledge work or delegated coding, check the tenant's actual model picker and plan access before committing. A Plus receipt alone does not establish that a Work or Codex model is available to that account.

Another failure mode: assuming a model listed on a plan page is available in every client or workspace. Read the current product guide and confirm in the tenant's picker; schedule validation for each surface separately.

A practical buying sequence

  1. Write the job in one sentence: draft emails, answer employees with company knowledge, ship code with an agent, or power a product feature.
  2. Map the job to Chat, Work, Codex/harness, or API — only one primary surface.
  3. For Chat, compare Free/Go vs Plus/Pro using the current plan page and model picker because OpenAI's availability pages differ.
  4. For Work, run a pilot with real knowledge sources and admin policies before company-wide seats.
  5. For coding, run the AI coding assistant finder and compare setup guides — do not default to Codex because the brand is OpenAI.
  6. For API, pick model IDs and rate limits explicitly; never “whatever Chat uses.”

When to prefer something else

  • Heavy IDE agent work with multi-file refactors: evaluate Cursor or Claude Code beside Codex.
  • Strict data residency or BAA paths: check each vendor’s enterprise story; OpenAI Chat alone may not be the answer.
  • Pure automation without chat UX: prefer API or an automation platform, not Chat seats.
  • A Microsoft 365 shop: on 25 September Microsoft announced a new Copilot app that combines Chat and Cowork, with a Code capability for building small apps. Everyday Copilot use is covered by a per-user licence, while Cowork, Code and frontier models run on usage-based billing. Compare that seat model against ChatGPT Work before buying either.

Common mistakes

  • Buying Plus for every employee when Work was the real requirement — or the reverse.
  • Expecting Codex behaviour from ChatGPT Chat.
  • Assuming an announced Work/Codex rollout means every account has access immediately.
  • Treating API spend as included in Chat subscriptions.
  • Skipping harness comparison because “we’re already an OpenAI shop.”

Bottom line

Buy the surface that matches the job. Chat, Work, and Codex have separate controls and allowances, and current model availability pages do not fully agree. Keep API billing separate, verify the plan and account picker, and pilot workplace and coding workflows before standardising.

Sources

Editorial note

AI Choice Engine publishes editorial guides to help readers understand fit, trade-offs, and next steps before choosing a tool or provider.

Newsletter

Get the buyer checklist that goes with this guide

Subscribe to download the matching checklist. Automated email delivery is still rolling out — this is not an inbox confirmation.

A practical scorecard for comparing fit, cost, rollout risk, support, and lock-in.

Updates only — checklists stay free from the resource library, with or without joining. Automated email delivery is still rolling out.

Next step

Use the live tool while the trade-offs are still fresh

The article gives context. The live tool turns those trade-offs into a clearer shortlist.

Buying guides

Guide pages connected to this article

These guides go one level deeper for readers who want a longer-form buying view before choosing a provider.

Keep reading

More articles in the same decision path

These pieces stay inside the same research journey instead of sending you somewhere unrelated.

  1. ChatGPT Free vs Plus in 2026 — Luna, Think, and the Sol sliderOpenAI's October plan page and Work/Codex model guide differ on GPT-6 Chat availability. Here's the dated August refresh, the current plan summary, and what to verify in your account.
  2. Claude Opus 5.5 vs Budget Flash Tiers — When API Spend Should SplitPaying frontier prices for volume work is the most common API overspend pattern in 2026. The September price cuts made the gap wider, not narrower. The fix is still tier routing, not a single default model.

Next steps

Next step across the network

Continue with a focused hub page instead of restarting your research from scratch.