You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
GPT-6 Astra rejects harmless prompts and falls back to GPT-5.6 Sol #44700
I can reproduce this on macOS with the same Codex account:
GPT-6 Astra fails consistently, including a harmless 2–6 character prompt, with: Invalid prompt: your prompt was flagged as potentially violating our usage policy.
GPT-5.6 Sol accepts the identical prompt and environment and returns normally.
On Codex App 26.903.71938 / bundled CLI 0.153.4, the Astra turn ends with codex_error_info: "other" and no assistant/output item in the local session record, while the Sol control run produces a normal assistant message.
The test was repeated in a fresh temporary working directory, so it does not appear to depend on project context or prompt content.
This looks like an Astra-specific failure before model output (possibly session/turn initialization or gateway validation), with a misleading generic invalid_prompt message.
Follow-up diagnostic: with the current Codex App 26.908.40834 / bundled CLI 0.154.0-alpha.6.2, a clean temporary CODEX_HOME, an empty workdir, and --ignore-user-config, GPT-6 Astra still fails on hi while GPT-5.6 Sol succeeds. The authenticated direct backend request also reaches response.in_progress and then returns SSE invalid_prompt / response.failed for Astra, while the identical Sol request completes. This is not a local project/configuration or capacity issue. Detailed transport evidence and request IDs are in my follow-up on #43237: #43237 (comment)
Activity
github-actions commentedon Sep 11, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
freanocank commentedon Sep 12, 2026
I can reproduce this on macOS with the same Codex account:
Invalid prompt: your prompt was flagged as potentially violating our usage policy.codex_error_info: "other"and no assistant/output item in the local session record, while the Sol control run produces a normal assistant message.This looks like an Astra-specific failure before model output (possibly session/turn initialization or gateway validation), with a misleading generic
invalid_promptmessage.freanocank commentedon Sep 12, 2026
Follow-up diagnostic: with the current Codex App 26.908.40834 / bundled CLI 0.154.0-alpha.6.2, a clean temporary CODEX_HOME, an empty workdir, and
--ignore-user-config, GPT-6 Astra still fails onhiwhile GPT-5.6 Sol succeeds. The authenticated direct backend request also reachesresponse.in_progressand then returns SSEinvalid_prompt/response.failedfor Astra, while the identical Sol request completes. This is not a local project/configuration or capacity issue. Detailed transport evidence and request IDs are in my follow-up on #43237: #43237 (comment)