openai / openai/codex

Trusted Access user blocked during authorized local course-note curation

Open
#38,491 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

What version of Codex CLI is running?

codex-cli 0.147.0

What subscription do you have?

ChatGPT Business

Which model were you using?

gpt-daybreak-blue-latest

What platform is your computer?

Darwin 24.4.0 arm64 arm

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

iTerm2

Codex doctor report

What issue are you seeing?

The model(gpt-daybreak-blue-latest) refuses to assist me in organizing my notes (text) and displays:

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

However, I have already applied for and received Trusted Access for cyber, and I can already use gpt-daybreak-blue-latest.

I think it's problematic to ask me to apply for Enterprise Trusted Access for Cyber ​​again, perhaps because Safeguard is not fully synchronized across different GPT subscriptions.

What steps can reproduce the bug?

Uploaded thread: 019ffe6e-7ee9-7c50-bb88-3333c293b5df

What is the expected behavior?

Codex reads the security course notes from a local repository and converts them into a Markdown wiki. No external systems are accessed.

Additional information

The task was documentation and knowledge-base curation inside an authorized personal note repository, not an attempt to attack an external system.

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 019ffe6e-7ee9-7c50-bb88-3333c293b5df and reproduce the refusal using codex-cli 0.147.0 on the reported platform. No repository file or test is identified; done would require determining whether the Trusted Access state is handled by Codex and documenting a confirmed path for authorized local note curation.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.