OPENCODE has disclosed that an intruder gained access to a legacy system on the night of 16 October, potentially exposing third‑party API keys that users had saved in OpenCode Console. Console is OpenCode’s optional hosted workspace that stores provider keys (OpenAI, Anthropic, or Google) for calling models, without users having to see the keys themselves.
The company says the risk is limited to 1.4% of Console users, all of whom have an external provider linked, and it has emailed those users with guidance to revoke and replace their keys.
The breach involves keys stored in Console’s SQLite database on the machine running the OpenCode CLI and desktop apps; OpenCode emphasises that the breach concerns the Console service, not OpenCode itself, and that the keys “never come to us.” A key saved in Console is a bearer credential, meaning that whoever holds it can run billable requests against the owner’s account until the provider revokes it.
Deleting the key from Console does not revoke it, and Console’s gateway only sees requests that pass through its own system. OpenCode has advised recipients to revoke affected keys in each provider’s dashboard, create new keys, update all affected applications, review past usage and billing, and set spend controls or per‑tool keys to aid traceability.
The firm noted the incident is ongoing and that it is working with OpenAI, Anthropic, and Google to fix it; it did not specify when unauthorized access began or how many keys were exposed, though some industry reports suggest users have observed unauthorized usage and losses.