๊ฐ€์ž… ํ›„ ์ดˆ๋Œ€ ๋งํฌ๋ฅผ ๊ณต์œ ํ•˜๋ฉด ๋™์˜์ƒ ์žฌ์ƒ ๋ฐ ์ดˆ๋Œ€ ๋ณด์ƒ์„ ๋ฐ›์„ ์ˆ˜ ์žˆ์Šต๋‹ˆ๋‹ค.

Caspar
@caspar_br
Agents @LangChain. ๐Ÿ‡ฆ๐Ÿ‡บ
๊ฐ€์ž… June 2016
153 ํŒ”๋กœ์ž‰ ์ค‘    2.4K ํŒฌ
Agent auth is hard, but it shouldn't be! Your agent needs to act as someone: sometimes that's one shared identity, sometimes it's the person asking. To get either right you'll need an OAuth app for each service, a token store, refresh logic, and a consent flow Today we're fixing this with Managed Connections: define who your agent acts as in code, and the rest is handled for you: ๐šŠ๐š๐šŽ๐š—๐š -> agent uses its own token ๐šž๐šœ๐šŽ๐š› -> agent uses the user's token, guiding them through the consent flow if they haven't connected yet With a single argument you avoid the whole OAuth dance. Available now, in ๐š–๐šŠ๐š—๐šŠ๐š๐šŽ๐š-๐š๐šŽ๐šŽ๐š™๐šŠ๐š๐šŽ๐š—๐š๐šœ 0.7
๋” ๋ณด๊ธฐ