Dispatcher

Dispatcher

The dispatcher skill, as described in the dispatcher file, is tasked with managing the founder's agent fleet from a single machine by reading every live session and assigning tasks based on permissions. This system is triggered by specific phrases like "dispatch" or "sweep the tabs." It's designed for the founder who juggles over 30 agent tabs, handling 169 messages in a single day with 30 of them being one-word messages and multiple tabs requiring his attention.

Work Where He Can See It

The workflow involves the founder actively overseeing the dispatcher's operations. The system uses PowerShell scripts (pwsh -File <skill>/scripts/open-screen.ps1) to display the current session in a separate window. Before each action, the dispatcher must log its process using scripts/journal.ps1. These logs include steps like look, idea, decide, send, you, and done, providing a transparent narrative of the dispatcher's actions.

The Loop (One Sweep)

The dispatcher begins its loop by executing pwsh -NoProfile -File <skill>/scripts/sweep.ps1 -Open, which reads all tabs and repositories' trunks in 20-75 seconds. This script generates a sweep record and updates the dashboard.html. The dispatcher identifies tabs needing permission and clears them by making decisions and communicating them back.

A key part of the dispatcher's role is ensuring that each workstream has a single owner. When multiple tabs are involved, the dispatcher designates an owner based on context and recent contributions, instructing others to hand over their tasks. Carrying facts between tabs is crucial, ensuring that data updates like number changes or job holds are communicated without the founder having to manually transfer information.

The dispatcher also curates a list of tasks that require the founder's direct involvement. These tasks, which include financial, legal, or client-related matters, are presented with clear instructions and estimated times, ensuring the founder knows exactly where his attention is needed.

Logging and Constraints

Every action taken is logged in the .claude/operations/dispatcher/README.md under the "Dispatch log" section, while metrics are already captured in the sweep log. It's critical for the dispatcher to adhere to its boundaries, avoiding direct work on tabs or making decisions involving money, legal, or client relationships.

The dispatcher serves as a practical solution for managing a high-volume, multi-agent environment, allowing the founder to maintain visibility and control without being bogged down by minutiae.