v0.5.1: Codex path after ChatGPT 26.924

Version 0.5.1 fixes Computer Use after the ChatGPT 26.924 update, and makes the ChatGPT component paths configurable.

Fix

ChatGPT 26.924 moved the Codex app-server from Contents/Resources/codex to Contents/Resources/codex-cli/CodexCLI.app/Contents/MacOS/codex. Version 0.5.0 looked only at the old path, so every call failed with "Signature verification failed for codex". This release uses the new location and falls back to the old one on earlier ChatGPT builds.

Configurable paths

If ChatGPT is installed elsewhere or moves these files again, set either path in config.json in the state directory:

{
  "codexPath": "/Applications/ChatGPT.app/Contents/Resources/codex-cli/CodexCLI.app/Contents/MacOS/codex",
  "computerUseAppPath": "/Users/me/.codex/computer-use/Codex Computer Use.app"
}

• The adapter reads the file each time a Computer Use session starts, so changes apply without restarting Pi or the MCP server.
• Configured binaries must pass the same OpenAI signature and Team ID checks as the defaults.

Clearer errors

• A missing component is now reported as "not found". The message lists the paths checked and the config file to edit. "Signature verification failed" now appears only when a signature check actually fails.
• /computer-use-status and codex-computer-use-mcp --status show the config path and the current error.

Upgrade

pi install npm:codex-computer-use-mcp@0.5.1

npx codex-computer-use-mcp@0.5.1

Validation

• Strict Oxlint, core and Pi type checks, and 59 tests pass, including the live signed-broker test on ChatGPT 26.924.22138. That test fails on 0.5.0.
• In a Pi end-to-end run, the model used computer_use with the default paths.
• Given a stale codexPath, the model read the error, found the correct binary, updated config.json and succeeded on its next call without restarting Pi.

Compare v0.5.0 to v0.5.1

Upgrade to v0.5.2: 0.5.1 rejects config.json files written by versions before 0.5.