技巧多源确认

企业级AI的难点是认证管理,Cursor和Claude的认证方式不同

The hardest part of and “org harness” or “enterprise ai” (as opposed to personal ai” is auth, and ma...

精选理由

朋友在讨论企业AI时提到,Cursor和Claude在认证管理上有不同做法,Cursor的Slack认证方式有缺陷,Claude的PR流程更灵活,想找实际解决方案。

企业级AI的难点在于认证管理,Cursor的Slack机器人认证方式是发起者而非消息发送者,而Claude的PR流程允许绕过代码审查,因为PR被当作外部实体创建。有人询问实际可行的解决方案。

原文 · Harrison Chase

The hardest part of and “org harness” or “enterprise ai” (as opposed to personal ai” is auth, and ma...

The hardest part of and “org harness” or “enterprise ai” (as opposed to personal ai” is auth, and managing auth in a multiplayer channel (like slack) We’re thinking a lot about how to do this right for managed deepagents anirudh @kamathematic i love @cursor_ai but the slackbot auths as the user who started a thread (instead of the user who sent a message) meanwhile claude tag lets you bypass PR reviews bc the PR is opened as an external entity (claude itself) anyone have solutions that actually work here? 🔗 View Quoted Tweet 💬 0 🔄 0 ❤️ 3 👀 399 ⚡