ๆณจๅ†Œๅนถๅˆ†ไบซ้‚€่ฏท้“พๆŽฅ๏ผŒๅฏ่Žทๅพ—่ง†้ข‘ๆ’ญๆ”พไธŽ้‚€่ฏทๅฅ–ๅŠฑใ€‚

Guillermo Rauch
@rauchg
ๅŠ ๅ…ฅ July 2008
656 ๆญฃๅœจๅ…ณๆณจ    492.5K ็ฒ‰ไธ
Vercel protects your agents' deployments behind SSO like @Okta. Even Production ones, giving you a secure 'intranet' of apps generated with @v0, Codex, Claude, etc. It's all fun and games until your agent gets ๐Ÿบ๐Ÿถ๐Ÿท ๐š„๐š—๐šŠ๐šž๐š๐š‘๐š˜๐š›๐š’๐šฃ๐šŽ๐š from the deployment *it just made* though ๐Ÿ˜‚ The solution: ๐šŸ๐šŽ๐š›๐šŒ๐šŽ๐š• ๐šŒ๐šž๐š›๐š•. By just prefixing ๐šŸ๐šŽ๐š›๐šŒ๐šŽ๐š• or ๐šŸ๐šŒ you unblock your agent and yourself to easily ๐šŒ๐šž๐š›๐š• any URL you have access to within the Vercel ecosystem.
ๆ˜พ็คบๆ›ดๅคš
Vercel CLI now supports native curl commands. Same syntax as ๐šŒ๐šž๐š›๐š•, but uses Vercel auth to test all of your deployments.