Comparison
Loop Engineer does not replace Claude Code or Codex CLI. It orchestrates them — and adds the structure a single agent session does not have.
Loop Engineer vs. a normal Claude Code session
A long agent chat mixes discovery, implementation, testing, and approval in one context. Loop Engineer splits those responsibilities and gives each phase a narrow contract.
| Concern | Single agent session | Loop Engineer |
|---|---|---|
| Agent access | One agent with one permission level for everything | Read-only roles inspect the repository; writing roles edit only an isolated worktree |
| State between steps | One growing chat transcript | Schema-validated JSON handoffs; transcripts never become workflow state |
| Command execution | Agent proposes shell commands as it goes | Local tester runs only configured allowlisted commands, without a shell |
| Definition of done | The model decides it is finished | Tests and review findings must satisfy explicit quality gates |
| Result | Edits land directly in your working tree | Markdown report, JSON report, and a reviewable worktree — no commit, no push |
| Review | Same context that wrote the code approves it | A separate reviewer role and final judge evaluate the diff |
Loop Engineer vs. Codex CLI
Codex CLI is one of Loop Engineer's providers, not a competitor. Used directly, Codex CLI gives you a capable single-agent session. Loop Engineer assigns Codex CLI (and Claude Code) to specific roles inside a controlled loop:
- You can mix providers per role — for example Codex as implementer and Claude as reviewer — so the code is never approved by the model that wrote it.
- Each role gets the minimum permission it needs: read-only for analysis and review, worktree-write for implementation.
- A local, deterministic command runner — not the model — executes your test suite and reports results into the loop.
- Provider-signaled session limits are detected and classified as provider unavailability, so a run fails cleanly instead of silently degrading.
When a plain session is the better tool
For a quick question, a one-line fix, or exploratory work, a direct Claude Code or Codex session is faster and entirely sufficient. Loop Engineer earns its overhead when a task needs implementation and verification: a feature with tests, a refactor that must keep the suite green, or changes you want reviewed before they touch your branch.
Next: read how the loop works or the FAQ.