You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
• Ran dotnet build Main/Main.sln
└ failed in sandbox: CSSM_ModuleLoad(): One or more parameters passed to a function were not
valid.
I get this output from codex
but somehow codex is able figure out a way to circulate this, but it always fail at first and try multiple times. I think it is a waste of token/compute, so filing a bug report here.
What is the expected behavior?
It should be able to run dotnet build
Or at least provide a clear instruction on what folder we need to whitelist in writable_roots to allow it to work
What do you see instead?
failed in sandbox: CSSM_ModuleLoad(): One or more parameters passed to a function were not
valid.
I just hit this myself and found it was basically unable to run any sort of dotnet test or benchmarks. Enabling "full access" temporarily was a workaround, but yeah, it'd be nice to know what was actually blocked so I could be more specific about it.
Something I noticed when working with Codex in VS Code was it needed full permissions because VS Test opens a socket to communicate back to the dotnet process and without full permissions it couldn't do that. Unclear if this is related. It's not the same error message, but it's the same end result - being unable to run tests.
Reacted by Tianqi Zhang, Serafín Martín and Sebastian Schubotz
Been trying out Codex while it's free because of the OS X App release. Turns out Codex is useless as a ASP.NET developer on Mac because of this bug. Good thing I didn't have to spend money on a subscription to find out.
Activity
feritzcan2 commentedon Dec 9, 2025
do anybody care about dotnet?
wewrere41 commentedon Feb 8, 2026
Same issue. Codex app - cli 0.98 macos
etraut-openai commentedon Feb 8, 2026
If someone in the community is interested in investigating this issue, we'd welcome a root cause analysis.
tillig commentedon Feb 11, 2026
I just hit this myself and found it was basically unable to run any sort of
dotnet testor benchmarks. Enabling "full access" temporarily was a workaround, but yeah, it'd be nice to know what was actually blocked so I could be more specific about it.Something I noticed when working with Codex in VS Code was it needed full permissions because VS Test opens a socket to communicate back to the
dotnetprocess and without full permissions it couldn't do that. Unclear if this is related. It's not the same error message, but it's the same end result - being unable to run tests.thomak-dev commentedon Feb 18, 2026
Been trying out Codex while it's free because of the OS X App release. Turns out Codex is useless as a ASP.NET developer on Mac because of this bug. Good thing I didn't have to spend money on a subscription to find out.