内部AI代理身份模式探讨
historically, most of our internal agents (openswe for coding, gtm agent for outreach) have acted "o...
LangChain创始人分享内部AI代理身份设计思考,探讨代理从工具向同事转变的可能性。
Harrison Chase讨论了公司内部AI代理的身份模式。他指出openswe用于编程,gtm代理用于外联,目前代理代表使用者行动。随着代理开始进行更主动的背景工作,他质疑这种模式是否应改变。他提出了三种可能的身份模式:固定凭据、代表使用者凭据,或混合模式。
historically, most of our internal agents (openswe for coding, gtm agent for outreach) have acted "o...
historically, most of our internal agents (openswe for coding, gtm agent for outreach) have acted "on behalf of" whoever is using them but as they start to do more proactive, background work... I wonder if that should change. eg i really like the idea Hone put forward of agents that are striving towards a goal ( x.com/hone/status/21… )... these kind of seem like coworkers, and i wonder if they should be treated as such Harrison Chase @hwchase17 what is the future of building internal company agents? how will their identity work? 1. fixed set of credentials 2. "on behalf of" flow (uses credentials of whoever is using it) 3. some fixed credentials, others "on behalf of" 🔗 View Quoted Tweet 💬 0 🔄 0 ❤️ 0 👀 298 ⚡