How to use your Codex subscription on multiple computers (without re-logging in everywhere)

I used to treat “using Codex on another computer” as a setup tax.

You install the CLI.

You authenticate again.

You repeat it on your laptop, your desktop, and your server.

What I actually want is simple:

I log in once.
I can start Codex from whichever computer I’m on.
If I switch computers mid-week, I don’t re-do the whole auth dance.

There are a few ways people solve this today.

This guide covers the trade-offs, then the workflow I use that makes multi-computer Codex much less fragile.

TL;DR

Decide what you mean by “use Codex on multiple computers”:
- you want the same subscription login everywhere, or
- you’re fine with separate logins per computer.
The default (native) approach is separate computer logins.
If you want a “log in once, reuse on other computers” workflow, you need a system that can store the credential and materialize it on other computers safely.
In Happier, that’s done via Connected services (openai-codex). It can be consumed by:
- Codex
- OpenCode
- Pi

The problem

A Codex subscription is tied to an account.

A computer is tied to an environment.

If you log into Codex separately on three computers, you create three little snowflakes:

different accounts
different auth methods
different session browsing “homes”

And then debugging becomes: “which computer is logged into which Codex home?”

What I tried first (and where I bounced off)

Log in separately on every computer: works, but it’s easy to drift into the wrong account.
Copy config files around: brittle; also a bad habit with secrets.
Use one computer for everything: safe, but it’s not how I actually work.

If you’re new to Happier

If you haven’t seen Happier before: it’s an open-source companion app (mobile/web/desktop) that helps you run sessions like Codex and OpenCode across computers.

For this guide, the relevant part is simple:

it can store a Codex subscription login once
and reuse it on compatible backends on other computers

Get set up:

How to run Happier from your phone
GitHub: https://github.com/happier-dev/happier
Install/download: https://github.com/happier-dev/happier#how-it-works
Discord: https://discord.gg/W6Pb8KuHfg

The current “native” reality (what most people do)

Most people do some version of:

install the Codex CLI on computer A
log in on computer A
repeat on computer B

It’s not wrong.

It’s just easy to drift.

Especially if you have:

work + personal accounts
multiple servers
a laptop you wipe/rebuild

The “log in once” workflow (Connected services)

Happier models a Codex subscription login as a connected service: openai-codex.

The important part is compatibility:

Codex backend can consume openai-codex (OAuth)
OpenCode backend can consume openai-codex (OAuth)
Pi backend can consume openai-codex (OAuth)

So your logged-in-once Codex subscription can then be used to start Codex/OpenCode/Pi sessions, on multiple computers, without re-authing on each one.

Step 1: connect your Codex subscription once

In the app:

Settings → Connected services → OpenAI Codex

Complete the OAuth/device flow.

(If you’re on web, paste-based flows are used when redirect capture isn’t possible.)

Step 2: start a session on any computer using the connected auth

When you start a new session, compatible backends show an auth picker.

Choose the connected profile.

The daemon then materializes the backend-specific auth on the target computer.

Step 3: understand the “Codex home” gotcha (browsing sessions)

Codex session browsing depends on which auth you chose:

native auth → computer’s standard Codex home
connected auth → connected-service-backed Codex home

So if you can’t find a session when browsing, the first thing to check is: which auth home you’re browsing.

What still doesn’t magically go away

Even with a shared subscription login, each computer still needs:

the backend installed
a working environment (PATH, dependencies)

Connected services makes the credential portable.

It doesn’t turn an unprepared computer into a fully configured dev box.