Formal gives cloud coding agents read-only production access without a single stored secret
We let our cloud agents query prod (with OIDC, not secrets)

Formal, which has long pushed to eliminate long-lived secrets, now uses OIDC to let cloud coding agents like Cursor and Devin reach production databases, S3 buckets, and cloud accounts. Each agent session becomes its own short-lived identity, tied to the engineer who launched it and the repo it works in, with access approval-gated and read-only. The same identity-propagation pattern already used for Metabase turned out to fit shared agents almost perfectly.
The broader lesson from our internal use is that agent access should be modeled as a temporary delegation — not just as another machine workload with another long-lived secret.