codex-remote-controllisted

# codex-remote-control Watch and address running Codex CLI sessions. **Why this exists:** Codex has no remote control. Claude Code does. Used from a Remote Control session, this skill lets someone drive their Codex runs from the Claude Code app on their phone — Codex inherits a capability it lacks by being proxied through Claude. That shapes how to use it. The person asking is often not at the machine, may be on a phone, and wants a decision-shaped answer: is it working, is it stuck, is it out of budget, what did it just do, should I redirect it. Lead with that, not with raw output. Codex appends every session to a JSONL **rollout** file under `~/.codex/sessions/YYYY/MM/DD/` and keeps metadata in `~/.codex/state_<N>.sqlite`. Reading the rollout tail is near-live: in testing its last entry was 16 seconds old. Sending goes the other way, through `codex queue`. ## Usage ```bash # Use an absolute path — this breaks from a subdirectory otherwise. S="${CLAUDE_SKILL_DIR}/codex_session.py" python3 "$S" list # every session — find the one you want python3 "$S" list --titles # with each session's opening prompt python3 "$S" list --running-only # only live ones python3 "$S" meta # what this session was asked to do python3 "$S" status # what is it doing right now python3 "$S" status --messages 5 --full # untruncated messages AND commands python3 "$S" status --commands 20 # longer comma