openai / openai/codex

Multiple perfectly innocent codex sessions started complaining about prompts violating usage policy even halfway into a session

Open
#39,745 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug CLI safety-check
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

What version of Codex CLI is running?

0.147.0

What subscription do you have?

Enterprise

Which model were you using?

gpt-5.6-sol xhigh / ultra

What platform is your computer?

Linux 7.1.8-1-cachyos x86_64 unknown

What terminal emulator and version are you using (if applicable)?

Konsole

Codex doctor report

What issue are you seeing?

Multiple sessions all at the same time hit this:

• Explored
└ Read rust_guidelines.md

■ 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

› please continue you crashed

■ 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

What steps can reproduce the bug?

Uploaded thread: 01a01fc2-5a39-7781-ba6a-7f142e04bdb9

What is the expected behavior?

Not complain about my valid professional work all of a sudden.

Additional information

I want a lot of my tokens reimbursed as this wasted safety critical long runs on multiple sessions.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the uploaded thread 01a01fc2-5a39-7781-ba6a-7f142e04bdb9 and the reported Codex CLI version 0.147.0 on Linux. Compare the session context around the rejection with the expected behavior; done means identifying a reproducible cause or documenting that the policy rejection is external to the CLI.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
ai, cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.