cd /news/ai-tools/breaking-openai-phase-is-no-longer-a… · home › topics › ai-tools › article
[ARTICLE · art-155654] src=driftwatch.et ↗ pub= topic=ai-tools verified=true sentiment=· neutral

OpenAI: phase is no longer accepted

OpenAI has removed the `phase` field from `DecisionInputMessage`, which is reachable from one OpenAI operation, according to the company's published API specification. Code that still sends `phase` will not be rejected; the field is now ignored, so calls succeed but behave subtly differently, and the change affects only code sending those DecisionInputMessage objects.

read1 min views1 publishedOct 22, 2026

What changed #

Usually ignored rather than rejected, so the call succeeds and does something subtly different.

Affects phase on DecisionInputMessage reachable from 1 operation. Grep for it: nothing else will tell you.

Who is affected #

Code that sends OpenAI's DecisionInputMessage objects, used by 1 OpenAI operation.

Before and after #

Where Before After
DecisionInputMessage.phase present absent

Code that breaks #

await client.post("/…", {
  // phase is now ignored, not rejected
  phase: value,
});

Based on OpenAI’s published API specification. How severity is decided.

── more in #ai-tools 4 stories · sorted by recency
── more on @openai 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
→ Live at https://your-agent.zahid.host ✓
Get free account → Pricing
from €0/mo · no card required
LIVE [news/breaking-openai-phas…] indexed:0 read:1min 2026-10-22 · —