Earlier quoted context omitted.
I developed a VM project just like this one. Asked Fable to stress test it and try to break out of containment, and to my surprise it didn't manage to. Fable didn't get downgraded to Opus either, for some reason. Would have thrown Mythos at it if I had access to it.
Isn't Fable just Mythos + guardrails? Sounds like you did throw Mythos at it.
Show HN: Clawk – Give coding agents a disposable Linux VM, not your laptop
31–40 of 177 posts
Re: Show HN: Clawk – Give coding agents a disposable Linux VM, not your laptop
#32Re: Show HN: Clawk – Give coding agents a disposable Linux VM, not your laptop
#33If the agent is running on your machine, it will suspend when you put your laptop asleep. I prefer using a remote Linux VM to let the coding agent keep working. I’m quite happy with exe.dev for this. My laptop is asleep upstairs but I have an agent coding away in a browser tab on the tablet I’m using. I could also check on it from my phone. But it might also be nice if a setup similar to exe.dev were available for se…
Re: Show HN: Clawk – Give coding agents a disposable Linux VM, not your laptop
#34Re: Show HN: Clawk – Give coding agents a disposable Linux VM, not your laptop
#35Re: Show HN: Clawk – Give coding agents a disposable Linux VM, not your laptop
#36Re: Show HN: Clawk – Give coding agents a disposable Linux VM, not your laptop
#37If the agent is running on your machine, it will suspend when you put your laptop asleep. I prefer using a remote Linux VM to let the coding agent keep working. I’m quite happy with exe.dev for this. My laptop is asleep upstairs but I have an agent coding away in a browser tab on the tablet I’m using. I could also check on it from my phone. But it might also be nice if a setup similar to exe.dev were available for se…
It is possible to simply not do that. Laptops work just fine as servers. They even have a builtin monitor and UPS.
Re: Show HN: Clawk – Give coding agents a disposable Linux VM, not your laptop
#38I still don't understand the point of all these VMs and containers for agents. Just create a separate user on your machine without sudo privileges, switch to it in your terminal and run all the agents you want without it being able to reach your files. What am I missing?
VMs and containers are fairly isolated and reproducible. A separate user on your machine still depends on the programs installed locally.
Re: Show HN: Clawk – Give coding agents a disposable Linux VM, not your laptop
#39I still don't understand the point of all these VMs and containers for agents. Just create a separate user on your machine without sudo privileges, switch to it in your terminal and run all the agents you want without it being able to reach your files. What am I missing?
Container is quite like a "separate user" except you can explicitly define what it can access.
(Even if all your daemons have good auth, it's now quite common for _apps_ to open listening sockets without much auth...)
Re: Show HN: Clawk – Give coding agents a disposable Linux VM, not your laptop
#40I still don't understand the point of all these VMs and containers for agents. Just create a separate user on your machine without sudo privileges, switch to it in your terminal and run all the agents you want without it being able to reach your files. What am I missing?
In a corporate environment they may not have that option