OpenAI
Updates

The change desk · Edition 001

What changed.
What it means.

A clearer view of OpenAI. Selected changes, who they affect, and a useful next move—without treating an announcement as a promise of access.

The short brief

Three things worth your attention.

This edition’s priorities, not another copy of every announcement.

  1. Agents API enters public beta

    A managed harness is an architectural choice, not simply a model-name replacement.

  2. Project API keys can have expiration dates

    A credential can stop working even when application code is unchanged.

  3. The standalone Codex MCP server has been removed

    Launching the removed command can break an integration; ordinary external MCP connections are a different case.

5 selected changes

How we select and verify ↓
Announcement datePublic beta

API & models

Agents API enters public beta

OpenAI introduced a managed agent harness with durable sessions and hosted or connected sandboxes.

Who it affects
Developers building agent-powered applications.
Access & limits
Public beta; verify account access and supported environments.

Our take / your next move

A managed harness is an architectural choice, not simply a model-name replacement. Prototype one bounded task. Check recovery, permissions and costs before committing an existing workflow.

Official evidence & review date

Source checked 11 September 2026 UTC. No independent rollout or account test. Earlier launch conditions may have changed.

Put this in context →Product directory ↗
Announcement dateAdmin control

API & models / Business & admins

Project API keys can have expiration dates

New project keys can expire; administrators can set maximum lifetimes at organization or project level.

Who it affects
API administrators and teams maintaining integrations.
Access & limits
Check the controls available in your Platform settings.

Our take / your next move

A credential can stop working even when application code is unchanged. Inventory owners and renewal procedures. Test replacement credentials safely; do not revoke working keys without a migration plan.

Official evidence & review date

Source checked 11 September 2026 UTC. No independent rollout or account test. Earlier launch conditions may have changed.

Put this in context →Product directory ↗
Announcement dateGenerally available

API & models

Cache diagnostics make misses easier to investigate

Responses API cache diagnostics are generally available for GPT-5.6 and later supported models.

Who it affects
Developers investigating inconsistent prompt-cache reuse.
Access & limits
Model support matters; this is not a ChatGPT subscription setting.

Our take / your next move

A cache miss needs diagnosis before it needs a bigger infrastructure change. Compare a representative miss with a previous response. Change one input variable at a time and measure the next run.

Official evidence & review date

Source checked 11 September 2026 UTC. No independent rollout or account test. Earlier launch conditions may have changed.

Put this in context →Product directory ↗
Announcement dateBreaking change

Codex

The standalone Codex MCP server has been removed

The codex mcp-server command and codex-mcp-server binary were removed after their August deprecation.

Who it affects
Developers whose integrations launch Codex as an MCP server.
Access & limits
External MCP connections through codex mcp remain supported. The suggested app-server alternative is experimental, not production-supported.

Our take / your next move

Launching the removed command can break an integration; ordinary external MCP connections are a different case. Inspect your launch configuration before upgrading. Evaluate the documented migration and its experimental status.

Official evidence & review date

Source checked 11 September 2026 UTC. No independent rollout or account test. Earlier launch conditions may have changed.

Put this in context →Product directory ↗
Announcement datePreview at announcement

ChatGPT & work / Business & admins

Sites preview opened a hosted website workflow

OpenAI announced Sites preview in the Codex app, with Business inclusion and Enterprise role-based enablement.

Who it affects
Teams considering OpenAI-hosted websites and internal tools.
Access & limits
Historical launch entry. Confirm current workspace access; this is not a live availability check.

Our take / your next move

Generating a website and authorizing its publication are separate decisions. Start with a non-sensitive draft. Review hosting, access and data handling before publishing or connecting business information.

Official evidence & review date

Source checked 11 September 2026 UTC. No independent rollout or account test. Earlier launch conditions may have changed.

Put this in context →Product directory ↗

Selection is part of the service.

We select changes with a practical consequence: a new workflow, an access condition, an integration risk, or an action to consider. This first edition is a bounded selection, not comprehensive coverage or a live status monitor. It includes an older Sites announcement for business-workflow context.

Announcement dates come from the linked official changelogs. The review date tells you when we checked them—not when a feature reached your account. Our interpretation is labeled separately from the source facts. Before acting, check the latest official guidance and your workspace settings.

Corrections should amend the existing entry with a dated note. Evergreen instructions belong in the decision guide or file-capability record; the history keeps its own historical scope.

By OpenAI Updates Editorial Desk · Source review: OpenAI Updates Verification Desk · Reviewed UTC.
Produced with AI assistance under editorial role aliases, not human credentials. Recommendations are our interpretation; account access is not independently verified.