Essentials Claude Code

Essentials for Claude Code

Loops, swarms, and teams powered by Claude Code's built-in Task System.

Loop, swarm, and team are three execution modes. Loop runs sequentially. Swarm runs parallel subagents. Team spawns full Claude Code instances with shared contracts via Agent Teams. All use Claude's native task dependencies, ctrl+t progress, and automatic persistence.

Plans define exit criteria. Loops run until tests pass. Done means actually done.

The Problem

The Solution

Quick Start

Zero external dependencies. All three modes enforce exit criteria. Swarm defaults to 3 concurrent workers. Team requires tmux and CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1.

Powered by Claude Code's Task System

Our loop, swarm, and team commands use Claude Code's built-in Task Management System (v2.1.19+).
Ralph TUI and Beads integrate seamlessly. Use Ralph TUI for dashboard visualization. Use Beads for persistent task tracking across sessions.

What We Used Before

The community built Ralph Wiggum loops with workarounds:

- Stop hooks: Shell scripts (.sh files) that ran after each Claude response, grepping output for keywords like "complete" or "done" to decide whether to continue the loop
- External plan files: Markdown files tracking task state since Claude had no built-in persistence
- TodoWrite: Flat task lists with no dependency ordering — tasks could run out of order
- Fresh sessions: Starting new conversations to fight context rot, manually re-establishing state each time

What We Use Now

Claude Code v2.1.19+ provides native tools that replace all of this:

The core loop is unchanged: Plan → Implement → Verify → Loop if fail → Done when pass.

What Tasks Do Well

- Dependency management: Task #3 blocked by #1 and #2 literally cannot start until both complete
- Visual progress:…