openai / openai/codex

Codex repeatedly requests security verification after authorization, interrupting work on Windows

Open
#43,291 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

What version of the Codex App are you using (From “About Codex” dialog)?

26.901.6511.0 (Windows x64)

What subscription do you have?

Plus

What platform is your computer?

Windows

What issue are you seeing?

While working on my Omnia project, Codex repeatedly stops to request security verification involving Daybreak, even though I have already completed the verification and authorized the requested work.

Codex does not appear to retain or recognize the previous authorization. This repeatedly interrupts the project and requires me to address the same security concern again.

What steps can reproduce the bug?

Feedback ID: 01a0783b-80eb-7322-a6e1-68bb7b695755

What is the expected behavior?

No response

Additional information

Codex should recognize completed verification and existing authorization for the same scope of work, and continue without repeatedly requesting the same confirmation.

If a separate security restriction still applies, Codex should clearly explain what remains blocked, why the previous verification does not resolve it, and the specific action needed to proceed.

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 Feedback ID 01a0783b-80eb-7322-a6e1-68bb7b695755 and investigate the Windows x64 security verification and authorization flow described for the Codex App. Reproduce the repeated Daybreak verification during work on the Omnia project; done means an existing authorization is recognized for the same scope, or any remaining restriction clearly explains the required action.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
authorization, desktop, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.