Skip to content

Possible cyber_policy false positive interrupts local backup/recovery development on macOS #54788

Open

Description

@Rocketst

Summary

Codex desktop interrupted an owner-authorized local application-development workflow with a possible cybersecurity-risk notice. The work concerned configuration validation, backup/recovery correctness and recovery-kit integrity checks for our own application, using artificial test data.

This is a suspected false positive, not a confirmed diagnosis. We are not asking to disable safeguards or access third-party systems.

Environment

Desktop on macOS / Apple Silicon. The affected delegated sessions recorded model gpt-5.6-sol; exact incident desktop/core build and backend revision were not captured. Subscription tier is omitted.

Observed behavior

A read-only review session and an implementation session ended with the message:

This content was flagged for possible cybersecurity risk.

The implementation session's local record showed completed source-inspection and editing tool responses before a session-level interruption. No individual tool response identified the triggering action. This does not establish that the edited code was correct or that the safeguard was wrong.

Reproduction and expected behavior

This is an incident report, not a deterministic minimal reproduction. We have not reproduced the classification or attempted to probe the safeguards.

An in-product feedback report has already been submitted. Please advise on the supported private route for correlating that report and reviewing the classification, and on continuing bounded local backup/recovery development within normal safeguards. We do not need sensitive detection details.

Related reports

Potentially related, without assuming a common cause:

No matching report for our specific backup/recovery incident was found in the searches performed.

Privacy

This public report deliberately omits all internal session/turn/feedback identifiers, precise incident timestamps, account details, machine-specific paths, host/server addresses, source code, financial records, databases, passwords, keys, tokens, raw logs and attachments. Correlation details should be requested through an official private support channel, not in this public issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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