[Windows][Subagents] Private permission profile cannot be applied before child tool registration
Open 💬 1 comment Opened Aug 17, 2026 by haroldodesouzatavares1
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
Summary
Codex Desktop for Windows does not expose a supported mechanism to apply a dedicated private permission profile to a nested subagent before child initialization and tool registration.
Uploaded thread: 019fc81b-92d5-76b3-a3ea-28bf39df04d1
Environment
- Product: Codex Desktop for Windows
- Package:
OpenAI.Codex_26.810.7004.0_x64__2p2nqsd0c76g0 - Executable:
C:\Program Files\WindowsApps\OpenAI.Codex_26.810.7004.0_x64__2p2nqsd0c76g0\app\resources\codex.exe
- Parent agent:
analise_versoes_moto_snipe - Intended nested child:
route02_external_evidence_observer
Reproduction
- Define a dedicated child permission profile.
- Deny access to
C:\. - Deny
D:\by default. - Grant write access to only one dedicated directory on
D:\. - Keep the child scoped only to its parent and absent from the global agent registry.
- Attempt to start the nested child with the dedicated profile applied before tools are registered.
Actual behavior
Ordinary nested subagents inherit the parent task permission policy.
The attempted isolated fallback fails before the child is spawned:
Program 'codex.exe' failed to run: An error occurred trying to start process
'C:\Program Files\WindowsApps\OpenAI.Codex_26.810.7004.0_x64__2p2nqsd0c76g0\app\resources\codex.exe'
with working directory 'C:\Users\harol\Documents\Nelogica'. Acesso negado.
1 Comment
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action