How do I use separate work and personal Codex CLI profiles?

[Ducksss]

Use one profile name for each local Codex context. Every non-default name selects its own CODEX_HOME: work maps to ~/.codex-work, personal maps to ~/.codex-personal, and default keeps using ~/.codex.

codex-profile init personal
codex-profile login personal
codex-profile init work
codex-profile login work

codex-profile cli personal
codex-profile cli work
codex-profile cli work exec "run tests"

The first login for each profile authenticates that Codex home. Later cli commands reuse the selected home, including its auth, config, sessions, plugins, caches, and logs.

This does not switch an already-open ChatGPT Desktop window. Named macOS app launches use a separate whole-window local-state context; see How do I open separate named ChatGPT windows on macOS?.

codex-profiles only selects directories. It does not read, copy, print, parse, upload, compare, or migrate tokens. SSH keys, GitHub CLI authentication, browser cookies, and other operating-system credentials remain shared by the OS user.

See the Quick start and Security model for the complete command and trust boundaries.