SignalOct 24, 20261 min read7 sources

Agents are getting their own identities and credentials, separate from the people they act for

In one minute

Glean now lets agents run under their own governed accounts. 1Password and Browserbase hand agents sign-ins without showing them the credentials, Vercel is replacing static keys with short-lived ones, and Cloudflare is working with card networks to authenticate shopping agents.

Banks meanwhile say they can't tell whether an agent was sent by the customer or went rogue. Builders should give each agent a verifiable identity of its own instead of reusing a person's login.

From the Field Notes:

Evidence / sources

  1. 1docs.glean.com/release-notes/releases/2026-10-01-october-release
  2. 21password.com/blog/1password-for-ai-agents
  3. 3browserbase.com/blog/browserbase-is-partnering-with-1password-for-agents
  4. 4vercel.com/blog/death-to-long-lived-static-credentials
  5. 5cloudflare.com/press/press-releases/2025/cloudflare-collaborates-with-leading-payments-companies-to-secure-and-enable-agentic-commerce
  6. 6axios.com/2026/10/22/ai-agents-banks-unauthorized-accounts-access
  7. 7docs.factory.com/delegations/slack
All Signals

Next reads

Read next

Open the graph
  1. 01archiveSignalsOpen the signals and the raw-signal archive.
  2. 02sourcesSourcesSee the original sources this archive cites.
Who read this page?Machine requests, hidden until opened

Loading the privacy-safe route aggregate...

Open the JSON contract