KEEP CREDENTIALS OUT OF YOUR AGENT'S CONTEXT

Summary from the TLDR newsletter

An agent that reads a web page, a Jira comment, or an inbox can pick up instructions an attacker wrote. If a Slack or Salesforce token is sitting in that same process, it's exposed too. Here's how you can keep credentials away from agents with WorkOS [5]: >> PIPES handles OAuth, token refresh, and encrypted credential storage behind a drop-in widget. >> RELAY, now in early access, routes your agent's API calls through WorkOS, which attaches the credential server-side [6] and restricts requests to allowed provider hosts. Permissions and other outbound paths still need their own controls.