> So you're explicitly picking a bot per person, you're just calling them an agent. But you never really admit this because you call it 'an agent' rather than "the user's agent". You're still ending up with lots of agents each owned by people, you're just writing another orchestration layer yourself.
Giving everyone their own agent/bot/app in Slack is nontrivial because of how Slack apps work. If you're okay with them impersonating you, it's easy, but that's weird and I don't like having to guess/discern if I'm talking to you or a bot wearing your face
> How? How is this resource managed or limited? Do I have to assume Buzz will just borrow my laptop's CPU & GPU at random?
This is opt in. It's an integration with https://github.com/Mesh-LLM/mesh-llm that scopes shared compute to your Buzz community. This is very early right now and we're working to get it right. But the idea of a totally self-sovereign, self-hosted community providing its own inference is exciting.