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.
There were rumors about OpenAI preparing for sign in with OpenAI to let users use their OpenAI allowances with apps, si this is basically it. The question is, how long before OpenAI bans this or makes it official.
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 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
I feel like this will have a short shelf life. OpenAI is going to notice traffic through that Codex endpoint that doesn't match its usage patterns and lock it down.
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.
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.
There were rumors about OpenAI preparing for sign in with OpenAI to let users use their OpenAI allowances with apps, si this is basically it. The question is, how long before OpenAI bans this or makes it official.
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 tend to think openai will just make this official rather than ban it based on their historical stance here
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
I feel like this will have a short shelf life. OpenAI is going to notice traffic through that Codex endpoint that doesn't match its usage patterns and lock it down.
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.