Skip to content
EverrunsEverruns

Fix ChatGPT plan sessions failing with HTTP 400

Changelog

Fix Platform Cloud FrameworkAPI

In 0.47.0

ChatGPT plan#4464

Sessions running on a ChatGPT plan connection could fail every model call with HTTP 400, because requests to the Codex backend carried metadata in the request body that it does not accept.

Everruns now leaves that metadata out of the request body while keeping the session HTTP header and host observability metadata. No configuration change is needed; existing ChatGPT connections work after upgrading.

See ChatGPT plan and #4464.