All Blog

Why not hand your API keys to a host: lessons from a key leak

A hosted console that leaks third-party keys can run up your provider bill overnight. Local BYOK cuts that middleman — not a promise of perfect safety.

Why not hand your API keys to a host: lessons from a key leak

Overnight, spending alerts fire on OpenAI, Anthropic, and Google at once. You did not run that traffic. Someone else did, with a key you left in a hosted console.

In October 2026, OpenCode said attackers broke into an older system and affected about 1.4% of OpenCode Console users, the online workspace where some people store third-party API keys. Developers reported unauthorized charges; some posts described hundreds of dollars, a few above $1,000. TechCrunch covered the incident and the scramble that followed (report). BleepingComputer separately noted user reports of overnight totals over $1,700 (coverage). Those figures are user reports, not an official aggregate.

OpenCode said the exposed keys were confined to Console. Co-founder Dax Raad wrote that the open-source app and CLI were not affected: keys for those "never come to us." Anthropic and Google blocked keys they believed were exposed; OpenAI worked with OpenCode on access and refunds. OpenCode told affected users to revoke and replace keys with each provider.

This post is not a takedown of one product. It is about a pattern: a hosted workspace that holds your provider key is another place that key can leave without you typing it.

An API key is closer to a card without a PIN

A provider API key is a bearer credential. Whoever presents it can spend against your account until you revoke it. Deleting the key from a console does not always mean the provider has invalidated it. You still need to rotate at OpenAI, Anthropic, Google, or wherever the key was issued.

That is why "I removed it from their UI" is not the same as "they cannot charge me anymore." The pin-less card analogy is imperfect, but the spending risk is the same: custody matters more than the brand of the wallet.

What "don't hand keys to a host" means in practice

You do not need to abandon every cloud tool. You do need a clearer custody rule:

  1. Prefer tools that keep keys on your device and call the provider from your machine, not through another company's hosted workspace that stores the same secret.
  2. Set spend limits and alerts at the provider. Caps and emails catch runaway use faster than hoping a middleman notices first.
  3. Rotate keys after any suspected exposure, and on a schedule if a key ever sat in a shared console.
  4. Use separate keys per tool or project when the provider allows it, so one leak does not open every workflow.

Local BYOK (bring your own key) follows that rule: the key stays on your computer; model calls go to the provider you choose. It reduces the "extra hosted middleman holding your key" surface. It does not mean your laptop cannot be compromised, malware cannot read a file, or a key can never leak. One less layer is not a security certification.

Where a local desktop BYOK app fits

Teebots is a local desktop multi-bot app. You bring your own key. The app is free; model spend lands on your provider bill. Requests go to the provider you pick, not through Teebots as an official model relay. Multi-bot group chat, personal memory, scheduled tasks, and bot browser use are available in the desktop client (download).

That is a custody choice, not a promise that local equals untouchable. We are not claiming military-grade key vaults, zero leak risk, or that every threat model prefers on-device storage. For path and product contrast, see Teebots vs Grok Bot. If your pain is shared weekly quotas burning out mid-week, start with Cloud quota burned out? Move to a local BYOK multi-bot setup.

Who still needs a hosted console

Some teams want a shared gateway so members never see the raw key. That is a real tradeoff: convenience and central policy versus an extra party that can hold the secret. If you go that route, treat the console like production infrastructure: least privilege, rotation, provider caps, and an exit plan to revoke at the issuer. This article does not recommend any specific hosted console; it only notes why the custody question exists.

If key custody is the worry

Start by inventorying where your provider keys live today. Anything sitting in a third-party hosted workspace is a candidate to move or rotate. Prefer on-device BYOK for personal and small-team agent work; keep provider spend limits on; revoke old keys that ever lived in a breached or unclear console.

Quota and role control are a different problem, covered in the migration post. Key custody is this one: fewer places that hold the secret, and revoke rights that stay with you and your provider.

Your local team of bots

Not locked to one model vendor. Each bot uses your own key — Claude, OpenAI, DeepSeek, Kimi, or any compatible endpoint. Requests go straight to the provider.