omp packages

pi-codex-accounts0.3.0

Keep your work and personal ChatGPT accounts signed in to pi side by side, and switch between them from /model.

GitHub Actions Published 5 days ago MIT ~429 downloads/mo

Untested on omp

This is a pi package. No one has reported whether it works on omp yet. If you try it, add your result below.

Did it work for you?

Result

One report per person. A new report replaces your old one.

Reports 0

No reports yet.

Readme

              __                                      __
 _______  ___/ /____ __  ___ ____________  __ _____  / /____
/ __/ _ \/ _  / -_) \ / / _ `/ __/ __/ _ \/ // / _ \/ __(_-<
\__/\___/\_,_/\__/_\_\  \_,_/\__/\__/\___/\_,_/_//_/\__/___/

          [ work ]   <-- /model -->   [ personal ]

pi-codex-accounts keeps your work and personal ChatGPT accounts signed in to pi, side by side.

pi's built-in OpenAI provider holds one ChatGPT login. If you use one account at work and another for your own projects, switching means logging out and back in every time. This little extension gives each account its own login and its own models in /model, so switching is just picking a model.

gpt-6.1-sol [openai]              your personal account (pi's built-in provider)
gpt-6.1-sol [openai-work]         your work account
gpt-6.1-sol [openai-codex-work]   your work account, through the Codex OAuth login

Install

pi install npm:pi-codex-accounts

Set it up

  1. Name your extra account in ~/.pi/agent/codex-accounts.json:

    { "accounts": ["work"] }

  2. Restart pi, run /login, choose Sign in with an account, and pick OpenAI (work).

  3. Sign in with your work ChatGPT account. A private browser window helps, so the browser doesn't reuse the account it is already signed into.

  4. Open /model and pick any [openai-work] model.

Each label also gets an OpenAI Codex (work) login, with the provider id openai-codex-work. It copies pi's legacy OpenAI Codex provider and its Codex OAuth login, which signs in through the browser or with a device code. Sign in there too if a tool reads the account's quota, such as quota-axi: a Sign in with ChatGPT token returns no quota data, and quota-axi measures the openai-codex-* logins.

The accounts file

Each label becomes two accounts: "work" shows up as OpenAI (work), with the provider id openai-work, and as OpenAI Codex (work), with the provider id openai-codex-work. If you have more than one work account, for example one per client, list them all: { "accounts": ["work", "client"] }. Without the file you get one extra label, 2. The label codex is not allowed, because its provider id openai-codex belongs to pi's legacy Codex provider.

pi saves each login under the provider id, so renaming a label means signing in again. The old login stays listed in /logout under its old id, and you can remove it from there.

Upgrading

To update, run pi update --extensions and restart pi. If you installed a fixed version, such as npm:pi-codex-accounts@0.1.4, run pi install npm:pi-codex-accounts first, because pi does not update a fixed version. The accounts file keeps its name and its format.

Version 0.1 copied pi's OpenAI Codex provider, which pi now calls legacy, under openai-codex-work. Version 0.2 copied pi's OpenAI provider and its Sign in with ChatGPT login instead, under openai-work, and needs pi 1.0 or newer. Version 0.3 gives each label both, so a login saved by 0.1 works again under its old id, and a login saved by 0.2 stays as it is.

How it works

Each account is pi's own OpenAI provider under a new id: the same Sign in with ChatGPT flow, the same models, and the same request code. The Codex account is pi's own legacy OpenAI Codex provider under a new id in the same way. Both behave like the built-in provider and pick up new models whenever pi updates. If a future pi drops the legacy Codex provider, the Codex accounts go away and the others keep working.

Accounts stay separate. Each one has its own saved login, and when you switch accounts in the middle of a conversation, one account's encrypted reasoning is never sent to another.

Your tokens stay in pi's auth.json. The extension never copies them into environment variables, so commands the agent runs can't read them.

Tested with pi 1.0.3.

Development

npm install
npm test

npm test runs the type check, the unit tests, and a smoke test that installs the packed package into pi the way pi install does. Releases are built on GitHub Actions and published with npm trusted publishing, so every version on npm links back to the commit it came from.

License

MIT