Movi already has a real Codex-friendly story today:
In plain language: Codex can help you understand and edit the plan, but it still cannot skip the same review-first safety gate a human uses.
Codex is a good fit for Movi right now because the repo already ships these real pieces:
Movi MCP v1 as a stdio-first local integration surfaceanalyze.create, review_queue.get, manifest.get, manifest.patch_*, review_rule.*, and apply.previewThat means Codex is not being name-dropped as a fantasy partner. The connection exists because the MCP surface already exists.
Use Codex with Movi when you want it to:
Think of it like asking a careful assistant to prepare the checklist, not giving that assistant the keys to drive the moving truck.
Movi does not currently let Codex:
apply.executeoverlay -> resolved snapshot -> dry-run -> executeCodex already ships a first-party MCP command surface, so the shortest current route is:
codex mcp add movi -- bash /absolute/path/to/movi-organizer/tooling/runtime/run_mcp_stdio.sh
If you want to inspect the saved MCP configuration or remove it later:
codex mcp list
codex mcp remove movi
The portable core is still just a stdio command. If you are wiring Movi into a Codex client surface that wants JSON instead of the CLI helper, use:
{
"name": "movi",
"command": "bash",
"args": ["/absolute/path/to/movi-organizer/tooling/runtime/run_mcp_stdio.sh"]
}
If you install the Python package entrypoint, movi-mcp can be used instead of the shell wrapper.