Codex Security Deep Scan fails to start on Windows: parent must provide a managed filesystem permission profile

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

Codex App version: 26.803.81509

What subscription do you have?

plus

What platform is your computer?

"$([Environment]::OSVersion | ForEach-Object VersionString) $(if ([Environment]::Is64BitOperatingSystem) { "x64" } else { "x86" })"

What issue are you seeing?

Codex Security Deep Scan cannot start on Windows because the Deep Scan worker fails the filesystem permission preflight.

The exact MCP error is:

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

I am using Codex Desktop on Windows as a personal user.

The repository is trusted and Windows Elevated Sandbox is enabled.

What steps can reproduce the bug?

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

I also tried explicitly configuring a managed filesystem profile:

default_permissions = "security-readonly"

[permissions.security-readonly.filesystem]
":minimal" = "read"
":workspace_roots" = "read"

[permissions.security-readonly.network]
enabled = false

What is the expected behavior?

Codex Security Deep Scan should automatically receive or derive a valid managed read-only filesystem permission profile from the parent Codex Desktop session on Windows.

A trusted repository running under the supported Windows sandbox should be sufficient for Deep Scan to create its read-only workers without requiring undocumented manual permission-profile configuration.

If additional configuration is required, the preflight should provide the exact supported config.toml keys and values needed for Windows.

Additional information

Windows Elevated Sandbox itself was installed and Codex Desktop launches successfully.

I previously encountered an Elevated Sandbox setup loop, but after resolving the sandbox setup state, Codex Desktop itself works normally.

This issue is specifically with Codex Security Deep Scan worker startup.

The behavior suggests a mismatch between the filesystem permission profile expected by Deep Scan and the permission profile exposed by Codex Desktop on Windows.

Relevant Codex App runtime information:

• Codex App version: 26.803.81509
• Windows sandbox: elevated
• Repository: local Windows drive
• Repository trust level: trusted
• Codex Security plugin: enabled
• Deep Scan discovery never starts
• No scan results are generated

It would be helpful to clarify:

1. What managed filesystem permission profile Deep Scan expects on Windows.
2. Whether Codex Desktop is supposed to create/pass this profile automatically.
3. Whether default_permissions is required for Deep Scan.
4. Which filesystem tokens are officially supported for the Deep Scan parent profile.
5. Whether this is currently a Windows-specific Codex Desktop bug.

Reproduce Deep Scan startup on Windows with the supplied security-readonly config.toml profile, then trace the filesystem permission preflight and parent worker setup. Done means the read-only worker starts under a trusted elevated-sandbox session, or the preflight clearly identifies the supported configuration and failure cause.