I believe the goal of their "SSO with OpenAI" was to allow people to use ChatGPT-adjacent services on 3rd party websites with their OpenAI account after signing in. So similar in result, different in execution I suppose.

The repo does explicitly say to only use this for personal or experimental projects. That being said, OpenCode is relying on this in a "professional" context without any issue so far. I am not saying that is proof this is _not_ against ToS, but it does show perhaps OAI is ok with such usage.

I find it hard to believe they'll make it official completely, as that's basically giving away free API credits. If they really wanted the benefits of having free API credits they would just do that directly (but I doubt they'd do that in their current situation).

they'll probably just more accurately tie the api credit usage into your pro plan or whatnot so it's more clear what's going on. i just don't expect them to fully ban using the recurring consumer sub for api use

Worth mentioning this post: https://x.com/opencode/status/2009805930377167233

In which OpenCode "collaborates" with OpenAI to support login with ChatGPT Pro/Plus (through this exact method!)

Not exactly proof that this method is "OpenAI allowed" but it's a good sign at least.

This occurred in response to Anthropic cracking down on a similar loophole, which tbh made me take it as more of an opportunistic marketing opportunity rather than a generalizable position.

Not disagreeing with you (and based on your other comments you're probably aware of this info) - just adding context on why this is a pretty interesting gray area and I'm similarly curious whether OpenAI will explicitly allow, disallow, or maintain ambiguity towards it.

Sign in with OpenAI will be nice. That being said, I feel like it might be difficult/not open to use for casual devs. Hopefully OAI leaves this up, as they've allowed it for OpenCode. https://x.com/opencode/status/2009805930377167233

I believe that OpenAI has to a certain extent allowed such usage (see: OpenCode, OpenClaw which have OpenAI OAuth built-in). This just opens it up to other developers!

You're not really "opening up anything to other developers," you just had an AI leverage what they already provide to make yourself a proxy. There's probably 100 of these proxies if you search GitHub.

Yes, I agree with you! There are indeed quite a few other options. I will not say that this implementation is objectively better in any way. However, I do think that for me, this is the easiest one to use.