codex
Use when operating Codex CLI itself (config, profiles, sandbox, approvals, and safe usage patterns).
When & Why to Use This Skill
The Codex CLI skill is a specialized utility designed to manage and optimize the Codex command-line interface environment. It focuses on streamlining configuration management, ensuring robust security through sandbox controls, and providing standardized troubleshooting procedures. By enforcing safe usage patterns and secret redaction, it enables developers to interact with the Codex ecosystem securely and efficiently.
Use Cases
- Environment Configuration: Setting up and switching between global and project-local environments using CODEX_HOME for isolated development workflows.
- Security & Sandboxing: Implementing 'workspace-write' sandbox restrictions and 'on-request' approval workflows to prevent unauthorized system changes.
- System Troubleshooting: Diagnosing CLI behavior by automatically capturing version data, system status, and configuration files while redacting sensitive API keys.
- Validation & Health Checks: Using built-in execution helpers and feature lists to verify that the CLI toolset is correctly installed and configured for the current task.
| name | codex |
|---|---|
| description | Use when operating Codex CLI itself (config, profiles, sandbox, approvals, and safe usage patterns). |
Operating guidelines
- Prefer safe defaults:
--sandbox workspace-writeand approvalson-requestunless the user explicitly asks otherwise. - Make config changes explicit and minimal (document what changed and why).
- When troubleshooting CLI behavior, capture:
codex --version/statusoutput- relevant config files (e.g.,
config.toml)
- Avoid leaking secrets into logs; redact tokens and API keys.
Common actions
- Validate configuration quickly via
codex exec --helpandcodex features list. - Use
CODEX_HOMEto switch between global and project-local setups.