2 pointsby shashimudunuri4 hours ago1 comment
  • shashimudunuri4 hours ago
    Author here. I built this to solve a simple problem: Claude Code is great, but it works sequentially. Complex features that touch auth, API, and frontend mean waiting through each step or dealing with merge conflicts.

      This tool spawns parallel Claude sessions, each in its own git worktree with its own branch. Avoids merge conflicts.
    
      Basic usage:
    
          /spawn auth "implement login"
          /spawn api "build REST endpoints"
          /spawn tests "write test suite"
    
      Each command opens a new iTerm tab, creates a worktree, and starts Claude with the task.
    
      There's also a fully automated mode — an orchestrator loop that initializes workers, handles prompts, monitors CI, runs code reviews, and auto-merges when checks pass.
    
      Technical details:
      - macOS only (uses AppleScript for iTerm2 tab automation)
      - Git worktrees for isolation
      - State machine tracks worker progress (NEEDS_INIT → WORKING → PR_OPEN → MERGED)
      - Built-in review agents before merge
    
      Based on patterns from Boris Cherny (bcherny), who created Claude Code at Anthropic.
    
      Happy to answer questions about the implementation.