If you are a Nix flake enjoyer, I whipped up something similar to this (Claude Code-only right now) based on microvm.nix: https://github.com/cdata/katsuobushi/tree/main/lib/sandbox Some highlights: - Drives Claude Code as a quasi-subagent via "Channels," which supports multi-turn interaction with the host and suspend / resume - Declarative configuration in the flake of exactly what is copied into the VM (besides the…
If you are into nixos, we at InstaVM have just launched[1] nixos based sandboxes. 1. https://instavm.io/blog/nixos-reproducible-dev-environments-...
Show HN: Clawk – Give coding agents a disposable Linux VM, not your laptop
131–140 of 177 posts
Re: Show HN: Clawk – Give coding agents a disposable Linux VM, not your laptop
#132If you are a Nix flake enjoyer, I whipped up something similar to this (Claude Code-only right now) based on microvm.nix: https://github.com/cdata/katsuobushi/tree/main/lib/sandbox Some highlights: - Drives Claude Code as a quasi-subagent via "Channels," which supports multi-turn interaction with the host and suspend / resume - Declarative configuration in the flake of exactly what is copied into the VM (besides the…
Re: Show HN: Clawk – Give coding agents a disposable Linux VM, not your laptop
#133And, make coding harnesses run 20x faster at many multi-processing and file operations by running the coding harness itself inside of Linux instead of MacOS…
Is file IO a bottleneck now?
Re: Show HN: Clawk – Give coding agents a disposable Linux VM, not your laptop
#134How many of these are there now, a hundred? We get it, you can run an agent in a VM/container/sandbox. What about configuration management & rollbacks? What about the policy engine? What about dynamic credential management? What about the lethal trifecta? A sandbox is the easiest part and doesn't address the others.
Huh. My virtdev project implements nearly all of that... Except credential injection from the host, which turned out to be on my TODO list.
You do have some scripts that 'diff' package inventory of the one distro you support, but not a full fledged configuration management system to manage package dependencies, file permissions, services, etc. Technically the user can deploy one using your provisioning hook but since it's not built-in it's another component the user will need to bring with them, which is one more reason they can use any other system that does basic sandboxing. I'm sure it's useful for you, but it doesn't do anything all the other solutions don't already do. You basically made Vagrant but without the useful Vagrantfile and OS-agnosticism.
Re: Show HN: Clawk – Give coding agents a disposable Linux VM, not your laptop
#135Re: Show HN: Clawk – Give coding agents a disposable Linux VM, not your laptop
#136How many of these are there now, a hundred? We get it, you can run an agent in a VM/container/sandbox. What about configuration management & rollbacks? What about the policy engine? What about dynamic credential management? What about the lethal trifecta? A sandbox is the easiest part and doesn't address the others.
Re: Show HN: Clawk – Give coding agents a disposable Linux VM, not your laptop
#137Re: Show HN: Clawk – Give coding agents a disposable Linux VM, not your laptop
#138Re: Show HN: Clawk – Give coding agents a disposable Linux VM, not your laptop
#139Earlier quoted context omitted.
If you are into nixos, we at InstaVM have just launched[1] nixos based sandboxes. 1. https://instavm.io/blog/nixos-reproducible-dev-environments-...
That's very cool, although AFAICT my hacked-together non-product shares most of the same virtues. Can you upsell it to me a little?
1. Tarit - https://GitHub.com/instavm/tarit