These feels like langchain all over again. I still don’t know what problem langchain solved. I remember building tools interfacing with LLM when they first started releasing and people would ask, are you using langchain and be shocked that I was not.
I would argue that issuing commands to an LLM that has access to your digital life and filesystem through a SaaS messaging service is stupid to an unimaginable degree.
To each their own!
The Discord/Slack frontend reduces friction significantly - particularly on mobile.
With proper sandboxing you get real benefits while limiting the blast radius significantly.
If it's properly sandboxed then I fail to see how it's useful, unless you're attaching it to your e-mail, calendar, etc. If you're attaching it to those things, then I still don't see how the SaaS messenger account you're using being hacked doesn't still directly imperil your personal information.
Like, I could run this thing on an isolated VLAN in a VM, but if I hook it up to a SaaS app for its frontend, then it's immediately insecure if the bot is connected to anything of value. If it's not connected to anything of value, then what's the point?
Clawdbot is one of those things that's really hard to get unless you have experienced it.
It's got four things that make it great:
1. Discord/Slack/WA/etc integration so those apps become your frontend
2. Filesystem for long term memory and state
3. Easy extensibility with skills
4. Cron for recurring jobs
Sure, many of these things exist in other systems but none in a cohesive package that makes it fun and easy.