I woke up to a thread of people complaining that they couldn’t get GPT-5.6. OpenAI had pulled back the rollout, gating access so only a slice of users could touch the new model while everyone else sat in a queue. The reasons behind the throttle aren’t the interesting part to me. What stuck was the shape of it: a model existed, it worked, and whether you could use it came down to a switch someone else controlled.

If your AI tool is wired to one provider, that switch is your switch too. You don’t get a vote.

Access is a feature now, and it’s not yours

For a while the story we told ourselves was that the model was the bottleneck. Get GPT-5 working, get it smart enough, and the rest follows. But the GPT-5.6 situation flips that. The model was ready. Availability was the thing being rationed, and availability turns out to be a lever that can move for reasons that have nothing to do with you, your work, or whether you’d happily pay.

So you’re a designer who builds a whole workflow around one model’s quirks. Or you’re a small team that standardized on a single API. The day the rollout gets throttled, paused, or region-locked, your tooling degrades and there’s no menu to pick from. You wait. That’s the whole experience. You wait.

This keeps happening, by the way. Nvidia pulled back from OpenAI earlier this year and people who’d bet everything on one stack felt it. I wrote about that in Nvidia Just Pulled Back from OpenAI. Different trigger, same lesson.

What bring-your-own-key actually buys you

BYOK is one of those acronyms that sounds like plumbing and ends up being the whole point. When you bring your own key, your tool isn’t married to a single provider’s rollout calendar. You point it at whatever model you can actually access, which might be GPT-5.2 today because 5.6 is rationed, Claude tomorrow because it shipped a better update, Gemini for the cheap bulk task, and DeepSeek when you’re watching cost.

This is the part that matters: the switch moves back to you. Not to a press release, not to a status page, not to whoever decided the rollout should slow down. You.

Dassi works this way on purpose. You can log in with your existing ChatGPT subscription if you don’t want to mess with keys at all, or you bring your own API key and run whatever provider you like. When one model gets throttled or starts acting weird, swapping is a dropdown, not a migration. And because nothing in your setup assumes a single vendor will always be there, a bad day at one lab is just a bad day at one lab.

The other half nobody mentions

Here’s where most of the BYOK conversation stops short, and it bugs me. People treat model choice as the finish line. Pick the right model, you win. But a model in a chat window is still a model in a chat window, no matter how clever it is, and it cannot see the invoice you have open, the form you’re halfway through, or the inbox you’re trying to clear without you copying every last detail into it by hand like it’s 2023 and we’ve learned nothing.

The reason BYOK plus a browser agent is the combination I keep coming back to is that the flexibility only pays off if the model can act where your work already lives. Dassi runs in your browser side panel and reads the tab you’re on. So switching models doesn’t mean rebuilding your workflow. The model changes underneath; the thing it operates on, your actual page, stays put.

That’s the difference between renting access to an AI and owning your setup. With a locked-in tool, a rollout limit somewhere far away quietly downgrades your day. With a key in your pocket and an agent in your browser, you reroute and keep moving.

Stop betting your week on one company’s good mood

I switched my own habit a while back, and the relief was mostly about not caring which lab is having a moment. There’s a related post on this, You Switched from ChatGPT to Claude. You’re Still Locked In., because swapping one single-vendor dependency for another single-vendor dependency isn’t the upgrade people think it is.

GPT-5.6 will roll out wider eventually. Some other model will get gated next, for some other reason, and a fresh batch of people will discover their tool only speaks one language. If you’d rather not be in that batch, Dassi is free on the Chrome Web Store and it’ll run whatever you can get your hands on.

Whatever’s available tomorrow, you’ll already be holding the key.