Codex

ACT supports all ACT skills and research agents in Codex by installing Codex-native generated skill copies and generated custom-agent TOML files. Supported hooks are also installed for logging and Dart formatting.

Install

cd ~/.agentic-coding-toolkit && ./scripts/install.sh --tool codex

What Gets Installed

Location	Includes
`~/.codex/skills/`	Generated Codex-compatible ACT skill copies, with auxiliary entries symlinked from canonical ACT skill directories
`~/.codex/agents/`	Generated TOML custom agents
`~/.codex/hooks/`	Copied ACT hook core scripts and Codex adapters
`~/.codex/hooks.json`	ACT-owned Codex hook entries merged with user hooks
`~/.config/agentic-coding-toolkit/`	Shared ACT settings and copied runtime helper

Canonical source skills remain shared with Claude Code, OpenCode, and Cursor. Codex gets generated copies so OpenCode does not discover Codex-transformed skill bodies.

Verify

Start or restart Codex after installing ACT, then use Codex skill discovery:

/skills

You can also mention an ACT skill directly where Codex supports skill mentions:

$act-help
$act-workflow-plan ai_specs/feature-spec.md

Skills

Codex skills are generated into:

~/.codex/skills/<skill-name>/SKILL.md

Generated Codex skills remove unsupported Claude/OpenCode tool wording where ACT’s transformer covers it. Re-run the Codex installer after updating ACT so these generated skill copies are refreshed.

Auxiliary skill entries other than SKILL.md are symlinked from the canonical ACT skill directory into the generated Codex skill directory.

If /skills shows stale ACT wording after reinstalling, restart Codex.

Commands and Agents

Unlike Claude Code and OpenCode, Codex doesn’t support custom slash commands. As a result, act-help and act-update are installed as generated Codex skills:

~/.codex/skills/act-help/SKILL.md
~/.codex/skills/act-update/SKILL.md

As a result, you can invoke them as $act-help and $act-update.

ACT research agents are converted to Codex custom-agent TOML files under:

~/.codex/agents/<agent-name>.toml

These generated agents use Codex custom-agent fields such as name, description, sandbox_mode, and developer_instructions.

Hooks

ACT installs Codex hooks for:

session logging through SessionStart
prompt logging through UserPromptSubmit
supported tool-use logging through PreToolUse and PostToolUse
permission-request logging through PermissionRequest
Dart formatting after supported Codex file edits

Codex hook support has limits:

No ACT statusline support on Codex
No SessionEnd, subagent lifecycle, compact, or full Claude hook-event parity
No policy enforcement: ACT logs permission requests but does not approve or deny them
Hook interception depends on which tools Codex reports to hooks

Session logging is controlled by the shared ACT setting enableLogging in ~/.config/agentic-coding-toolkit/act-settings.json.

Permissions

Codex permissions are controlled by Codex itself rather than an ACT-managed permission file. ACT logs supported PermissionRequest hook events, but it does not approve or deny Codex permission requests.

Update

After updating ACT, rerun the Codex installer:

cd ~/.agentic-coding-toolkit && ./scripts/install.sh --tool codex

Restart Codex if generated skill wording still appears stale.

Uninstall

cd ~/.agentic-coding-toolkit && ./scripts/uninstall.sh --tool codex

Uninstall removes only ACT-owned Codex skills, agents, and hook entries/scripts. It preserves user-owned Codex artifacts and leaves shared ACT settings under ~/.config/agentic-coding-toolkit untouched.

Best Fit

You want to use ACT from Codex
You are comfortable with generated ACT integrations rather than direct slash commands
You accept experimental support limits and simpler interactive clarification flows