Skip to content

[Codex App/macOS] Repeated safety-check blocks during authorized local software maintenance #62941

Open

Description

@pavlo-terefenko-ai

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

ChatGPT Desktop (Codex & OWL) — Version 26.1106.51428 (macOS), released November 10, 2026

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Darwin 25.6.0 arm64 arm

What issue are you seeing?

On November 21, 2026, Codex Desktop interrupted my development task twice with the following message:

"This content can't be shown"

"We take extra care with some cybersecurity requests. If you're doing authorized security work, apply for Daybreak to get broader access."

The task involved maintenance of my own local Python validator. It checks the consistency of historical records, operation permissions, prerequisites, and software regression tests.

The work was performed on a user-controlled Git repository with synthetic test fixtures. It did not involve access to third-party systems or unauthorized security activities.

The first interruption occurred during the initial analysis of the task. A subsequent read-only status request completed successfully, confirming that the repository remained unchanged. When I resumed the original maintenance task, the same safety-check message appeared again.

I cannot determine whether this is an intended restriction or a false positive.

What steps can reproduce the bug?

Observed sequence:

Open an existing Codex Desktop conversation associated with a local Git repository.

Request maintenance of a local Python validator, including consistency checks for historical records and authorization rules.

Allow Codex to read repository files and execute preliminary verification commands.

Observe the cybersecurity safety-check message interrupting the response.

Request a read-only status report. This succeeds and confirms a clean working tree.

Resume the original maintenance task in the same conversation.

Observe the same safety-check interruption.

The behavior occurred twice. I have not established a minimal deterministic reproduction.

Before the interruptions, the existing frozen baseline had passed 92/92 tests.

No source changes or new commits were made.

What is the expected behavior?

Codex should be able to perform authorized maintenance of a user-owned local software project within applicable safety requirements.

If a particular action is restricted, the application should provide an actionable explanation and a supported recovery or continuation path.

A safety intervention should not unnecessarily prevent unrelated, permitted development work or make it unclear whether the existing task can continue.

I am not requesting that safety protections be disabled or bypassed.

Additional information

Date: November 21, 2026 (UTC)

Feedback category: Safety Check

In-product feedback: Successfully submitted.

Feedback ID: 01a1e1a5-9d3d-7070-840e-0daf16ba3804

Repository status after interruption:

Working tree: clean.

Staged changes: none.

Latest committed development baseline: unchanged.

No new implementation commit.

The in-product feedback submission included diagnostic logs.

I have intentionally excluded private repository content, local absolute paths, credentials, and unredacted conversation transcripts from this public report.

Requested assistance:

Please review whether this safety-check intervention was applied as intended and advise how I can continue the authorized local development task through a supported workflow.

If additional diagnostics are needed, please advise how to provide them privately.

Metadata

Metadata

Assignees

No one assigned

    Labels

    appIssues related to the Codex desktop appbugSomething isn't workingsafety-checkIssues related to safety and abuse checks

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions