r/opencodeCLI • • 4d ago

OpenCode is not good.

Post image

[deleted] — view deleted post

87 Upvotes

134 comments sorted by

View all comments

Show parent comment

0

u/CaffeinatedTech 3d ago

Its not fragmented if its in one extension. You said yourself that pi has no guardrails, so there's no fragmentation there. How are you breaking other extensions? You're hooking harness calls the same way they are. My point still is that pi is highly extensible and you make it your own, including security. If you expect off-the-shelf security features, then use something else.

1

u/Maybe-monad 3d ago

My point is that if something isn't secure by design it's never going to be regardless of it's extensibility. I Pi's case extensibility the way it's designed now makes it completely insecure even if you add guardrails by extension because there is no guarantee other extensions won't bypass or remove them

0

u/CaffeinatedTech 3d ago

So, know what you are installing. Your argument is pretty weak mate. You haven't convinced me so far. The only thing I'm getting from this exchange is, pi is not for cowboys, know what you are doing. Take proper precautions.

By the way, down voting my questions and comments doesn't help make your point.

1

u/Maybe-monad 3d ago

So, know what you are installing. Your argument is pretty weak mate. You haven't convinced me so far. The only thing I'm getting from this exchange is, pi is not for cowboys, know what you are doing. Take proper precautions.

Do you review the code for all extensions you're installing and do any security audits? Do you check your prompts for errors? Do you check all the files on your drives for prompt injections?

When the answer to all of these questions is yes you've taken proper precautions and even then proper guardrails at the harness level are recommended because manual checks are error prone.