| ▲ | zaptheimpaler 19 hours ago | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
They're totally right to not bother with security inside a harness, its just a terrible approach that creates permission fatigue and bad UX. Claude asking me to approve a 50 line arcane bash command doesn't help at all. Pi also has the same philosophy of not enforcing security within the harness. Security should be enforced outside the harness with a sandbox. You can define what's allowed and what's not in one place and have strong enforcement guarantees instead of ad-hoc permission requests every minute. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ▲ | neobrain 16 hours ago | parent | next [-] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> Security should be enforced outside the harness with a sandbox. You can define what's allowed and what's not in one place and have strong enforcement guarantees instead of ad-hoc permission requests every minute. I agree in principle, but in practice most sandboxing technology (like bwrap) is too static for this use case: You grant access once during startup and can't extend/revoke without a restart. That's inconvenient when you realize halfway through your session that you need additional permissions, and it's insufficient for permissions that are only briefly needed (for the duration of one tool call). A harness that controls the sandbox (e.g. for each individual tool invocation) can manage this much more effectively. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ▲ | rpunkfu 18 hours ago | parent | prev | next [-] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Security when calling external services is much more than just FS permissions, sandbox doesn’t protect at all what you push to github or call API with | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ▲ | CyberShadow 14 hours ago | parent | prev | next [-] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
OpenCode's security problems are not limited to just permissioning agent actions. For a long time, simply starting OpenCode, and without requiring any other actions or prior configuration, allowed any website to run any code on your computer without any restrictions. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ▲ | DanielHB 17 hours ago | parent | prev | next [-] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Yeah I came to the same conclusion, I migrated to run harnesses and my projects inside a container. However some kinds of development are really hard to run inside a container (like native mobile development or 3d game engines). I have even been running my IDE in server/client mode with the server inside the container too (because of malicious extensions). | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ▲ | trollbridge 13 hours ago | parent | prev | next [-] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
100%. I have my agent request permissions for things like a Cloudflare API key (or I guide it or just come up with the request myself). These go in a simple queue, with justifications. I review them and then have another agent with far more permissions create the tokens, with expiry and so on, and then hand the API tokens back. The original agent doesn’t even run as my main user; it sits on a computer in a restricted account (easy to do with either macOS or Linux, or even Windows these days). It has taken some rather long prompts to get it to self-report on itself when it tries to workaround. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ▲ | testtestmetest 14 hours ago | parent | prev | next [-] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
I dont want it doing damage to the sanbox either. I have half a dozen sandboxes running 24/7, there's definately a balance. My sandbox can't say dont run python for this type of task or similar conditional permissions. There are gaurdrails that the harness should handle well. Also the harness should definately just have a solid permission structure for the average user that 1000% is not using a sandbox, most people I know naively do not and think these things are perfectly safe. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ▲ | californical 17 hours ago | parent | prev | next [-] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Even better, just limit what the agent can access. Don’t give it bash, give it the exact collection of tools you want it to be able to use. Limit it, it still works totally fine without full bash access. I gave my harness access to everything it needs through tool calls to specifically scoped actions and it works great | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ▲ | hsaliak 16 hours ago | parent | prev | next [-] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
this is ultimately the right approach. You are going to get more mileage by giving your agent a specific set of tools and operations it can freely access and restrict the rest. Ive also found that any dynamic rejections pollute the context and may lead the agent to go find worse workarounds. Put your agent in a restricted but fixed environment, and let it do its task. Anything else is mostly theatre and token burn. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ▲ | hendersoon 15 hours ago | parent | prev [-] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Wrong. This is largely a solved problem with “auto review” permissions mode, which uses another LLM to review all tool calls that could potentially be dangerous. That solution isn’t perfect of course but it is reliable and usable at the point. This is available in Claude code, codex, copilot, and a bunch of others. I find auto review mode mandatory and refuse to consider any harness that doesn’t support it. Opencode doesn’t support it. And there are no good plugins to do it either, the most popular had only six stars last I checked. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||