OpenAI adds webhook-triggered Work tasks and deprecates Codex MCP server

OpenAI’s late-August release notes add a more event-driven workflow to ChatGPT Work and announce a breaking change for Codex MCP integrations. Work scheduled tasks can react to supported app activity, while the codex mcp-server command is now deprecated in favor of the Codex app server.

ChatGPT Work tasks can respond to app events

Work scheduled tasks can now use webhooks to respond when something changes in a supported app. OpenAI lists new Gmail messages, Slack channel messages, and GitHub pull-request activity as supported triggers. A task can summarize an incoming email, draft next steps from a Slack conversation, or respond to a pull-request change.

The release is available to Plus and Pro users on the web, iOS, and Android for the listed webhook workflows. Slack tasks require adding @ChatGPT to the monitored channel, and actions that need approval pause until a person reviews them.

Share a task without sharing your connected apps

Scheduled tasks can also be shared so another person can review and customize the instructions, connect their own apps, and create an independent copy. Free, Go, Plus, and Pro users can share tasks, but running a shared webhook task still depends on Work access and the recipient’s own connected app authorization.

Free users can create up to three active scheduled tasks. Free and Go users cannot create webhook-triggered tasks, so plan and capability differences matter when designing a team workflow.

Codex MCP server command is deprecated

OpenAI’s August 24 Codex release note says the codex mcp-server command is deprecated. The recommended replacement is the Codex app server. OpenAI also points Claude Code users to the Codex plugin for Claude Code when they want to use Codex from that environment.

Teams with scripts or development instructions that invoke codex mcp-server should inventory those integrations and plan a migration. The release note does not state a shutdown date, so this is a deprecation notice rather than a claim that the command has already stopped working.

Practical takeaway

The Work changes make scheduled automation more responsive, but they do not make approvals disappear: consequential actions still require review, and app access is tied to each user’s plan and authorization. The Codex change is a separate compatibility concern—update new integrations to the app-server path and keep the official migration guidance close to any existing setup instructions.

Sources

• OpenAI — “Release Notes” (Codex MCP server deprecation, August 24, 2026): https://openai.com/products/release-notes/
• OpenAI Help Center — “ChatGPT — Release Notes” (Work scheduled tasks, August 25, 2026): https://help.openai.com/en/articles/6825453-chatgpt-release-notes
• OpenAI Developers on X: https://x.com/OpenAIDevs