EvanZhouDev

I would say that the risk is very low. OpenAI has allowed usage of Codex's OAuth in other AI harnesses (as per communications on X/Twitter), and this is simply generalizing that. I have personally been using OpenAI OAuth's CLI frequently since v1 months ago.

That being said, by using OpenAI OAuth, you assume the risks of using this project, and you are still responsible for complying with OpenAI's Terms of use and usage Policies. See https://github.com/EvanZhouDev/openai-oauth#legal for more information.

OpenAI OAuth v2's new Sign in with ChatGPT button lets users securely link their free or paid ChatGPT account that your app can use as an OpenAI API. It uses a reverse-engineered version of Codex's OAuth flow under-the-hood, and authenticates directly between your browser and OpenAI's servers with the credentials passed locally through a Sign in with ChatGPT browser extension.

And, just like OpenAI OAuth v1, you can always run `npx openai-oauth@latest` to instantly get a free local OpenAI API with your Codex account.

OpenAI OAuth v2 is open source under Apache-2.0 on GitHub: https://github.com/EvanZhouDev/openai-oauth

Let me know if you have any feedback or find any bugs!

To be clear, when I posted this, the title of the post was "IPv8 Proposal". However, it seems to have been edited at some point to be "Internet Protocol Version 8 (IPv8)" thus becoming a misleading title and seems to have gotten his post flagged. Not sure how that happened, or why.

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).

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.

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

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.

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!