The AgentSecrets Audit Log Had a Problem

The log was accurate. Every proxied request produced an entry with the timestamp, credential reference, endpoint, status code, and duration. Nothing was missing in the technical sense. But when something unexpected showed up, the first question anyone asked was the one the log could not answer: which agent did this? In a single-developer setup that question has an obvious answer. There is usually one agent running, one project configured, one reasonable explanation for any given entry. You can work it out from context. The moment a team starts running multiple agents across multiple workflows, that changes. A billing tool, a reconciliation script, and a new integration being tested alongside established ones all share the same log. STRIPE_KEY used at 14:22 on api.stripe.com — which one made that call? The log had nothing to say. That gap is what agent identity closes. What shipped in v1.1.1 Every agent using AgentSecrets can now carry a name. That name travels with every credential cal