--- name: workflow-mode description: Enable, disable or inspect Agent Workflow routing when the user explicitly asks for workflow mode, ultracode mode, or persistent workflow routing for this session or project. --- Use `node "/bin/launch.mjs" mode on|off|status`. Resolve plugin-root from this installed skill, two parents above its directory. A request to run one workflow uses agent-workflow and does not enable persistent mode. Default to session scope with the real Codex identity from context or CODEX_THREAD_ID; never fabricate one. For explicitly requested project routing, use that project's actual cwd: ```text node "/bin/launch.mjs" mode on --scope session --session "" node "/bin/launch.mjs" mode status --scope session --session "" node "/bin/launch.mjs" mode off --scope session --session "" node "/bin/launch.mjs" mode on --scope project --cwd "" node "/bin/launch.mjs" mode status --scope project --cwd "" node "/bin/launch.mjs" mode off --scope project --cwd "" ``` Keep explicit --data-dir consistent. Otherwise CLI/hooks share AGENT_WORKFLOW_DATA_DIR if set, then LOCALAPPDATA/agent-workflow or home .local/share/agent-workflow. PLUGIN_DATA does not implicitly redirect it. Inspect the result before reporting the requested scope enabled/disabled. Use workflow-setup if installation is missing. Mode is opt-in and persists outside plugin cache. The prompt hook supplies routing context for user prompts; ordinary questions and small direct edits stay conversational. Workers/tool messages are excluded. A status question or steering instruction does not replace the active user objective. Mode grants no file, network, publication or installation permission, and adds no native composer control, effort slider or shared hard budget. Manual CLI/dashboard use does not require mode. Hook trust is separate; report runtime readiness and hook availability independently. Do not edit global AGENTS or Codex settings to imitate routing.