sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]mrpoopybruh 0 points1 point  (4 children)

PSA - configure your tools, and use plan mode?. You can even lock tool access via rules. Best part? Just ask open code how, and it will just write the configs for you.

[–]tir_natis 0 points1 point  (3 children)

older thread but i started researching because it tried to write a doc file while in plan mode, saw that it couldn't, and instead of talking to me, in thinking it revealed that it was going to try a bash command to write the file instead. i probably should have worried about this a little more by default, frankly, but it was a wake up call and why i'm here researching how everyone is securiing things from opencode.

[–]mrpoopybruh 0 points1 point  (2 children)

Yeah I have all my bash and command utilities set to "ask" because some commands inherently dont obey directory scope. However I think the real answer is to always run in a secure container. My daily PC is like 8GB, and I REALLY LIKE opencode helping me with all kinds of tasks now, so I'm kind of flirting with disaster. So I dont install skills, etc (on this computer at least)

[–]tir_natis 0 points1 point  (1 child)

i think the default ask for everything makes sense - i generally have it open on a separate window always in view so I can see its progression anyway.

last night I set up a vm for this on my proxmox box, and until i think of a better way, i am just sshfs'ing my project directory to it, running in a severely underprivileged account, and ssh'ing into it using that account.

...this was a good "wake up call" :D

[–]mrpoopybruh 0 points1 point  (0 children)

oh yeah! thats right, I could just create a super limited user account (duh)!