domains / families / agent-tooling / codex-profiles
codex-profiles
authentic
Use codex-profiles to run Codex CLI or Codex Desktop with isolated CODEX_HOME profiles for separate accounts, projects, and local state.
When to use
- Use when the user wants to keep multiple Codex accounts or project contexts separate on one machine.
- Use when a workflow needs a different `CODEX_HOME` without manually exporting environment variables.
- Use when diagnosing which Codex profile is active or whether profiles are logged in.
- Use when the user asks about Codex account switching without copying `auth.json`.
- Use when launching Codex Desktop from a profile, only after confirming the user accepts app/process disruption.
When not to use
- `codex-profiles` is community-maintained and is not an official OpenAI tool.
- It isolates Codex state through separate `CODEX_HOME` directories; it does not isolate the operating-system user, shell history, SSH keys, browser cookies, GitHub CLI auth, or unrelated application state.
- Desktop profile launch behavior is macOS-focused and can change with Codex Desktop releases.
- Existing Codex sessions may still contain project context from before a profile strategy was adopted.
- The tool does not replace backups for important Codex state.
Skill page
Source