OpenAI Codex began as a software development tool, but OpenAI now describes a much wider pattern of use. Analysts, marketers, operators, designers, researchers, investors, and bankers are using Codex for research, data analysis, documents, presentations, spreadsheets, and small internal tools. That makes OpenAI Codex for knowledge work a more useful subject than the vague claim that AI will “transform work.” We can look at the jobs people are handing to it, the outputs it creates, and the limits of the evidence.
OpenAI reported on June 2, 2026 that Codex had more than 5 million weekly active users. Knowledge workers accounted for about 20 percent of users and were growing more than three times as fast as developers. Those figures come from OpenAI, not an independent usage audit, but they show how the company sees the product changing: Codex is being positioned as a workspace for making things, not simply as a place to ask questions.
What knowledge work means in Codex
In OpenAI’s account, knowledge work includes creating reports, spreadsheets, presentations, contracts, and other finished materials. Research, data analysis, workflow automation, and lightweight tool building are also prominent. The fastest-growing task groups among knowledge workers were data analysis, research, and the creation of what OpenAI calls knowledge artifacts.
The distinction between an answer and an artifact matters. A chat response may explain a sales trend. A work product could be the spreadsheet that calculates it, the chart used in a meeting, the written summary, and a small dashboard where colleagues can explore the assumptions. Codex is intended to work across more of that chain.
OpenAI also says users increasingly run several Codex tasks in parallel. A researcher might investigate separate questions while another task organizes findings. An operator could prepare a report while a second task turns the same context into tickets. Parallel work may reduce waiting, but it does not prove that every result is correct or that the tasks agree with one another. More output can also mean more material to inspect.
Research and information spread across tools
Finding the right information is often harder than writing the final memo. Notes may be split between chat threads, shared documents, project trackers, and data systems. OpenAI says Codex can work with connected tools and organizational context through plugins. The practical promise is that a task can begin with the material where it already lives instead of requiring someone to collect every excerpt by hand.
Zapier offers a concrete example in OpenAI’s announcement. Its teams use Codex to pull knowledge from Slack, Google Docs, and Coda, then turn that context into postmortems, incident response plans, and feature tickets. This is more specific than saying Codex “does research.” The system gathers relevant internal material and reshapes it for a known business purpose.
That example does not establish that Codex will find every relevant message, resolve conflicting records, or judge which source is authoritative. Access to a tool is not the same as complete understanding of it. If a postmortem depends on dates, owners, or causal claims, a person familiar with the incident still needs to check the evidence. Readers who deal with information scattered across ChatGPT itself may also find our ChatGPT unified search guide useful.
Documents, spreadsheets, slides, and annotations
Codex is not presented only as a research collector. OpenAI says nontechnical teams inside the company use it to prepare executive materials, create dashboards, build internal apps, and turn creative briefs into work that follows brand and design constraints. These are production tasks with different kinds of structure. A spreadsheet needs formulas and traceable inputs. A presentation needs a readable argument. A branded asset must follow visual constraints rather than merely contain the right words.
Annotations are meant for the revision stage. A user can select a particular part of a document, spreadsheet, slide, site, Markdown file, or code file and request a focused change. OpenAI gives several examples: select a site’s navigation bar and ask for a different font, highlight a claim in an investment thesis and ask where it came from, or mark a chart and request a clearer label.
This is a sensible editing model because useful work rarely arrives in one perfect draft. A focused instruction can preserve the sections that already work. Still, the source describes how annotations direct a revision, not a guarantee that the revised claim, formula, or chart label is accurate. The user must read the changed section and check whether the surrounding material still makes sense.
Plugins and what “no code” means here
OpenAI introduced role-specific plugins that package tools, context, and workflows for a particular kind of work. Its announcement names a data analytics plugin for business performance analysis and says six role-specific plugins were launching. It also listed Corporate Finance, Private Equity Investing, Marketing Strategy, Strategy Consulting, and Legal among the plugins planned to come later.
The phrase “no coding required” refers to using the new role-specific plugins, according to OpenAI. It should not be stretched into a claim that every workflow is effortless or that technical work disappears. Teams can adapt plugins, build custom plugins, and share them for their own systems. Custom connections and specialized processes may still require people who understand the underlying data, permissions, and expected output.
A useful way to think about a plugin is as a prepared route through a task. It can give Codex access to relevant tools and establish a repeatable method. It cannot supply missing records, correct a bad source system, or decide what an ambiguous business term means for a particular company. If “active customer” has three definitions in three departments, connecting another tool will not settle the disagreement.
From a model to an interactive site
OpenAI also announced Sites, a preview feature for Business and Enterprise customers. The company describes Sites as hosted, interactive websites and apps that can be shared with people in a workspace by URL. Examples include dashboards, planners, review workspaces, project boards, galleries, and other lightweight tools.
The examples are concrete. Codex could turn material for a customer review into a page containing product updates, open questions, usage trends, and next steps. It could convert a financial model into a scenario planner where leaders compare assumptions. Launch materials could become a shared hub for current messaging, milestones, owners, and decisions. OpenAI says a site can be updated as those details change.
These examples explain the intended shape of the feature. They do not tell us how well any specific site will handle complex permissions, regulated data, heavy traffic, unusual calculations, or long-term maintenance. Nor do they show that a generated site is a replacement for a production application. “Lightweight tools” is the company’s own framing and is a useful boundary. For related coverage, see our guide to building and publishing sites with ChatGPT.
Documented examples from OpenAI, Zapier, and NVIDIA
The strongest part of OpenAI’s announcement is the set of named examples. Inside OpenAI, nontechnical teams make internal apps, dashboards, executive materials, and creative work. Zapier uses connected company knowledge for incident and product documents. At NVIDIA, researchers use Codex across experiment workflows, including finding research ideas and writing scripts for machine learning infrastructure.
These examples cover different handoffs. The OpenAI case moves from a brief or business need to a deliverable. The Zapier case moves from scattered internal context to structured records and plans. The NVIDIA case links scientific exploration with the scripts needed to support experiments. None of the examples says that people leave Codex alone to approve an executive report, determine the cause of an incident, or validate a scientific result.
OpenAI’s separate knowledge-work report also says people use Codex to find information buried across systems, coordinate work across tools and teams, produce deliverables, and move projects through review and approval. The final phrase is worth noticing. Review and approval remain part of the process. Codex may prepare and route work, while accountable people still decide whether it is ready.
What can be concluded, and what cannot
The official sources support a narrow set of conclusions. Codex is used by developers and nondevelopers. It can create several common work products, use connected context through plugins, accept targeted annotations, run tasks in parallel, and create shareable lightweight sites in the preview described by OpenAI. Named organizations report using it for real internal workflows.
The sources do not provide an independent comparison with competing products. They do not establish an error rate for research, financial analysis, contracts, spreadsheets, or generated sites. They do not claim that every plugin works with every system, that every role-specific plugin is already available, or that a user can safely skip subject-matter review. This article is based on the published material and does not present personal testing.
That leaves a straightforward standard for readers. Judge a Codex workflow by the evidence visible in its output. Can you trace a claim to its source? Do spreadsheet totals reconcile? Are assumptions shown? Does a generated site expose only the intended information? Can a reviewer understand what changed after an annotation? Those questions test the work itself without pretending that a product announcement answers them.
Official sources
- OpenAI: Codex is becoming a productivity tool for everyone, published June 2, 2026.
- OpenAI: Codex for every role, tool, and workflow, published June 2, 2026.
FAQ
Is Codex only for software developers?
No. Developers remain its largest user group, but OpenAI says knowledge workers account for about 20 percent of Codex users. The company specifically names analysts, marketers, operators, designers, researchers, investors, and bankers.
Can Codex create documents and spreadsheets?
OpenAI says knowledge workers use Codex to create reports, spreadsheets, presentations, contracts, and other work products. Annotations can target a selected part of documents, spreadsheets, and slides for revision. The sources do not guarantee the factual or mathematical accuracy of every output.
Do Codex plugins require coding?
OpenAI says its role-specific plugins are designed for use with no coding required. Teams can also customize plugins or build their own, which may call for technical knowledge depending on the systems and process involved.
Does Codex replace human review?
The official announcements do not say that it does. Their examples include work moving through review and approval, and annotations are built around human feedback. Important claims, calculations, permissions, and decisions still need an accountable reviewer.