← ClaudeAtlas

claudexorlisted

Use the local Claudexor control plane for harness-agnostic coding work across Claude Code, Codex, Cursor, and OpenCode. Use when a task benefits from route-aware harness and account selection, quota-aware account rotation, shared thread context, read-only planning or research, best-of-N execution, or cross-harness review.
razzant/claudexor · ★ 524 · AI & Automation · score 90
Install: claude install-skill razzant/claudexor
# Claudexor Use the MCP tools supplied by this plugin. They connect to the user's local Claudexor installation; they do not provide accounts or remote model access. ## Preconditions - Support macOS and Linux. Do not claim Windows support. - Require Node.js 20.19 or newer and a preinstalled `claudexor` command. If the MCP server is missing, ask the user to run `npm install -g claudexor`, then restart the host. Do not download a runtime implicitly. - If a generated Claudexor host integration already owns the current host's setup, leave it in place. Do not repair, replace, or uninstall it automatically. ## Choose a route Start read-only unless the user explicitly asked to change or create files. 1. Call `claudexor_status` to inspect the aggregate/default-store projection, but do not use it as a universal admission veto. An unpinned request may be admitted by the canonical account pool through a ready exact profile even when default doctor is unavailable; only a genuinely profile-less/default fallback requires doctor status `ok` and the requested intent. Aggregate status neither proves nor vetoes a pooled or explicitly named profile. 2. Call `claudexor_accounts` before choosing an account or reviewer identity. It is a read-only atomic snapshot of registered profiles, readiness, quota freshness, and the daemon's `next_up` routing projection. `available/passed` on the exact selected row is the usable route evidence; `unknown`, `not_run`, or