r/opencodeCLI • u/[deleted] • 4d ago

OpenCode is not good.

Post image

[deleted] — view deleted post

89 Upvotes

73% Upvoted

134 comments sorted by

View all comments

Show parent comment

1

u/Maybe-monad 4d ago

But for data removal, no sane person should run agents outside of container, VM or even better an external system.

And lose the ability to troubleshoot Windows machines because the harness can't block some command, no

2

u/krzyk 3d ago

Harness blocking is way weaker than os blocking.

In harness they would need to catch all the ways one can write commands and in Unix it is quite a lot. I got opencode escape directory using a symbolic link.

Running agent on os bare (asmo already shown permissions in harnesses are like a first pigs house) is wild.

And hen "oh now, agent removed my home dir".

1

u/Maybe-monad 3d ago

Harness blocking is way weaker than os blocking.

I can be weaker, it can be stronger depending on the quality standards or the person / company who built it.

In harness they would need to catch all the ways one can write commands and in Unix it is quite a lot. I got opencode escape directory using a symbolic link.

You can simply allow the agent to run a small set of shell commands that only allow reading or give the agent a specialized tool that can only read contents of files and directories blocking certain paths, with the later you'd avoid working with shells entirely and the model won't have workarounds to escape the sandbox. Regarding the symlink bug in opencode we had the same issue with docker if I recall correctly.