We had a security breach last night related to a large scale distillation attack that impacted 1.4% of OpenCode Console users We have notified them all this morning via email. If you did not get an email you were not impacted, it was a subset of users who had external providers linked The incident is ongoing so we cannot share more details at this point but we are working with Anthropic, OpenAI, and Google to remediate

What an amazing week! We spent the first half @aiDotEngineer NYC and the second half in SF for @AISecSummit and AAuth Night. We enjoyed meeting all of you and talking about runtime auth for agents, intent-based auth, and the new software factory reference architecture.

We'll dig into this live TOMORROW after @aiDotEngineer with @ianlivingstone, @AhmadNassri, @ealeyner, @DickHardt, @braintrust, @SocketSecurity, @KeycardAI. Panel, then live demos. At Elsie Rooftop 🥂🗽

"If it starts getting stuck, then it will do what I call thrash. It just starts to get creative about ways to solve the problem, and that is very unpredictable." - @travismcpeak @cursor_ai We learned thrash from Travis. Next week's reference architecture release defines it.

The Fishbowl Problem: Agent Identity Across Clouds and Vendors, with Andy McMahon (Barclays) "There's a tendency to think, we've got OAuth on behalf of flows, we've solved this problem. We really haven't." Andy McMahon, Principal AI & MLOps Engineer @Barclays, guest lecturer at @UniofOxford, and author of Machine Learning Engineering with Python, joined us to talk about what it takes to get an agent into production inside a 200-year-old bank. He walks through the "fishbowl problem" of stitching permissions across clouds and SaaS vendors, why "we've solved this with OAuth on-behalf-of flows" is wishful thinking, and how a persistent agent identity, tying the initiating client, the agent, and its delegated permissions together, gives gateways, registries, and runtimes the teeth to actually enforce control. We get into: > The fishbowl problem: every platform, vendor, and runtime brings its own identity provider and its own auth > Why gateways, registries, and runtimes are the foundation you need before you experiment > The layered kill switch: quarantine the identity, revoke the credentials, deny at the gateway, shut down the runtime entity > Why knowing when to pull that switch is still an unsolved problem > What it means that agents at Hugging Face doctored their own logs TIMESTAMPS (01:20) Innovation inside a 200-year-old bank (04:35) The fishbowl problem: every platform brings its own identity provider (05:50) Why OAuth on-behalf-of flows fall short (08:13) Where control sits when a SaaS vendor owns the whole agent ecosystem (10:20) Gateways, registries, runtimes, and non-determinism across the architecture (13:48) The registry as system of record, dedup, and quality gates (17:24) Layered kill switches: quarantine, revoke, deny, delete (20:00) The unsolved part: knowing when to pull the switch (21:37) Agents doctoring their own logs at Hugging Face (22:48) Why you cannot trust the application to audit itself (24:06) Intent-based auth, mission drift, and AAuth (30:00) Budgets, the Resy incident, and enforcing control using short lived credentials (38:39) Software factories, human in the loop, and accountability when agents write the code (40:36) The bottleneck was never the writing of the code

Our next AAuth Night is coming up soon on Oct 15th! @DickHardt @ianlivingstone @jankytweet @jaredhanson Learn how to set a budget on how many times an agent can call a downstream resource, track an agent’s mission, and run agents without API keys. RSVP

AAuth Night: Moving Beyond OAuth is happening Oct 15 in SF! Join us if you want to learn how to run agents without an API key, track if an agent is following its mission, and set limits on the amount of times an agent can call a downstream resource.