You need to read this thread, its legit hilarious.
@alatiera The funniest one to me is when people say "oh just use a sandbox for the personal assistants" completely ignoring that as soon as you fetch any relevant 3rd party data into the context as "parameters" those parameters can now make the app and anything consuming the return values do basically anything
"What if we made SQL injections a first-class feature in every app" etc.
Doesn't matter for anything that's not like OpenClaw but still, it's crazy how unaware people are of this
@alatiera Lmao
It's kind of a bummer that this is like a fundamental design flaw of them. I have a few friends who demoed what's essentially client-side search engines built on top of this stuff and it's incredible. You can give it queries like "find that one issue with IPv6 in GNOME OS and find what's been changed since the last time I visited" and it will actually find it. You can even have it ping you when things change. But the second you give it any kind of access token you've (1/2)
@alatiera allowed basically anyone to do anything with your account by pasting a random string in a GitLab comment.
I've seen people add "read-only email access" to their personal assistants, completely forgetting that yk every password reset flow uses the email so it's actually effectively a write permission to every account 🙃
@alatiera Yeah exactly
One of the better uses I've recently discovered is the new search on Vercel (terrible company otherwise but yk). You press cmd-k with any query, like "add work account", and it drops you to the right place in the settings in the right project etc.
No mention of LLMs anywhere either, it's just a simple "no keywords found" → fallback to LLM which works very nicely because gosh is finding these things otherwise annoying