10 ms·
Why do people run and install these agents locally? No container nothing. I am running Opencode in WSL2 with the windows mounts disabled.
by k8sToGo 2mo ago
Why do people run and install these agents locally? No container nothing. I am running Opencode in WSL2 with the windows mounts disabled.
- butlike 2mo agoSo the idea is that these should be treated as programs in an extremely low trust environment, akin to running malware in a VM?
- jack_pp 2mo agoyes, this is basically experimental tech, if used with open source harnesses. if used with proprietary harnesses, treat as actual malware.
- advael 2mo agoI treat all proprietary software as malware, though of course the risk surface varies
- butlike 2mo agoI never thought about it in that extreme, but just today the google results ai gave me conflicting information from one search to another. Maybe I should start. P.S. the conflicting information was Keith Richard's age. One search said he was 37 Dec 18 1981, the other said he was 37 in 1980.
- k8sToGo 2mo agoTechnically open source harness like opencode is more "malwarey" than claude code for example because its default permissions are very open.
- arandomhuman 2mo agoI disagree with this, Claude code does many malware like things and has its source obfuscation. Plan mode doesn’t even work.
- Demiurge 2mo agoYes, I think if agents as interns with enough smarts to be dangerous.
- denysvitali 2mo agoSame reason one uses VSCode locally
- Anon1096 2mo agoIf the agent you are running really wanted to it could easily find a way to mount the windows folders and read them all. WSL isn't a security boundary, you are only barely more protected than people running grok in their home directory.
- k8sToGo 2mo agoit is not about "security" but it is more about confinement. And how could it do that without sudo rights?
- arandomhuman 2mo agoStill, you are barely more protected than someone running this as non root at home. By your same logic you could “confine” the agent to any arbitrary directory on your filesystem and say it’s sufficient.
- k8sToGo 2mo agoYes, that is exactly the point I am making. The agent / cli is confined within the WSL2 environment. How is it "barley" protected? Neither you nor the other guy have yet answered this question. I never claimed WSL2 is a security sandbox. I am saying running it in a container or WSL2 allows you to severly limit the blast radius. I am not expecting the agent to be malicious, but I am expecting it to do unexpected things.
- arandomhuman 2mo agoThat’s a fair approach, thanks for elaborating. I think the main point of contention is there is an expectation this software should be more reliable, that doesn’t take away from your approach, running close sourced software like a harness (or operating system) is asking for problems.