Custom sandboxing #4667

Activity

1. o1lo01ol1o

   added

   enhancementNew feature or requestNew feature or request

   on Oct 3, 2025
2. github-actions commented on Oct 3, 2025

   

   github-actionsBot

   on Oct 3, 2025 – with GitHub Actions

   Contributor

   More actions

   Potential duplicates detected:

   • Project-specific mcp servers #4658

   Powered by Codex Action
3. Meowzz95 commented on Oct 4, 2025

   

   Meowzz95

   on Oct 4, 2025

   More actions

   Are you looking for
   https://github.com/openai/codex/blob/main/docs/config.md#sandbox_mode

   search for writable_roots
4. o1lo01ol1o commented on Oct 4, 2025

   

   o1lo01ol1o

   on Oct 4, 2025

   Last edited by o1lo01ol1o

   Author

   More actions

   @Meowzz95 No, my issue is that nix-shell or the equivalent will load a shell with all my tools for the given project. if I launch codex, codex does not have access to that shell. Codex is not allowed to invoke that shell and, though nix is fast all things considered, it should not reload the shell every time it needs to check the compiler output.

   the shell policy should default to all but apparently codex does not take the ambient PATH at execution because it doesn't have any of the tools, including nix-shell:

   • Ran cabal test tests
     └ Error: cabal: Could not resolve dependencies:
       [__0] trying: foo-0.1 (user goal)
       … +7 lines
       goals I've had most trouble fulfilling: base, snap-stream, foo
   
   • Ran nix-shell --command 'cabal test tests'
     └ bash: line 1: nix-shell: command not found
   
   > nix-shell isn’t available in this environment (command not found), so the combined command can’t run. If you have Nix installed elsewhere, you could
     invoke the same command there; otherwise we’ll need another way to get the right GHC/base version.
   

   This policy might be able to do something if I could populate it from the given path during the nix shell evaluation:

   [shell_environment_policy]
   inherit = "all"
   set = { PATH = "$NIX_SHELL_PATH" }

   But that's already a bit more janky then just passing through the PATH to codex
5. etraut-openai

   added

   sandboxIssues related to permissions or sandboxingIssues related to permissions or sandboxing

   on Nov 14, 2025
6. etraut-openai commented on Dec 18, 2025

   

   etraut-openai

   on Dec 18, 2025

   Contributor

   More actions

   This feature request hasn't received any upvotes or additional posts in over two months, so I'm going to close it out.
7. etraut-openai

   closed this as not plannedon Dec 18, 2025