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.
Coop – Isolated VM Environments for Running Claude Code and Codex
11–20 of 23 posts
Re: Coop – Isolated VM Environments for Running Claude Code and Codex
#12Re: Coop – Isolated VM Environments for Running Claude Code and Codex
#13sidenote: 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
Re: Coop – Isolated VM Environments for Running Claude Code and Codex
#14sidenote: coop is also a large swedish grocery chain, pronounced the same way :) https://www.coop.se/
Re: Coop – Isolated VM Environments for Running Claude Code and Codex
#15Re: Coop – Isolated VM Environments for Running Claude Code and Codex
#16sidenote: 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
Re: Coop – Isolated VM Environments for Running Claude Code and Codex
#17Re: Coop – Isolated VM Environments for Running Claude Code and Codex
#18Re: Coop – Isolated VM Environments for Running Claude Code and Codex
#19Personally I am using Eclipse Enclave to sandbox my agents. Good to see another fully open source solution in Coop.
Re: Coop – Isolated VM Environments for Running Claude Code and Codex
#20Oh 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