Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Coop – Isolated VM Environments for Running Claude Code and Codex

github.com

Post reply on HN
Print view View original

1–10 of 23 posts

Re: Coop – Isolated VM Environments for Running Claude Code and Codex

#3

Post by darkamaul »

I use coop daily and found it super convenient for my use case (ie letting agents go on with no access to my other projects or personal files)

I would recommend anyone that has desire to provide stricter boundaries to agents to give it a try - while remembering that a motivated agent would probably be able to escape it :)

Re: Coop – Isolated VM Environments for Running Claude Code and Codex

#5

Post by 3stacks »

Oh awesome, I just started building something like this but nice to use something off the shelf for once.

I used a project called toolgate to autoapprove "safe" tool calls but request permission on riskier calls declaratively. But there's so many unnecessary tool permission requests

Re: Coop – Isolated VM Environments for Running Claude Code and Codex

#9

Post by darkamaul »

compiotr wrote: post #7

How is this different from docker sbx or microsandbox.dev? Not saying we don't need more alternatives, just asking to see if there is a reason to switch.

I _think_ (disclaimer: I have only read the documention of the two tools) they overlap quite a bit. The main idea is to get VM isolation for your agents env.

Re: Coop – Isolated VM Environments for Running Claude Code and Codex

#10

Post by wolfi1 »

vladde wrote: post #6

sidenote: coop is also a large swedish grocery chain, pronounced the same way :) https://www.coop.se/

not only in Sweden, in Germany and Switzerland as well. I guess it has the same origins in the trade unionist purchasing cooperatives at the turn of the century from the 19th to the 20th
Post reply on HN