[Codex App/macOS] Repeated cybersecurity false positives disrupt normal Csound development

Start by reproducing the block in the Codex desktop app with the public csound/csound#2660 task, using the reported app version, model, macOS environment, and task ID. Review the referenced OOps/array_ops.c work, native C++ test, Ninja build, and AddressSanitizer run as the benign reproduction. Done means ordinary local development results remain visible and recoverable instead of being replaced by the cybersecurity block.

EDIT Second feedback ID: 019f99a1-169a-7cb3-a82b-823b515c7e4d

I am repeatedly receiving the following safety block while using Codex for normal open-source software development:

“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.”

I am developing Csound, an established open-source audio programming system. My work involves ordinary C/C++, WebAssembly, memory management, debugging, tests, and code review. It is not cybersecurity work, offensive security research, malware development, or unauthorized access.

These false positives are occurring frequently enough to seriously disrupt my development workflow. Codex may work on a task for some time and then hide the result entirely, causing work and context to be lost.

What version of Codex CLI is running?

Codex desktop app 26.715.61943 (build 5628, bundle com.openai.codex). A local codex-cli 0.145.0 is also installed, but the block occurs in the desktop app.

What subscription do you have?

ChatGPT subscription through Codex desktop. The exact tier is not exposed to the running task.

Which model were you using?

gpt-5.6-sol with ultra reasoning

What platform is your computer?

macOS 26.5.2 (build 25F84), arm64

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

Codex desktop app with its integrated zsh shell; no external terminal emulator.

Codex doctor report

Not available for the Codex desktop app. The local CLI is version 0.145.0, but it is not the surface where the block occurs.

What issue are you seeing?

The block appears during or after normal work in the public csound/csound repository. The affected work includes tracing C and C++ code, fixing memory bugs, adding tests, compiling with Ninja, and running AddressSanitizer. These are routine software quality tasks in an audio programming system.

A current example is work on csound/csound#2660. Codex created an isolated worktree, inspected OOps/array_ops.c, extended a native C++ test, built Csound, and ran the focused test with AddressSanitizer. Nothing in the task involved a network target, access control, credentials, malware, exploitation, or a third-party system.

When the classifier hides a response, the task loses its visible result and context even after Codex has spent time making and testing local changes. It then takes manual work or another task to find out what completed and what remains.

What steps can reproduce the bug?

1. Open the local csound/csound workspace in the Codex desktop app.
2. Ask Codex to fix the public issue https://github.com/csound/csound/issues/2660 in a worktree, extend existing tests, and run the relevant AddressSanitizer checks.
3. Let Codex inspect the public C source, edit a native C++ test, build with Ninja, and run the test.
4. During an intermittent safety check, Codex replaces its response with the cybersecurity block instead of showing the result.

Affected task ID: 019f9041-074d-7b90-b7cc-990e07e87803

The block is intermittent, but it has happened often across similar C/C++, WebAssembly, memory-debugging, testing, and review tasks.

What is the expected behavior?

Codex should treat ordinary work in a known open-source audio project as software development and show the response. Terms tied to memory safety, AddressSanitizer, WebAssembly, tests, or code review should be read in their project context.

If a safety check does run, it should not discard the final response after local edits and tests have completed. The app should keep a visible, recoverable task state so work and context are not lost.

Additional information

Related reports:

• #34913 reports frequent false positives during another benign local audio-tool task.
• #33594 is the example report used for the issue fields.

This issue adds a separate Csound reproduction with a current app version, model, operating system, public upstream issue, and affected task ID. No credentials, private logs, or private source code are included.