| ▲ | testtestmetest 14 hours ago | ||||||||||||||||
You really wanting handle this at the sanbox layer? I have 100 different containers configurations, only a few differnet harness configurations. You're just being stubborn, the best UX is through the harness. Most users dont even know how to configure a sandbox properly and dont even use one. Ive known quite a few naive people that have gotten their home directories wiped and really gotten burned. Many users of these products dont even know how to use a terminal and these harness companies are marketing to the average joe. | |||||||||||||||||
| ▲ | krzyk 13 hours ago | parent | next [-] | ||||||||||||||||
> Most users dont even know how to configure a sandbox properly and dont even use one. This is their problem. But running and screaming "ai deleted my database" is all on them, not on LLM. | |||||||||||||||||
| ▲ | ghosty141 14 hours ago | parent | prev | next [-] | ||||||||||||||||
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. | |||||||||||||||||
| |||||||||||||||||
| ▲ | whoanoway 13 hours ago | parent | prev [-] | ||||||||||||||||
[dead] | |||||||||||||||||