Local-first profile launcher for macOS

Profiles, without the ritual.

Choose a profile. Launch Codex CLI or the macOS app. Switching is always explicit—and authentication stays with the official Codex tools.

Free and open source · MIT · macOS 15+

Three isolated profile windows orbiting an Open Profile Manager control plane

Why OPM

One deliberate choice replaces a fragile routine.

The problem

Profiles live apart. Your workflow should not.

Separate CODEX_HOME directories are useful, but remembering paths and rebuilding launch commands is busywork.

The choice

No silent switching.

You select every profile yourself. Quota status informs; it never triggers account rotation.

The boundary

Your tokens stay untouched.

OPM never reads, copies, decodes, migrates, prints, or stores authentication tokens.

The result

A small control plane for local profiles.

Keep profiles isolated, see their status, and launch the right official Codex surface with a clear, explicit action.

See the workflow

From profile to focused session.

Videos load only when you play them.

LaunchPick a profile and open a new session.
Visual transcript
  1. Two terminal windows show why sharing one Codex home between accounts is fragile.
  2. Open Profile Manager is introduced as a way to keep every account cleanly separated.
  3. Three named profiles are added with distinct local directories.
  4. Read-only quota status is shown for each profile; switching remains manual.
  5. opm run work launches the real Codex process in the terminal.
  6. The native macOS app, privacy boundaries, and GitHub project are shown.
CLI tutorialUse the focused opm command-line workflow.
Visual transcript
  1. Clone the repository, run the local installer, and confirm the installed version.
  2. Add Work, Research, and Client profiles with separate CODEX_HOME directories, then list them.
  3. Delegate authentication to the official Codex login flow; OPM does not handle tokens.
  4. Check read-only quota status for all profiles.
  5. Launch the CLI, official macOS app, or a profile-specific Finder launcher explicitly.
  6. Run opm doctor to verify the registry, Codex CLI, official app, and private directories.
App tutorialUse the same profile model in a native macOS interface.
Visual transcript
  1. The profile list and explicit actions are introduced in the native macOS app.
  2. A Client profile is added with its own Codex home.
  3. The Research profile is selected and its read-only quota status is refreshed.
  4. The Work profile's CLI command is copied for use in Terminal.
  5. The independently installed official macOS app is launched with the Work profile.
  6. A profile-specific Finder launcher is installed in ~/Applications.

What it does

A profile manager, kept intentionally narrow.

Explicit launches

Select the profile first, then launch Codex CLI or the independently installed macOS app.

Useful status

Read profile and quota status without turning it into automatic account selection.

CLI and native app

Use a concise command-line tool or a focused AppKit and SwiftUI interface.

English + Português

Use the macOS experience in English or Português.

Privacy by boundary

Local profiles. Official authentication.

OPM stores local profile configuration and launch preferences. Authentication remains owned by the official codex executable inside each profile's CODEX_HOME.

Install

Download the notarized app.

Get the latest signed, notarized release for macOS 15 or later. Install the official Codex CLI separately.

Download latest release

Build from source

git clone https://github.com/mneves75/open-profile-manager.git && cd open-profile-manager && Scripts/bootstrap.sh && Scripts/check.sh && Scripts/install-local.sh

Prefer to inspect first? Read the installation guide.

Keep the choice yours

Launch the profile you meant to use.