openai / openai/codex

codex can't complete a request

Open
#40,949 1 comment 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.149.1

What subscription do you have?

Enterprise

Which model were you using?

gpt-5.6-sol

What platform is your computer?

macOS

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

Terminal

Codex doctor report
codex doctor --json completed successfully.

  - Auth mode: chatgpt
  - ChatGPT tokens: present
  - API key: not stored
  - Overall status: warning
  - Codex CLI: 0.149.1 (current)
  - Network/auth connectivity: healthy

  It does not report your subscription tier, so this still can’t distinguish Free, Plus, Pro, Business, or Enterprise.

  Warnings were limited to CrowdStrike exclusions being unverified and a minor thread-history database mismatch.
What issue are you seeing?

Codex doesn't answer my question, instead it show below lines:

This content can't be shown
 We take extra caution with cybersecurity requests. If you’re a security professional, you may be able to apply for Trusted Access.
 Trusted Access: https://openai.com/form/enterprise-trusted-access-for-cyber/
 Learn more: https://help.openai.com/en/articles/20001326

What steps can reproduce the bug?

Uploaded thread: 01a03f4b-22c7-7653-8ec4-66dfaa3e9d49

What is the expected behavior?

Expected full answers to question.

Additional information

No response

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 01a03f4b-22c7-7653-8ec4-66dfaa3e9d49 and the codex doctor report. The issue names no source file, test, or reproducible question, so first determine whether the refusal is produced by the CLI or an upstream service; done means identifying a reproducible cause and an appropriate fix or confirmed service boundary.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
cli
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.