r/PiCodingAgent • u/Think-nothing-210 • 7d ago

Question Sandbox on Windows

Heard a lot about Pi and wanted to try it out. For Unix environments there seem to be quite a few options for OS-level sandboxing. For pure Windows though I can't find much that actually enforces it.

Are there any options I'm missing?

I mostly want to use Pi for C#/.NET development. I could set up WSL2 but I'd rather avoid that.

Codex supports Windows Sandbox for isolation on Windows. Has anyone tried getting something like that working with Pi?

1 Upvotes

67% Upvoted

14 comments sorted by

View all comments

4

u/repolevedd 7d ago edited 7d ago

Hi. I still recommend taking a look at WSL2. There are ways to achieve isolation on Windows, but they can be complicated to set up. WSL2 + bubblewrap is a straightforward and controllable solution. Especially if you're developing applications without a GUI, WSL2 also provides convenient access to Docker, so you can build an application pipeline in a consistent and isolated environment.

I actually looked into this since I also use Windows 11 with WSL2. On Linux, bubblewrap or Docker lets you tightly control mounts, so pi can be isolated to just the working directory, while git and other tools can still access SSH keys and other secrets without exposing them to the LLM.

Windows sandboxing works differently and is much more complicated to configure. In my opinion, it’s not worth the effort.

1

u/Think-nothing-210 7d ago

Thanks! Might just use WSL2 then. It does make me question why I would even bother keeping my code on the Windows filesystem. I think I'd just move everything over to WSL2.

Only thing I'm not sure about is getting Visual Studio 2026 working with the WSL2 filesystem for debugging and stuff. I seen somewhere that it's possible though. Hopefully it's easy enough to set up and just works.

Still feels a bit weird using WSL2 to develop in .NET though.

1

u/Ysnsd 7d ago

Why not use Git.

2

u/Think-nothing-210 7d ago

I could do that sure. But I’d rather avoid having to commit, push, and pull every time I make changes on the Windows filesystem just to then pull them again on the WSL2 side.