Tool Pools Multiple ChatGPT Subscriptions Behind One App

b-nnett shipped codex-subscription-router on GitHub August 16, and it passed 200 stars within a day. The tool patches a local copy of OpenAI's desktop ChatGPT app. It splits the app's single connection across several accounts, launching one official Codex process per subscription, each with its own isolated Codex home directory.

The Go multiplexer picks whichever account's weekly allowance is closest to running out, with a bounded boost for accounts holding banked resets in reserve. Once a thread starts, it stays pinned to the subscription that opened it. A follow-up keeps its conversation context and account-level caching instead of switching accounts mid-thread.

The repo ships build tooling only, not OpenAI's binaries, and the README carries an explicit unofficial warning. Not a hosted service. A local patch users assemble themselves, one OpenAI can shut down only by cutting off the accounts behind it.

I don't expect OpenAI's terms of service to tolerate account pooling like this for long, and I won't build anything load-bearing on top of it. What happens to pooled accounts once OpenAI's systems notice the pattern in request logs is the open question the project doesn't answer. The repo went up August 16, a day before this writing, with no word yet from OpenAI.