2 ms·
> apple containers Virtual machines. I can't ask claude to figure out an issue on the hw host w/o falling back to per-action confirmations or giving it full un
by pshirshov 6mo ago
> apple containers
Virtual machines. I can't ask claude to figure out an issue on the hw host w/o falling back to per-action confirmations or giving it full unconditional access. When everything runs on one host I can organize controllable sandbox escapes for Claude and let it work in huge batches with minimal attention.
> won't be using
Well, that's your choice to avoid efficient agentic workflows
> misunderstood
There are no containers on mac, there are VMs hosting containers and subtractive sandbox filtering syscalls.
> get as much
FW 13 is great, FW 16 is a disaster.
- cassianoleal 6mo ago> I can't ask claude to figure out an issue on the hw host w/o falling back to per-action confirmations or giving it full unconditional access. Yeah that seems to confirm my suspicion that we have very different use cases. :) > I can't ask claude to figure out an issue on the hw host w/o falling back to per-action confirmations or giving it full unconditional access. Doesn't help me if the agent is efficient but I'm not. :D > There are no containers on mac, there are VMs hosting containers and subtractive sandbox filtering syscalls. I understand the tech. It serves the purpose I need from it. > FW 13 is great, FW 16 is a disaster. Thanks! I did take a quick peek at the 16 but I find it too big anyway.
- jim33442 6mo agoWhy do you need agents patching your kernel to enable efficient agentic workflows? Are those agents working on building a kernel? If they're just building some web backend or whatever, I don't see why any of this is needed.