Codex uses Palmier and FFmpeg for a multi-step video edit
LLMJunky said Codex used Palmier with FFmpeg to choose frame ranges, speed up a clip, add overlays, animate an icon, and place text. He still handled some zoom effects manually.

TL;DR
- Codex handled a real multi-step video edit: LLMJunky said it chose the cut points with FFmpeg, sped one section up 5x, added an overlay, animated an icon, and placed text in the frame LLMJunky's edit breakdown.
- Palmier was the bridge between Codex and the timeline: LLMJunky told people to connect Palmier's MCP, and Palmier's docs say agents can trim, split, reorder, adjust, and place clips LLMJunky's Palmier note.
- The human still owned part of the finish: LLMJunky said he did the zoom effects himself and still saw color grading as better suited to DVR LLMJunky's follow-up.
- Codex workflow control is part of the same story: LLMJunky separately called out
codex --enable default_mode_request_user_inputas a feature he had pushed for LLMJunky's Codex flag post.
Palmier's docs say the Mac app can connect agents through MCP, with setup instructions for Cursor, Codex, Claude Code, and Claude Desktop. The GitHub README exposes the local MCP endpoint and the exact Codex command. OpenAI's Codex MCP docs say Codex CLI, the IDE extension, and ChatGPT desktop can all use MCP servers on the same Codex host.
Palmier as a timeline MCP
Palmier describes Pro as a macOS video editor where Claude and Codex can read and edit a multi-track timeline. Its docs list three agent actions that matter for this demo:
- Generate images, video, and audio, then place them directly on the timeline.
- Trim, split, reorder, and adjust clips with full project context.
- Rerun or tweak AI-generated clips by prompt.
The Palmier pricing page says the editor and MCP are free with no account required, while credits apply to AI generation.
The FFmpeg cut
LLMJunky's prompt was timing-specific rather than tool-specific:
- Clip the section just after Cerebras finished.
- Stop about 0.5 seconds before the GPUs finished.
- Speed that section up 5x.
- Add the overlay, animation, and icon.
- Place the visual cleanly in the bottom-right of the frame.
The interesting part is frame selection. In LLMJunky's description, Codex “watched the video with FFmpeg” and found the exact frames to slice before applying the speed change and overlays.
Zooms and color grading
LLMJunky drew the human-agent boundary clearly: he did the zoom effects, while Codex handled the speed-up, flashing icon, text, and placement.
Color grading remained outside the agent handoff. In his Palmier note, he said Palmier was strong for editing, while color grading was “still best in DVR.”
The local setup
The Palmier README says the app exposes an MCP server at http://127.0.0.1:19789/mcp when it is open.
For Codex, the README gives this command:
OpenAI's Codex MCP documentation says local Codex clients support STDIO and streamable HTTP MCP servers. Its CLI reference says codex mcp stores server entries in ~/.codex/config.toml.
Codex asking for input
LLMJunky also pointed to a Codex flag: codex --enable default_mode_request_user_input.
OpenAI's CLI reference documents feature flags through codex features, with enable and disable persisting changes into $CODEX_HOME/config.toml. The exact default_mode_request_user_input name comes from LLMJunky's post, not the public reference page.