← ClaudeAtlas

codex-app-linklisted

Create Codex threads and send messages into Codex desktop-app (GUI) threads, then wait for and read their replies, so Claude can orchestrate Codex agents. Use when the user asks to message, direct, steer, start, check on, or hand work to a Codex thread or agent (often given as a thread ID like 01a10323-9edd-...), or to run Codex as a sub-agent.
transcendr/slopware-skills · ★ 40 · AI & Automation · score 73
Install: claude install-skill transcendr/slopware-skills
# Codex App Link `scripts/codex-thread.mjs` drives Codex threads from the terminal. It sends messages through the Codex desktop app, or through the shared app-server daemon for a thread open in a terminal `codex` session, works whether or not the thread is in the foreground, and reads replies from Codex's own session files. By default, output is compact text, to save tokens in an agent's context: - one line of `key=value` scalars; - then the agent's reply (`lastAgentMessage`) as raw, unescaped text. Add `--json` only when you need every field. Do not pipe JSON through `jq` into your context. Errors are one-line JSON on stderr, with exit code 1. Set `CT` to the script inside this skill's base directory, **fresh in every session**: ```bash CT=<skill-base-dir>/scripts/codex-thread.mjs node $CT version # confirms the version and path you are actually running ``` Never reuse a `.../codex-app-link/<version>/...` path remembered from an earlier session or a summary. Plugin updates install side by side, so an old path keeps running the old version and misses its fixes and scripts. **Terminal sessions.** A thread open in a terminal `codex` session is held by the shared local app-server daemon (`~/.codex/app-server-control/app-server-control.sock`), not the app, so the app can never take it over. `send` detects this (`status` shows `loadedInDaemon=true`) and talks to the daemon instead: `--steer` injects into the daemon's active turn, with that turn id as a precondition, a