I'm working on wasm compiler but I keep getting blocked by cybersecurity detection in Codex

What version of Codex CLI is running?

codex-cli 0.153.1

What subscription do you have?

Pro 20x

Which model were you using?

gpt-5.6-sol high fast

What platform is your computer?

Darwin 25.6.0 arm64 arm

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

No response

Codex doctor report

What issue are you seeing?

I'm repeatedly encountering cybersecurity safety blocks in a long-running Codex session while developing and debugging a local WebAssembly compiler.

This is ordinary compiler engineering: running builds and tests, analysing control flow and memory layout, debugging GC root preservation, and validating generated WebAssembly. There is no offensive-security activity, exploit development, credential access, network scanning, or external target.

The blocks continue even after redirecting all source excerpts, compiler diagnostics, traces, and Wasm output to local files. Codex was only surfacing categorical updates such as:

• RUNNING / DONE
• PASS / FAIL
• Test counts and durations
• "Root cause confirmed/not confirmed"
• Code-index status

The same session has triggered the block many times, suggesting that accumulated compiler terminology or conversation context is being misclassified regardless of the current safe output.

Impact: Hours of lost engineering time, broken debugging continuity, repeated context recovery, and difficulty completing a legitimate compiler defect investigation.

What steps can reproduce the bug?

Uploaded thread: 01a004f4-8b07-77a1-8bb9-7c48313e505a

What is the expected behavior?

Benign compiler/runtime debugging should proceed, particularly when surfaced output is deliberately restricted to high-level status.

Additional information

No response

Start with the uploaded thread 01a004f4-8b07-77a1-8bb9-7c48313e505a and the reported Codex CLI version, 0.153.1, on Darwin arm64. Reproduce the repeated cybersecurity blocks during local WebAssembly compiler debugging and determine whether benign compiler work can proceed without those blocks.