---
name: setup
description: Check the isolated Claude profile, version, authentication, and required installed-script execution rule. Requires explicit invocation.
---

On non-Windows hosts report that C1 setup and reverse-provider execution are unsupported and stop without Claude diagnostics or data/configuration changes.

Resolve ../../scripts/ccx.mjs from this skill directory's actual installed path. Run exactly one call: node '<canonical absolute installed script path>' setup. On Windows first require the process-local PATH launcher in ../../README.md, excluding WindowsApps components and directories containing pwsh.exe. Once per current Codex process/environment, before bridge/rules execution, verify a harmless node --version command actually uses System32\WindowsPowerShell\v1.0\powershell.exe with -NoProfile and login disabled; a requested shell override alone is insufficient. Reuse the observed successful preflight until the environment changes; then recheck. Stop on another shell. Keep persistent PATH/config unchanged. Then use native PowerShell with login disabled and one literal command starting with node, followed by the canonical absolute installed script path written with backslashes in a single-quoted PowerShell string. Use the same exact path spelling as setup's printed rule; paths that resolve to the same file can still differ for rule matching. Double any embedded apostrophe in a PowerShell single-quoted argument. Quote each path or option value as a literal argument. Do not use the & operator, interpolate request text into shell code, or render an argument array. Never suggest a generic PowerShell allow rule. Return its output verbatim inside one fenced code block. Change no settings, copy no credentials, and install no global agents. The script resolves absolute CCX_CODEX_DATA_DIR, otherwise <CODEX_HOME or ~/.codex>/ccx. Authenticate only the dedicated profile identified in the output, using the printed instructions.

The Windows installed-script rule executes outside the Codex OS sandbox; Claude application permissions do not supply OS confinement. The user adds the exact printed rule after inspecting it. Never broaden the rule to a generic PowerShell allow rule. Linux/macOS reverse-provider execution is unsupported in C1.