I really feel for the OpenCode team, as agentic attacks are becoming more common and defending against them is difficult, especially when you’re also trying to build something people love.
If you’re affected, rotate your keys immediately and check your provider audit and usage logs for unauthorized activity.
There is a path forward where connecting a tool doesn’t mean handing it a long-lived key. Workload identity federation and delegation let us issue short-lived, scoped access, while proof of possession means a copied token alone isn’t enough to use it elsewhere.
We don’t yet know the full details of this incident, but we can make progress together on reducing what an attacker can steal and reuse. That’s a big part of what we’re building at @KeycardAI, alongside centralized audit logs and the ability to revoke access where it’s enforced.
@peduarte Same i'm not trying to convince you it's a bad decision to bundle BYOK under a paid plan and have your users (yours truly after 3 years of a paid plan) leave to try other forks and open source solutions, and basically finding it the same experience so far
@peduarte I'm pretty sure anyone who knows how to bring their own keys is technical enough to vibe clone that UI functionality. I just wanted to point out it is really not a great value as you think it is for 8 per month
I'm sick of researchers improving weather forecasting literally every week in the headlines and still the damn forecasts can't reliably predict the next hour