[ed_mercer]

For us, we actually moved away from k8s to dedicated VMs on Proxmox for our agents. We initially had a containerized environment manager running in k8s, but found that VMs give you things containers struggle with: full desktop environments with X11 for GUI automation, persistent state across sessions and dedicated resources per agent. Each agent gets their own Debian VM with a complete OS, which makes it much easier to run tools like xdotool and browser automation that don't play well in containers.

[indigodaddy]

Yeah, I feel like k8s is adds unneeded complexity. I started this project to isolate via LXC/Incus containers on a VPS/server. Works nicely for my needs.

https://github.com/jgbrwn/vibebin

[eftalyurtseven]

Makes sense, if your agents need full desktop and GUI automation VMs are the way to go. klaw is more on the headless side, agents talking to APIs, Slack, X, that kind of thing, so the lightweight binary model works. How many agents are you running on Proxmox?

[ed_mercer]

Ahh, that makes sense. Yeah you likely have a very different business model. We're more using them as "AI employees" that help us with tasks. Currently running 4 of these VMs but planning to add more. Note that each VM has a specific role: cluster monitoring, database stats, frontend/backend features (this is where VMs really shine) and a (very experimental) high-level manager.

[mountainriver]

I got this issue too, but still found that a containerized desktop was superior due to resource efficiency

[NewJazz]

I have never had an issue with browser automation like selenium in containers. Is that actually an issue?

[ed_mercer]

We found that it works great for scraping but it's not so great for development. git worktrees in a VM are much faster over spinning up new containers with an existing codebase.