I have a harness built on top of pi that uses XMPP for all agent communication with me and between agents[0]. It works well, I text them from my phone and from my browser (or anything else that supports xmpp). They can communicate with each other over group chats and can schedule agent tasks using a GitHub project and a cron job.
The agents run on my NixOS server in their own unix account, this is the real secret sauce. This lets me use unix perms to limit their access to things, and it allows them to handle server administration. I've given them access to a cli mail and calendar client[1], github, and they have the ability to deploy updates whitelisted services. NixOS lets them install whatever they want in ephemeral shells, and it's not possible for them to break the server in a way I can't trivially roll back.
They can modify the caddy config, so there have been times I've entirely built and deployed new services on a new domain from my phone on the bus.
The harness is called pi-msg, I've done a writeup of my machine's setup on my site.[2]
The agents run on my NixOS server in their own unix account, this is the real secret sauce. This lets me use unix perms to limit their access to things, and it allows them to handle server administration. I've given them access to a cli mail and calendar client[1], github, and they have the ability to deploy updates whitelisted services. NixOS lets them install whatever they want in ephemeral shells, and it's not possible for them to break the server in a way I can't trivially roll back.
They can modify the caddy config, so there have been times I've entirely built and deployed new services on a new domain from my phone on the bus.
The harness is called pi-msg, I've done a writeup of my machine's setup on my site.[2]
[0]: https://github.com/zachpmanson/pi-msg [1]: https://github.com/zachpmanson/docket [2]: https://notes.zachmanson.com/the-fleet/