| ▲ | ghosty141 14 hours ago | |||||||
I have a sandbox script and a simple wrapper that runs any command in that sandbox thus that "pi" -> without sandbox, "pisb" -> pi in the sandbox. I practically only use pisb. This separation doesn't mean it must result in bad UX. It just needs somebody to make a nice UI/TUI to configure the sandbox and when running that it does its setup and open whatever command you want. The problem with the harness doing sandboxing is that from my experience the simply break all the time leading to users ignoring properly configuring it and using abominations like codex' `Approve for me` where IT ASKS A SEPARATE AI and not the user. | ||||||||
| ▲ | testtestmetest 13 hours ago | parent [-] | |||||||
My main issue is these are being marketed to average joes. You wont see anything on these harnesses documentation, opencode et al, who say it should be used in a sandbox. The people making them, opencode et al, scream everyday about how you're holding yourself back by using permissions without a single mention of sandbox. Hundreds of thousands of people are using them naively, if they shipped with common sense strictish permissions instead of none at all, like what opencode opted to do it would be safer for everyone. Its much easier for a normal non programmer to configure a simple config file than it is for them to learn how to properly setup a container/vm, they will just not do the latter 9/10. Honestly, a harness should always install heavily gaurded, remember when Grok code/build was instantly indexing your home directory and sending it back to HQ on the first request it made.. | ||||||||
| ||||||||