The point of this approach is to create AI employees and interact with them as you would with employees, not to have an AI powered plugin for managing YouTube subscriptions. Nothing stops you doing both, of course, with AI "closer" to your accounts being more like a normal software feature that you just interact with and the Grok Bots or equivalent being more like employees that are expected to run for long periods without interaction with you.
replyThis sounds like a problem the service providers should solve. Some kind of 'create bot account' function where you can give granular permissions for a new account to interact with your data. This already exists in some form with company accounts.
replyThe likes of AWS and Github have scoped API keys for that purpose. But good luck trying to convince a non-tech company to implement something like this.
replyThis is the growing pain of any “employer” and I suspect lots of startups and features coming to fill the void.
replyStart with a shared credit card. Then company credit cards. Then you layer in spend controls.
Now repeat but for “agents”.
Whether this is more near term inefficiency to drive output side actual efficiency remains to be seen. But great if you’re selling tokens!
The issue is not just bank or CC accounts, but your personal data accounts (Email, photos, SMS, calendar, documents, etc.) that give the necessary context to the agent to do useful work for you. That's where the problem lies.
replyThey're nowhere near smart enough, but in an ideal case, the same utility you would get out of hiring a $600 a month personal assistant with a basic desktop PC who lives in a developing country somewhere on the other side of the planet and speaks reasonably good English. If the AI/LLM is good enough (they're not, yet), the same level of access/credentials/logins that you would give to an entirely new real person.
replyI'm 100% sure my (human) executive assistant can be tricked into mistakes with the appropriate phishing or social engineering, however the scope of tactics that can be employed for it seems limited to way fewer dimensions (eg, clear text email, maybe phone calls) vs the scope of prompt injections that could harm an equivalent AI assistant (which could include any hidden instructions in "invisible" text in emails, webpages, PDFs, screenshots, attachments and much more).
replySo, you mean that it will run its own AI agent, which itself also has its own computer, which will be used to run its own agent, which so has its own computer…
reply