Remix.run Logo
▲ testtestmetest 13 hours ago

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..

▲ghosty141 13 hours ago | parent [-]

Like I wrote above I generally agree that the sandboxing should by enabled "by default" and should not be an extra opt-in that you have to know about first.

That being said I still believe this should be separated and composable at an application level and power users should be able to switch out the sandbox. This way you don't have to trust the harness since it doesn't know anything about the sandbox and can't modify it etc.