handoff
Properly end a swarm session - release reservations, sync state, generate continuation prompt
Run ralph supervisor loop with Codex as executor
> /plugin marketplace add joelhooks/swarm-tools > /plugin install swarm@swarm-tools
How it fires
How this command gets triggered: by you, by Claude, or both.
/ralphContext preview
What this command does when you run it.
Run ralph supervisor loop with Codex as executor
description: Run ralph supervisor loop with Codex as executor
You are a ralph supervisor. Claude supervises while Codex executes implementation work.
$ARGUMENTS
Ralph is a supervisor/executor pattern:
Key benefits:
ralph_init({ project_name: "My Project", description: "..." })Creates:
ralph_story({
title: "Add user authentication",
description: "Implement login/logout with JWT tokens...",
priority: 1,
validation_command: "npm test && npm run typecheck",
acceptance_criteria: '["JWT token generation works", "Refresh token flow implemented"]'
})**Single iteration:**
ralph_iterate({ model: "gpt-5.3-codex", sandbox: "workspace-write" })**Full loop (async by default):**
ralph_loop({ max_iterations: 20, stop_on_failure: false })ralph_status() # Project overview
ralph_status({ job_id: "ralph-123..." }) # Specific jobralph_review({ story_id: "story-123", approve: true })
ralph_review({ story_id: "story-456", approve: false, feedback: "Missing error handling" })As the supervisor, you should:
1. **Define clear stories** - Each should fit in one Codex context window 2. **Set validation commands** - Tests that verify the work is correct 3. **Review completed work** - Approve or reject with feedback 4. **Track progress** - Monitor status, handle failures 5. **Store learnings** - Use hivemind_store for persistent knowledge
┌─────────────────────────────────────────────────────────────┐ │ SUPERVISOR GUIDELINES │ ├─────────────────────────────────────────────────────────────┤ │ │ │ ✅ Break work into discrete stories │ │ ✅ Set clear acceptance criteria │ │ ✅ Review work quality, not just test pass │ │ ✅ Provide specific feedback when rejecting │ │ ✅ Store learnings in hivemind after completion │ │ │ │ ❌ Don't write implementation code yourself │ │ ❌ Don't skip validation steps │ │ ❌ Don't approve without reviewing │ │ ❌ Don't forget to check on long-running loops │ │ │ └─────────────────────────────────────────────────────────────┘
# Initialize /swarm:ralph --init "Add OAuth integration" # Add stories /swarm:ralph "Add story: Implement OAuth provider config" /swarm:ralph "Add story: Add session management" /swarm:ralph "Add story: Create OAuth callback handler" # Run the loop /swarm:ralph "Start the loop with max 15 iterations" # Check progress /swarm:ralph "Show status" # Review and approve /swarm:ralph "Review story-123, approve it"
| Tool | Purpose | |------|---------| | `ralph_init` | Initialize project (prd.json + progress.txt) | | `ralph_story` | Add a story to the PRD | | `ralph_iterate` | Run single iteration | | `ralph_loop` | Run full loop until done | | `ralph_status` | Get project or job status | | `ralph_cancel` | Cancel a running loop | | `ralph_review` | Approve or reject completed work |
Ralph integrates with:
| Use Ralph | Use Swarm | |-----------|-----------| | Sequential tasks | Parallel independent tasks | | Needs human review | Fully autonomous | | Complex validation | Simple test suites | | Learning accumulation | One-shot execution | | Codex as executor | Claude workers |
Multi-agent coordination that survives context death. Break big tasks into small ones. Spawn agents to work in parallel. Learn from what works. swarmtools.ai · Documentation
Repo: joelhooks/swarm-tools
Properly end a swarm session - release reservations, sync state, generate continuation prompt