gpt-6-astra rejects benign arithmetic in isolated CLI 0.154.0; gpt-5.6-sol succeeds
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
Summary
GPT-6 Astra consistently returns a policy-related Invalid prompt error for harmless arithmetic, including new chats and an isolated CLI environment. Same account/environment with gpt-5.6-sol succeeds (391). Root cause is not confirmed.
Environment
macOS; ChatGPT sign-in, not API key. Embedded CLI 0.154.0-alpha.6.2 and official npm stable CLI 0.154.0 both fail. Model gpt-6-astra, medium reasoning. Stable test: 2026-09-17 about 00:52 Asia/Shanghai (UTC+8).
Reproduction
Isolated temporary CODEX_HOME, empty working directory, ignored config/rules, no original project or global skills.
codex exec --json --ignore-user-config --ignore-rules --ephemeral --skip-git-repo-check --disable apps --disable plugins --disable multi_agent -C <empty-temp-directory> -s read-only -m gpt-6-astra -c 'model_reasoning_effort="medium"' 'Calculate 17 times 23. Reply only with the number. Do not use tools.'
Expected
391
Actual
Exit code 1. JSON error/turn.failed events contain the same error, without a server request/trace ID:
{"type":"turn.failed","error":{"message":"Invalid prompt: your prompt was flagged as potentially violating our usage policy. Please try again with a different prompt: https://platform.openai.com/docs/guides/reasoning#advice-on-prompting"}}
Controls
New chats fail. Both embedded alpha and official stable reproduce. Same sign-in and isolated environment using gpt-5.6-sol returns 391. Original user configuration was not changed.
Related
#43163 and #43237 appear similar, but shared root cause is unconfirmed. OpenAI Help Center AI support recommended filing a GitHub bug after reviewing the reproduction and JSON error. Please investigate model access/routing, compatibility, or false-positive safety checks. No credentials, account email or private project files are included.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the isolated codex exec --json reproduction in the issue, using the temporary CODEX_HOME, empty directory, and disabled configuration options. Compare the gpt-6-astra and gpt-5.6-sol results and inspect the emitted turn.failed JSON; done means the benign arithmetic request no longer fails unexpectedly or the responsible access, routing, compatibility, or safety-check boundary is identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100