codex

Delegate coding tasks to OpenAI Codex CLI with multi-node profiles and cron integration.

6|1|Updated May 11, 2026
One-click install
npx skills add https://github.com/yakeworld/Synthos --skill codex-yakeworld
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codex
Source: https://github.com/yakeworld/Synthos/tree/main/skills/extended/external-automation/automation-skills/autonomous-ai-agents/codex
Command: npx skills add https://github.com/yakeworld/Synthos --skill codex-yakeworld

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @openai/codex, and includes references (resource) components.

What problem does it solve? Coordinating autonomous coding work across multiple model nodes is error-prone: Codex CLI refuses to run outside git repositories, tmux interactions silently drop Enter keypresses, and incompatible model providers cause cryptic 401 failures. This Skill encodes the operational rules for running Codex CLI reliably as a primary coding agent. ## Core Features & Use Cases - Multi-Node Parallel Execution: Route independent tasks to different vLLM nodes via -p <profile> flags (default, amax, hermes, fallback) for parallel batch work like fixing multiple issues in separate git worktrees. - Cron and No-PTY Automation: Run codex exec with the prompt as a CLI argument inside bash scripts, enabling scheduled coding tasks without an interactive terminal. - Failure Prevention Rules: Built-in guardrails covering git-repo requirements, tmux send-keys splitting, --yolo sandbox risks, and the OpenAI Responses API-only constraint (DeepSeek and OpenRouter are incompatible). - Use Case: You need to fix issues #78 and #99 overnight. Create two git worktrees, launch codex --yolo exec on the default node and codex -p hermes --yolo exec on the hermes node in the background, then push both branches and open PRs in the morning. ## Quick Start Ask the agent to run a one-shot coding task such as adding a dark mode toggle in your git repository using Codex CLI on the default node.

Frequently Asked Questions about codex

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run Codex CLI for one-shot coding tasks?

Use `codex exec "task description" --yolo` inside a git repository. The exec subcommand runs once and exits when done; add `--full-auto` for sandboxed auto-approval or `--yolo` for no sandbox and no approvals on trusted tasks.

How do I run Codex CLI tasks in parallel on multiple nodes?

Assign each task a different profile with the `-p` flag, such as `codex -p hermes exec "task" --yolo` in the background. Each profile file in ~/.codex/ points to a different vLLM node, so tasks run as independent processes on separate endpoints.

Can I use DeepSeek or OpenRouter with Codex CLI?

No. Codex CLI only supports the OpenAI Responses API (`wire_api = "responses"`), while DeepSeek and OpenRouter expose only chat/completions endpoints, causing 401 errors. Use OpenCode or a cron agent provider for those models instead.

Why does Codex CLI freeze when I send commands through tmux?

Codex's TUI needs Enter as a separate keypress. Sending the instruction and Enter in one `tmux send-keys` call makes Enter a literal character, so the command never submits. Send the text and Enter as two independent send-keys calls.

Why does Codex CLI fail with 'not a git repository'?

Codex refuses to run outside a git repository by design. For scratch work, create a temporary repo first with `cd $(mktemp -d) && git init`, then run your codex exec command inside it.

How do I schedule Codex CLI tasks with cron?

Write a bash script with `#!/bin/bash` and `set -euo pipefail`, cd into the project directory, and call `codex exec` with the prompt passed as a CLI argument. No PTY is needed; run it via `bash script.sh` in the cron job.