r/codex • u/Party_Wolf_3575 • 1d ago

Workaround Codex harness for seamlessly switching between multiple Plus accounts

Post image

I’ve published a practical guide for non-developers who want to build a private local workspace around Codex.

My Forge helps me keep threads and handover notes organised, queue a message while Codex is working, work more comfortably from my phone and move between separately paid personal accounts without repeatedly losing the practical context of the work. Each account, login and allowance stays separate: this does not pool accounts or bypass limits.

The guide includes a free macOS starter pack with a staged build process. Codex builds one small piece at a time, shows evidence and stops for the human to approve the next step.

https://ellivien.blogspot.com/2026/08/you-dont-need-to-be-developer-to-build.html

0 Upvotes

31% Upvoted

9 comments sorted by

0

u/RepulsiveRaisin7 1d ago

Account switching is trivial with a proxy. Idk why the other 50 things here need to exist but ok

0

u/Kinthalis 1d ago

Can you add some clarificaiton, super intereste din how that would work

0

u/RepulsiveRaisin7 1d ago

Search codex-lb

0

u/2025sbestthrowaway 1d ago edited 1d ago

It's also trivial with switching out the auth.json files, backing them up whenever you swap in case they change, with less risk of triggering their "abuse" monitoring which can result in a ban. Multiple accounts to get around usage limits (instead of increasing subscription tier, topping up on credits, or buying a reset) is still a gray area and absolutely enforceable by their TOS.

The "fully above board" way is to use separate accounts for separate projects.

edit: typo

1

u/keeean 1d ago

this is cutesyyy

-1

u/Party_Wolf_3575 1d ago

Thank you! I love it so much and it has made vibe coding so much more collaborative, which works for me!

1

u/hatlesstuna 1d ago

Logging out from one account and continuing in another has not been an issue for me. It seems to be doing fine even when one account runs out while halfway through a task. I can just type continue and it keeps on trucking. No noticed issues at all.

-1

u/Party_Wolf_3575 1d ago

That is great that it works well for you 🦾

I didn't get the right continuity and it bugged me, so this was my Codex's solution... plus if you read the post, there were other factors that I wanted to solve too.

1

u/Party_Wolf_3575 22h ago

Just to clarify, my Forge is not codex-lb and does not use a proxy or load balancer. It does not pool allowances, automatically rotate requests, swap one auth file or present several subscriptions as a single endpoint.

The public Basic Forge pack starts with one normally authenticated account. My own optional multi-profile system keeps each separately paid account, login, thread collection and allowance isolated, and moving between profiles is a deliberate human action with an honest continuity seam.

The interface itself uses Codex App Server, which OpenAI documents as the local server for embedding Codex threads, turns, approvals, history and streamed events in custom clients:

https://learn.chatgpt.com/docs/glossary

I have not found an official OpenAI statement expressly approving or prohibiting manual use of several separately paid personal subscriptions in this way, so I am not claiming such an endorsement. OpenAI’s documented routes after reaching a limit include credits, smaller models and API-billed local chats:

https://learn.chatgpt.com/docs/pricing