| name | codex-profiles |
| description | Use codex-profiles to run Codex CLI or Codex Desktop with isolated CODEX_HOME profiles for separate accounts, projects, and local state. |
| category | productivity |
| risk | critical |
| source | community |
| source_repo | Ducksss/codex-profiles |
| source_type | community |
| date_added | 2026-07-08 |
| author | Ducksss |
| tags | ["codex","codex-cli","profiles","code-home","account-isolation","desktop"] |
| tools | ["codex"] |
| license | MIT |
| license_source | https://github.com/Ducksss/codex-profiles/blob/main/LICENSE |
Codex Profiles
Overview
Use codex-profiles when a user wants separate Codex CLI or Codex Desktop contexts for work, personal, school, client, or project-specific activity. The tool wraps Codex's CODEX_HOME support so each profile has its own Codex home directory for auth, config, sessions, connectors, plugins, caches, logs, and local state.
This skill is for profile selection and operational safety around that boundary. It is not an official OpenAI project, and it does not provide full OS-level isolation.
When to Use This Skill
- 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.
How It Works
Step 1: Confirm Scope and Installation
First check whether the user wants CLI-only profile switching or Codex Desktop profile launching. Desktop operations can quit, launch, clone, or rebuild app instances, so get explicit approval before running them.
If the tool is already installed, inspect the live command surface:
codex-profile --help
codex-profile doctor
codex-profile list
codex-profile status
If it is not installed, prefer package-manager installs the user can inspect and control:
npm install -g codex-profile
brew install Ducksss/tap/codex-profile
Do not run remote install scripts automatically. If the user asks for a source install, clone the repository and inspect its install instructions first.
Step 2: Create or Select a Profile
Create a new isolated Codex home only when the user names the intended profile:
codex-profile init work
codex-profile path work
Ask the user to log in once per profile when needed:
codex-profile login work
Do not copy, parse, print, or migrate auth.json tokens between profiles.
Step 3: Run Codex CLI With a Profile
Use the CLI profile wrapper for ordinary agent work:
codex-profile cli work
codex-profile cli work
