call-codex

name	call-codex
description	Open and manage app-server-powered calls between Codex threads. Use when the user asks to call Codex, spin up workers, message a worker, broadcast to a call, check call status, or coordinate multi-thread work in the Codex macOS app.

CALL-CODEX

CALL-CODEX lets Codex coordinate Codex through app-server calls. Treat the macOS Codex app as the primary surface.

Core Rules

• Use call_boot before any other CALL-CODEX action.
• Use call_create to open a named call and create workers.
• Prefer default mode: "worktree" for real repo work; use fork or fresh only when shared-cwd workers are intentional.
• Use call_send for one worker and call_broadcast for everyone on the line.
• Use call_wake to start active work; use call_steer only after a worker has an active turn.
• Use call_interrupt for the worker brake, then inspect call_status.
• Use call_status before summarizing progress; trust its worker_progress block for recent worker output and auto-cleared turns.
• Use call_transcript for final receipts; it imports and caches worker assistant output, and its metadata marks live vs cached, fresh vs stale, and read failures.
• If visibility: "macos_app" reports materialization_required, use call_materialize_macos, then Computer Use to open Codex macOS, create one New Chat per worker, paste the worker prompt, and finish with call_attach_visible_thread.
• Use call_remove_thread to cleanly archive and remove one worker thread from a call.
• Use call_close when the call is done.
• Never call these workflows orchestration in user-facing copy. It is a call.

Style

Be playful, sharp, and operationally precise. "CALL-CODEX lands AGI" is a rallying cry, not a technical claim.

Safety

Keep app-server local to 127.0.0.1. Do not suggest remote listeners for v1. Preserve transcripts and audit state. Treat worktree cleanup as explicit, never automatic.