Open Orchestrator

Appearance

This workflow shows how to use Open Orchestrator to develop multiple features in parallel, maximizing your productivity.

The Scenario ​

You need to implement several related features:

  • User authentication (JWT)
  • REST API endpoints
  • Integration tests

Instead of doing these sequentially, you'll develop them in parallel.

Step 1: Set Up Worktrees ​

Create isolated worktrees for each feature:

bash
# Authentication feature
owt new "Implement JWT authentication"

# API endpoints
owt new "Build REST API endpoints"

# Integration tests
owt new "Write integration tests"

Each worktree now has:

  • Its own git branch (auto-named from the task description)
  • Installed dependencies
  • tmux session with AI tool ready

Step 2: Delegate Initial Tasks ​

Send initial instructions to each AI session:

bash
# Authentication task
owt send feat/implement-jwt-authentication "Implement JWT authentication with:
- Access token (15min expiry)
- Refresh token (7 day expiry)
- Token rotation on refresh
- Password hashing with bcrypt"

# API task
owt send feat/build-rest-api-endpoints "Create REST API endpoints:
- GET /users - list all users
- GET /users/:id - get user by ID
- POST /users - create user
- PUT /users/:id - update user
- DELETE /users/:id - delete user"

# Testing task
owt send feat/write-integration-tests "Set up integration test framework and create tests for:
- User creation
- User retrieval
- User update
- User deletion"

Step 3: Monitor Progress ​

Open the Control Plane to see all sessions working:

bash
owt

The Control Plane groups each worktree into a prioritized lane (NEEDS YOU / READY TO SHIP / IN FLIGHT), one row per worktree:

open-orchestrator · 3 rows · 14:32:08

IN FLIGHT
  feat/implement-jwt     claude   JWT middleware
  feat/build-rest-api    claude   REST endpoints
  feat/write-integration claude   Test framework

Step 4: Follow Up as Needed ​

Send additional instructions as work progresses:

bash
# Add requirement to auth
owt send feat/implement-jwt-authentication "Also add middleware for protecting routes"

# Update API based on auth progress
owt send feat/build-rest-api-endpoints "Add authentication middleware to all protected endpoints"

# Update tests to include auth
owt send feat/write-integration-tests "Add authentication tests:
- Login success
- Login failure
- Token refresh
- Protected route access"

Step 5: Review and Iterate ​

Attach to each worktree from the Control Plane to review the work:

  1. Open the Control Plane: owt
  2. Navigate to a row with up/down (or j/k)
  3. Press a to attach to that worktree's session
  4. Review the AI's work
  5. Press Alt+s to return to the Control Plane
  6. Navigate to the next row and repeat

Step 6: Coordinate Integration ​

Once individual features are ready, coordinate integration:

bash
# Sync all with main
owt sync --all

# Send integration instructions
owt send feat/implement-jwt-authentication "Export auth middleware for use by other modules"
owt send feat/build-rest-api-endpoints "Import and use auth middleware from auth module"
owt send feat/write-integration-tests "Import both modules and test full integration"

Step 7: Merge ​

When ready to merge, use the two-phase merge:

bash
# Merge base into feature first (catch conflicts)
owt merge feat/implement-jwt-authentication

# Then merge the next feature
owt merge feat/build-rest-api-endpoints

# And the tests
owt merge feat/write-integration-tests

The two-phase merge first merges base into feature (to catch conflicts), then fast-forwards feature into base.

Step 8: Clean Up ​

After merging:

bash
# Clean up merged worktrees
owt cleanup --days 0

Benefits ​

Time Savings ​

Instead of sequential development:

feat/auth (2 hours) -> feat/api (2 hours) -> feat/tests (2 hours)
Total: 6 hours

With parallel development:

feat/auth  ────────────────────
feat/api   ────────────────────
feat/tests ────────────────────
Total: ~2-3 hours (with AI doing the work)

Better Focus ​

  • AI handles implementation details
  • You focus on coordination and review
  • No context switching between features

Consistent Quality ​

  • Same patterns across features
  • Integration tested early
  • Parallel code review

Tips for Success ​

  1. Start with clear requirements -- Be specific in initial instructions
  2. Monitor the Control Plane -- Catch issues early
  3. Iterate quickly -- Send follow-up instructions as needed
  4. Review incrementally -- Don't wait until the end
  5. Coordinate integration -- Plan how features work together

See Also ​