# Claudex Loop

Harden a plan with independent Claude/Codex review, then optionally build and...

- Repository: https://github.com/chaseai-yt/claudex-loop (3314 stars)
- Category: AI and agents
- License: see repository
- Last updated: 2026-10-14
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add chaseai-yt/claudex-loop --skill claudex-loop -g -a claude-code -y`
Codex: `npx skills add chaseai-yt/claudex-loop --skill claudex-loop -g -a codex -y`
Cursor: `npx skills add chaseai-yt/claudex-loop --skill claudex-loop -g -a cursor -y`
Gemini CLI: `npx skills add chaseai-yt/claudex-loop --skill claudex-loop -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add chaseai-yt/claudex-loop`

## Description

Harden a plan with independent Claude/Codex review, then optionally build and cross-inspect it. Start in either Claude Code or Codex: the host plans and the other provider reviews. Use for claudex this plan, claudex-loop, or the legacy crucible trigger; not for trivial edits.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Claudex Loop

The current conversation owns requirements, planning and coordination. The other provider reviews the plan. Either provider can build; the provider that did not build inspects the final code in a fresh session.

## Resolve roles once

Identify the actual host from your runtime, not PATH, installed skills, model-name guesses, or the repository. Both CLIs may be installed. Use `host=claude` in Claude Code and `host=codex` in Codex. If the runtime identity is unavailable, ask which host the user is using once.

| Host | Requirements and plan | Plan reviewer | Default builder | Final inspector |
|---|---|---|---|---|
| Claude Code | Current Claude session | Codex | Claude | Fresh Codex session |
| Codex | Current Codex session | Claude | Codex | Fresh Claude session |

Honor `builder=claude|codex`. The inspector is always the other provider. The host remains coordinator even when the other provider builds. To swap the planner, start the conversation in the other host; do not pretend a CLI reviewer is the user's planning conversation.

Model selection is independent of provider roles. Preserve the host's selected model. Review/build CLI calls inherit their own configuration unless `reviewer_model`, `builder_model`, or `inspector_model` is supplied; map these to the runner's `--model` for that invocation. Apply an explicit `*_effort` similarly. Fable 5.1 and GPT-6 Astra are suitable explicit choices, not mandatory pins. A model in the host UI does not prove which model a separate CLI will use. Report requested and observed model information separately; report an unresolved CLI default honestly. Never silently fall back to another model/provider on a failure.

Read [the runtime reference](references/runtime.md) before launching a CLI. Resolve its runner relative to this installed SKILL.md, never relative to the project being reviewed. Use absolute paths when launching it.

The rest: https://github.com/chaseai-yt/claudex-loop/blob/HEAD/skills/claudex-loop/SKILL.md