Windows: Codex Security 0.1.24 Deep Scan blocked by disabled parent permission profile

Problem

Codex Security Deep Scan cannot start in a Windows desktop task. It rejects the parent permission profile before launching any scan workers, preventing the requested security review. Repeating the request in another desktop task also failed.

Related report: #38097. Additional reproduction evidence was previously posted at https://github.com/openai/codex/issues/38097#issuecomment-5618163383. This issue documents the current installation and diagnostics separately.

Environment

• Reproduced September 10, 2026
• Windows desktop, local project
• Installed Windows package: OpenAI.Codex 26.903.8094.0
• Codex Security plugin: 0.1.24
• Session record: permission_profile.type = "disabled"
• Session record: sandbox_policy.type = "danger-full-access"
• Session record: approval_policy = "never"

Steps to reproduce

1. Open a local project in Codex Desktop on Windows in a task with the permission state above.
2. Ask Codex to perform a deep security scan with agents, focusing on exposed keys, passwords, and vulnerabilities.
3. Codex invokes start_codex_security_deep_scan for the project with scope ".".
4. The tool immediately rejects startup.

Actual result

Exact error:

Deep Scan cannot safely start a read-only worker: the parent must provide a managed filesystem permission profile.

No scan workers start, and no source review, tests, or security findings are produced.

Diagnostic evidence

The installed plugin's resolveDeepWorkerParentSandbox function rejects missing profiles or profiles whose type is not "managed". It accepts an unrestricted filesystem when the enclosing profile is managed and the network value is valid.

An isolated test of the extracted original validation function, keeping filesystem access unrestricted and network enabled, produced:

The actual desktop session records show the disabled profile. This establishes the rejected condition but does not establish why the application selects it. The synthetic managed case passing this function does not prove that a complete scan would succeed.

No live permissions were changed, no metadata was forged in a real request, and no security check was bypassed.

Expected behavior / requested resolution

Please provide a supported Windows desktop path for launching Deep Scan with the required managed parent profile. If the current task's permission mode is unsupported, show actionable instructions identifying the exact setting and whether a new task or restart is required.

Please clarify whether this is an unsupported configuration or a desktop/plugin integration defect, and identify the fixed version or supported configuration if available. Full access being enabled does not satisfy the current validation, which is confusing for users who have already authorized the review.

Privacy

This report contains no project source, credentials, personal filesystem paths, or raw session logs.

Start by tracing the start_codex_security_deep_scan entry point and the resolveDeepWorkerParentSandbox validation described in the report, then compare the disabled and managed permission_profile cases. Done means establishing whether this is an unsupported Windows desktop configuration or a desktop/plugin integration defect, and documenting the exact supported setting, task or restart requirement, and fixed version if applicable.