operator pattern
The second agentic pattern where a user opens multiple independent Claude Code terminal windows, each with isolated context, and manually coordinates work across them
As defined in Every Claude Code Workflow Explained (& When to Use Each)
Where it comes up · 1
Most important claims · 4 of 4Search all claims for “operator pattern” →
- The operator pattern involves opening multiple independent Claude Code terminal windows simultaneously, each with its own isolated context window and branch (via git work trees), allowing parallel execution of independent tasks without context interference, where the user acts as orchestrator coordinating across terminals.Every Claude Code Workflow Explained (& When to Use Each)
- The operator pattern can only manage a practical limit of 4-5 terminals simultaneously before terminal-switching becomes difficult and cognitively taxing for a single user.Every Claude Code Workflow Explained (& When to Use Each)
- In the operator pattern, tasks must be independent and not depend on each other for the workflow to be effective; if tasks require sequential dependencies, the operator pattern breaks down.Every Claude Code Workflow Explained (& When to Use Each)
- Closing a work tree session in the operator pattern causes Claude to handle cleanup automatically: if nothing has changed, the workspace is removed; if work exists, Claude asks what to do.Every Claude Code Workflow Explained (& When to Use Each)