Background agents should act under their own identity and authority.
This isn't the industry go-to for non-technical reasons; creating a client / app identity on most SaaS can only be done by admins.
To avoid the organizational challenge, we use delegation, PATs and api keys.
software factories feel like a temporary problem. the models will learn to build them for you
the more interesting question to me is how to build a workspace where agents can collaborate with you
the most import skill in 2026 is still being able to tell your agents "wtf is this crap, no, not like this"
if you stop doing that, you're basically fucked, despite what some devfluencers would like you to think.
the most import skill in 2026 is still being able to tell your agents "wtf is this crap, no, not like this"
if you stop doing that, you're basically fucked, despite what some devfluencers would like you to think.
I see a lot of people describe their agent setups. But I don’t see many ways for other people to quickly clone and run that setup. The distribution model is lacking. What projects do you know that are solving this?
This is the way. People are shocked that I use AI all the time, but never on my own machine. Open claw, Hermes, grok @bot all running in a Mac mini. Separate email. Separate phone number. Separate Twitter (@clawdreyhepburn if you want to say hi). Don’t let agents impersonate you - give them their own identities.
When you collaborate with coworkers, you are not delegating your access to them. Yet this is how most AI access works. That’s going to change. Collaboration, not delegation.
Credentials and corresponding challenges need to be in-path of a harness so that an agent can reason over its own access paths. Challenges in particular are useful here.
Personal agents demand this, since the services they call don’t control the network or the harness. Yet they need to be able to challenge for credentials.