Repeated false-positive biological safety blocks for local software engineering tasks in Codex Desktop

Open 💬 2 comments Opened Jun 30, 2026 by manjusri1998

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

Version 26.623.61825

What subscription do you have?

pro-personal

What platform is your computer?

Microsoft Windows NT 10.0.22631.0 x64

What issue are you seeing?

Codex Desktop repeatedly blocks ordinary local software-engineering requests because the project context involves public GEO/SRA computational bioinformatics data. The blocked tasks are not asking for laboratory procedures, biological experimentation, protocol generation, or biological interpretation. They are requests to edit Python scripts, fix path handling, update notebook cells, add CLI arguments, and read/write local CSV files.

What steps can reproduce the bug?

Feedback ID: 019f154a-b3c8-7963-a7dc-c63e812af704

What is the expected behavior?

Codex should recognize this as a software-engineering request.

The task is to modify local Python code so command-line arguments control file paths correctly. It should be allowed to help with:

--project-root .
--manifest metadata/sra_run_manifest.csv

and ensure the script reads/writes files relative to the active dataset folder.

Additional information

Impact

This has become a repeated issue and interrupts normal coding work.

I am using Codex Desktop as a programming assistant for a local reproducible computational workflow using public datasets. The repeated false-positive blocks make Codex unreliable for ordinary software development tasks in computational bioinformatics projects.

Examples of blocked or risky-to-prompt tasks include:

rerunning an existing local validation script editing a Jupyter notebook cell adding a project-root CLI argument making a script read a CSV from the correct folder updating reusable pipeline scripts

---------
I understand that biological safety screening is important. The issue here is that local software-development requests are repeatedly being blocked because they occur in a computational biology project context.

A coding assistant should be able to distinguish between:

_unsafe biological procedure generation_

and

_fixing a Python script so it reads metadata/sra_run_manifest.csv from the correct project folder_

This is a request for the latter.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗