[Done] Understand what would happen if we replaced Codex CLI in the current project with Pi, including the pros and cons.

[YiweiShen]

/codex --fetch --no-pr
https://github.com/badlogic/pi-mono/tree/main/packages/coding-agent
https://github.com/openai/codex

[github-actions]

If you replaced Codex CLI with Pi in this project right now, it would fail immediately without code changes.

What would break immediately

1. The action executes codex-specific commands and flags in src/client/codex.ts, src/client/codex.ts, and src/client/codex.ts:
   • codex login --with-api-key
   • codex ... exec --yolo ...
     Pi has different CLI semantics.
2. The runtime image installs only Codex CLI in Dockerfile.
3. Config/docs/workflow naming is Codex-centric (/codex, codex-env, descriptions in action.yml and docs).

What stays mostly the same

1. GitHub event handling, permission checks, cloning, diff detection, PR/comment posting.
2. Commit message generation via OpenAI API (src/api/openai.ts) is independent of Codex CLI.

Pros of moving to Pi

1. Much broader provider/model support (OpenAI plus many others).
2. Strong extensibility model (skills/extensions/packages) if you want custom behavior later.
3. Multiple run modes (print/json/rpc/sdk) that can be better for machine integration long-term.

Cons / risks for this repo

1. Migration cost: you need a new client adapter, new CLI arg mapping, auth/env mapping, and tests.
2. Behavior drift: output quality/format and tool behavior may differ from current Codex runs.
3. Current preflight model check is OpenAI-only in src/main.ts, so true multi-provider support needs config refactor.
4. Security surface can increase if you adopt third-party Pi packages/extensions (they run with full system access per Pi docs).

Practical assessment

1. Minimal “swap engine but keep OpenAI” migration: moderate effort.
2. Full “provider-agnostic agent backend” migration: larger refactor.

If you want, I can draft a concrete migration diff plan (file-by-file) for a safe phase-1 adapter that keeps existing workflow UX (/codex, PR behavior) while running Pi underneath.