OpenAI expands Codex with Sites, Annotations, plugins

OpenAI updated ChatGPT Codex with in-thread web tooling and an expanded plugin ecosystem, per OpenAI documentation and independent coverage. The Codex in-app browser supports browser comments for visual annotations and lets users manage allowed and blocked websites from settings, according to the Codex app developer guide. OpenAI Academy materials show Codex workflows aimed at turning calendars, messages, docs, and dashboards into review-ready briefs. Independent reporting and a release guide note broader platform additions including gpt-image-1.5, background Computer Use (desktop control features), and a plugin catalog; Digital Applied reports 90+ plugins are available and SiliconANGLE describes a plugin directory with more than a dozen prepackaged integrations. Editorial analysis: these additions move Codex from a coding assistant toward a broader knowledge-worker automation hub, raising integration and trust tradeoffs practitioners should evaluate.
What happened
OpenAI released a series of feature updates to ChatGPT Codex, documented in OpenAI's developer and Academy pages and summarized by independent outlets. Per the Codex app documentation, the in-app browser now supports browser comments, which let users leave visual annotations directly on rendered pages, and the settings include management of allowed and blocked websites. OpenAI Academy guidance published April 23, 2026, highlights Codex workflows that convert calendars, messages, emails, documents, dashboards, and spreadsheets into review-ready artifacts such as briefs, decks, and plans. Independent coverage and release guides report additional platform changes: Digital Applied's April 16 guide lists gpt-image-1.5, background Computer Use features that let Codex operate alongside the user on macOS, and a plugin ecosystem; Digital Applied reports 90+ plugins and SiliconANGLE describes a plugin directory with more than a dozen prepackaged integrations.
Technical details
Editorial analysis - technical context: The browser comments capability is delivered via Codex's in-app browser, which the developer documentation describes as a rendered, sandboxed view that does not carry cookies, signed-in states, or extensions. That limits access to authenticated pages but enables read-only inspection, screenshots, element-level comments, and basic DOM interaction without exposing user browser state. Background Computer Use, per independent reporting, provides a separate agent cursor and the ability for Codex to perform scheduled or multi-step desktop tasks on macOS first, which implies elevated local automation scope compared with in-thread-only assistants.
Platform integrations
OpenAI's plugins and skills model remains the extension path for task automation and data access, per OpenAI's Plugins and Skills documentation. Skills are described as workflow playbooks combining natural language instructions and technical assets, while plugins connect Codex to external tools. Reported integrations called out by third-party coverage include connectors to Google Drive, GitHub, Atlassian, CircleCI, Microsoft Office, and Neon by Databricks. Digital Applied's summary cites a catalog of 90+ plugins, and SiliconANGLE notes prepackaged integrations and the ability to include multiple components in a single plugin.
Context and significance
Public reporting frames these updates as part of a broader industry shift where coding-oriented assistants are expanding into knowledge-worker automation. The combination of desktop control, visual in-thread inspection, and a large plugin catalog follows competitor moves in the code-assistant space and aligns with patterns of productizing agentic and integration features to reduce manual context assembly.
Practical implications for practitioners
Editorial analysis: For engineers and platform builders, the in-app browser and browser comments reduce friction for reproducing UI bugs and producing front-end fixes without duplicating screenshots or lengthy step-by-step descriptions. For security and privacy teams, the developer documentation's explicit note that the in-app browser does not support authentication or carry cookies is important, but the presence of background Computer Use and broad plugin access increases the attack surface for misconfiguration and data leakage if connectors are granted excessive scope. For product teams, skills provide a way to encode repeatable workflows and guardrails, but they also require careful testing to avoid automation that depends on brittle DOM structure or unauthenticated page content.
What to watch
For practitioners and procurement teams, monitor plugin permission models and audit logs as organizations scale Codex integrations. Watch whether OpenAI extends authenticated browser support or adds enterprise controls for permitted sites and plugin scopes. Track early adopter reports about reliability of background Computer Use on macOS and the extent to which plugins surface structured data suitable for programmatic consumption versus requiring human verification.
Scoring Rationale
This is a notable product expansion from a major platform that broadens Codex from coding assistance toward knowledge-worker automation. The changes matter to engineers who will integrate plugins and to security teams who must manage permissions, but the update is an incremental platform evolution rather than a frontier-model release.
Practice interview problems based on real data
1,500+ SQL & Python problems across 15 industry datasets — the exact type of data you work with.
Try 250 free problems

