caolisted

# CAO Treat activation as the user's continuing preference for **this conversation**. Keep Codex responsible for requirements, task boundaries, acceptance, and integration; use CAO to delegate development work to the user's configured coding agents. Ordinary questions and planning requests do not start workers. ## Locate the installation and conversation Resolve this skill's directory from the loaded `SKILL.md`. Run `node "<skill-directory>/scripts/cao.mjs" --paths` to locate the CAO checkout and guides. That wrapper works from any project directory and resolves installed symlinks. Use the wrapper for subsequent CAO commands; keep the working directory at the user's target project. Use `CODEX_THREAD_ID`, then `CODEX_SESSION_ID`, as the conversation identity when available. Pass `--thread ID` explicitly if the runtime provides the current conversation ID another way. If no native ID is available, generate one UUID for this conversation and retain it in handoff notes for subsequent commands. Never use a project path, another conversation's ID, or a fresh UUID on every turn as the identity. Use one CAO state directory outside the target project. Honor a state directory already associated with this conversation; otherwise use the CLI default. Pass `--state-dir PATH` consistently when using a custom location. ## Activate, inspect, or turn off - For a bare CAO invocation, `/CAO`, `$cao`, or an explicit request to enable the workflow, run `mode enable`. Preserve existing proj