This ChatGPT proxy is dead. Let it rest.

What it does

go-chatgpt-api was a Go reverse proxy that intercepted traffic between third-party ChatGPT clients and OpenAI’s web endpoints. It translated web accessTokens into pseudo-API keys through an /imitate/v1/chat/completions shim, letting users plug ChatGPT web credentials into software that expected a standard OpenAI API key. The author now considers the project deceased and warns that every instruction in the README is outdated as of October 2023.

The interesting bit

The README opens with a blunt eulogy—“这个项目已经死了，请让它安息吧”—and then proceeds to document a sprawling integration list covering everything from QQ bots to Feishu plugins. It is essentially a snapshot of the duct-tape era when ChatGPT had no official consumer API and developers treated Cloudflare bypasses as infrastructure.

Key highlights

• Exposed ChatGPT web endpoints as proxy routes, including login, conversation CRUD, model queries, and plugin listing.
• Provided an /imitate/v1/chat/completions endpoint that let users swap an apiKey for a web accessToken in standard OpenAI client libraries.
• Bundled optional WARP proxy support and a Render deploy target for users in regions with blocked access.
• Shipped integration snippets for at least six third-party clients, including ChatGPT-Next-Web, Pandora, and a Mirai QQ bot.

Caveats

• The author explicitly declares the project dead and states all documentation is expired and unsupported.
• Google and Microsoft account logins were never supported, even when the project was maintained.
• GPT-4 required a community-sourced arkose_token workaround that the README treats as external configuration, not a first-class feature.

Verdict

A useful archaeological dig if you want to understand how the pre-API ChatGPT ecosystem operated, but actively unsafe to run today. Anyone needing a current proxy should treat this repository as read-only history.