Codex
Code Config prepares a launch folder for Codex and applies the toolkit to a copy of your Codex configuration.
Before you start
Section titled “Before you start”Install and sign in to Codex on this computer, connect Code Config, and choose a toolkit. Configure the coding-app account separately from your code-config.com login.
Open your project
Section titled “Open your project”In the Code Config app, choose your project, toolkit, Codex in a terminal, and account, then launch.
From the project folder:
csc launch codexThis uses the project or workspace default toolkit. A launch syncs changes before starting Codex.
Check your tools
Section titled “Check your tools”Find a selected skill or converted command in Codex and try it. For MCP servers, check their connection status and complete any credential setup.
Hooks require your approval in Codex. Review them before choosing whether to trust them. Continuing without trust leaves them disabled. Changed hooks can require approval again; Code Config does not approve them for you.
What Code Config changes
Section titled “What Code Config changes”A launch copies your config.toml into its folder. Toolkit settings, subagent role files, hook activation, and supported MCP registrations are applied to that copy. Where toolkit settings override your settings, the result identifies the override.
Toolkit settings do not reach your original ~/.codex/config.toml. When the run ends, though, Codex’s own user choices, such as folder trust and hook approvals, can be carried back to your original configuration, without the toolkit-added settings.
| Content | Delivery |
|---|---|
| Skills and agents | Converted to Codex formats; unsupported fields are reported. |
| Commands | Converted to user-invoked skills, not the older prompts folder. |
| Rules, context files, output styles | Combined into AGENTS.md. |
| Hook bundles | Written to hooks.json and enabled in the launch configuration, subject to your trust decision. |
| Supported MCP servers | Registered for this launch with local credential access. |
Limitations
Section titled “Limitations”Plugins, workflows, and marketplace entries are not written as Codex configuration. Hooks on unsupported events are reported and do not run. Converted commands retain their name and description, but some command-specific behavior cannot be represented.
If your existing config.toml cannot be read, the launch stops with the file and error location. Fix that file so the launch keeps its model and permission settings.