codex-profiles

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:

cod