Menu
Use codex-profiles to run Codex CLI or Codex Desktop with isolated CODEX_HOME profiles for separate accounts, projects, and local state.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Give an AI agent a permanent network address, encrypted P2P messaging, and an installable app store via Pilot Protocol
A ship gate that runs before any production deploy: checks the silent failure modes that make a deploy 'succeed' while prod stays broken, then verifies the live revision instead of trusting deploy output.
Integrate RouterBase as an OpenAI-compatible model gateway for routing GPT, Claude, Gemini, media, audio, and embedding requests.
Use Tree Ring Memory for local-first AI-agent memory lifecycle work: recall, evidence, audit, forgetting, and consolidation without transcript dumping.
Go in depth harness — fan-out web searches, fetch sources, adversarially verify claims, synthesize a cited report.
Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.
| 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 |
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.
CODEX_HOME without manually exporting environment variables.auth.json.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.
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.
Use the CLI profile wrapper for ordinary agent work:
codex-profile cli work
codex-profile cli work exec "run tests and summarize failures"
For one-off shell sessions, prefer the tool's environment or shell activation commands after checking --help:
codex-profile env work
codex-profile shell-init --help
Codex Desktop launch flows can affect running app state. Before running them, state which profile, app mode, and workspace will be used, then wait for approval.
codex-profile app work ~/Dev/project
codex-profile app work --instance ~/Dev/project
Use --instance only when the user wants side-by-side Desktop profiles and accepts the additional local app clone and separate Electron user-data boundary.
codex-profile list
codex-profile status
codex-profile doctor
Use this before changing profile state. It should not expose token contents.
codex-profile cli work exec "inspect this repository and run its test suite"
Confirm the profile name is intentional before running long tasks.
If the wrapper is unavailable, explain the underlying boundary instead of improvising token movement:
CODEX_HOME="$HOME/.codex-work" codex
CODEX_HOME="$HOME/.codex-work" codex exec "review this change"
work, personal, client-a, or school.status, list, and doctor before destructive or Desktop actions.codex-profile --help, because command flags can change.codex-profiles is community-maintained and is not an official OpenAI tool.CODEX_HOME directories; it does not isolate the operating-system user, shell history, SSH keys, browser cookies, GitHub CLI auth, or unrelated application state.auth.json tokens as a shortcut.codex-profile remove only after confirming the exact profile path and whether the user needs a backup.CODEX_HOME.Problem: A user expects profile switching to isolate GitHub CLI, SSH, or browser state.
Solution: Explain that codex-profiles isolates Codex home state only; check and switch other tools separately.
Problem: A Desktop command disrupts an active session. Solution: Ask before Desktop operations and prefer CLI commands when the user only needs isolated command-line work.
Problem: A profile exists but is logged out or missing connectors.
Solution: Run codex-profile status and have the user log in or configure connectors inside that profile.
@environment-setup-guide - Use when installing or documenting local development tools.@codex-maintenance - Use when maintaining local Codex Desktop, MCP, plugin, or cache surfaces.@filesystem-context - Use when reasoning about local files, config paths, and workspace boundaries.