CLROOM does not replace Codex. It launches the installed codex CLI.

The clean launch supports both interactive clroom codex ... and non-interactive clroom codex exec ... through the existing CLROOM isolation path. The native --ignore-user-config capability is specifically preflighted and injected for exec; its absence on the TUI path is not an interactive refusal reason.

Codex can combine global instructions with project instructions

OpenAI documents a global instruction layer under CODEX_HOME and a project instruction chain discovered from the repository root toward the current working directory.

That persistent layering is useful for personal defaults.

It also creates the exact class of question CLROOM is designed to make easier to test: is this behavior coming from the repository and task, or from personal-global instructions that normally join every Codex session?

Current CLROOM blocks the known global Codex AGENTS.md / AGENTS.override.md inputs for its clean launch while leaving project context available.

CODEX_HOME vs CLROOM

OpenAI documents CODEX_HOME as the way to point Codex at a different home/profile.

Use another CODEX_HOME when you want a persistent alternate Codex configuration.

CLROOM is useful when you want a repeatable per-launch clean/selective setup without maintaining a second normal Codex home or rewriting the one you already use.

Codex profiles vs CLROOM

Codex profiles are useful for reusable configuration values.

That is not automatically the same problem as controlling which personal-global instructions and skill contents can participate in a session.

Use a profile when a profile solves the actual problem. Use CLROOM when the problem is per-launch composition of known personal-global inputs.

Skills are separate from AGENTS.md

OpenAI documents Codex skills at repository, user, admin, and system locations.

For example, the documented user location is $HOME/.agents/skills, while admin skills can live under /etc/codex/skills.

CLROOM’s selected-skill workflow is about personal-global skills admitted for one launch. It should not be described as controlling every admin/system skill or every managed Codex mechanism.

For practical workflows, see Use cases and Skill sets.

Can I disable a Codex skill natively?

Yes. OpenAI documents skill configuration that can disable local skills persistently.

That may be the simpler answer when the desired change is permanent.

CLROOM is aimed at session-specific selection without editing the normal setup.

What does codex exec --ignore-user-config do?

Codex provides codex exec --ignore-user-config as a native non-interactive way to suppress user configuration for an exec task. Use it directly when that broad suppression is exactly what you need.

CLROOM preflights this capability and injects the flag for its qualified codex exec path, while preserving its selective filesystem restrictions and selected-skill inventory. Interactive Codex uses the same existing isolation path without that exec-only flag.

Is CLROOM a way around managed Codex controls?

No.

Administrator-managed behavior belongs to a different control plane from the personal-global material CLROOM is designed to filter. CLROOM should never be marketed as a way around organization policy.

Official OpenAI sources

The developers.openai.com Codex URLs can redirect to their current ChatGPT Learn canonical pages.

Last verified against current OpenAI documentation: 2026-09-07.