Thanks for opening this. I reproduced the failure on Windows with Codex using the current main hook manifest (i-have-adhd v0.1.0) and Node v26.5.0.

Observed

Codex reports:

hook exited with code 1

main/hooks/hooks.json currently contains:

"command": "node",
"args": ["${CLAUDE_PLUGIN_ROOT}/hooks/always-on.mjs"]

The Codex hook runner does not handle this Claude-specific args / ${CLAUDE_PLUGIN_ROOT} combination the same way Claude Code does. In the observed path, only node is executed and the SessionStart JSON on stdin is parsed as JavaScript.

Minimal PowerShell reproduction:

$payload = '{"session_id":"codex-repro","cwd":"C:\\Temp","hook_event_name":"SessionStart"}'
$payload | node

This exits 1:

SyntaxError: Unexpected token ':'
ExitCode=1

If the argument is forwarded literally instead, the same manifest fails with a MODULE_NOT_FOUND path containing ${CLAUDE_PLUGIN_ROOT}.

Expected

The SessionStart hook should invoke hooks/always-on.mjs and exit 0 (silently when the opt-in flag is absent) on Codex/Windows as well as Claude Code.

Minimal Codex-side fix

Putting the complete command in command and using Codex's plugin-root placeholder fixes the failure:

           {
             "type": "command",
-            "command": "node",
-            "args": ["${CLAUDE_PLUGIN_ROOT}/hooks/always-on.mjs"],
+            "command": "node \"${PLUGIN_ROOT}/hooks/always-on.mjs\"",
             "timeout": 5,
             "statusMessage": "Checking i-have-adhd always-on flag..."
           }

If one manifest must remain Claude-compatible, a host-specific entry/adapter may be needed so Claude can keep its existing root variable while Codex receives the complete command.

Verification

With the local diff above:

the SessionStart payload invokes always-on.mjs;
the hook exits 0;
stdout/stderr are empty when .i-have-adhd-always is absent;
two regression checks pass.

The missing opt-in flag is therefore not the cause—the script already treats that case as success. This is related to #70, but the Codex args handling is the additional failure mode here.

The regression appears to have been introduced by d3cba85, which changed the hook from a single command string to separate command and args fields.

hook codex Support #91

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions