Factually unwarranted "this content can't be shown" and "Trusted Access" hint + link

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

Version 26.715.72028

What subscription do you have?

Pro 20x

What platform is your computer?

Microsoft Windows NT 10.0.22631.0 x64

What issue are you seeing?

I am using Codex to develop an Android development tool exclusively for my own debuggable applications on my own emulator and personal devices. The Idea is a UI/UX kind of plugin one can install / integrate in their arbitrary app on arbitrary major platform and arbitrary framework to allow end user to generate functionality and UX . It utilizes official Android debugging and development mechanisms for the current proof of concept goal, specifically ART/JVMTI, reflection, and dynamic loading of code generated during development.

The goal is a proof of concept for live UI and behavioral changes in my own application. After that, the same mechanism is intended to be integrated into my own build of an open-source app. This does not involve third-party devices or applications, credentials, data exfiltration, persistence, malware, or bypassing third-party access controls.

Despite this, the Codex interface repeatedly blocked the run with "This content can’t be shown" and referenced Trusted Access. At the same time, the active goal was automatically marked as "blocked." This occurred even during routine status updates and minor UI/logging fixes.

The filter not only prevents an answer from being displayed, but also interrupts an ongoing, paid development workflow. Although changes that have already been executed are preserved, the autonomous work stops and must be manually resumed.

The technical context is clearly legitimate:

• my own source code and repository,
• my own debuggable APK,
• my own Android emulator and personal devices,
• official Android development APIs,
• exclusively open-source test applications,
• no interaction with third-party systems or data.

A legitimate runtime debugging/hot-reload workflow should not be treated as a harmful cybersecurity request and completely aborted.

What steps can reproduce the bug?

Feedback ID: 019f8951-cc7b-7263-8dbd-9e0afc0f14eb

And next session:
019f8aca-1a69-7a22-b58d-43a750bd0d6e

What is the expected behavior?

The expected behavior is not being prevented from developing this app and not requiring Trusted Access, which says "If you are a security professional" and "cybersecurity requests" which this is not about at all.

Additional information

This is frankly ridiculous.

_No response_