worker

Coordinate OMX team tasks in tmux by enforcing a worker protocol with ACK flows, mailbox handling, and task lifecycle management. Workers parse identity, read centralized inbox files, claim unblocked tasks, execute work, and report completion back to a durable state store.

The tmux worker ACK protocol is a fixed startup sequence where OMX workers announce readiness to the team leader. Workers parse the OMX_TEAM_WORKER identity variable, read their inbox, claim ordered tasks, and execute work before reporting status transitions back to the state store.

Set the OMX_TEAM_WORKER environment variable to your team-name/worker-n identity, then read your inbox to find the first unblocked task. Workers parse centralized task files, claim work in ordered processing, and write task completion updates to the durable state store.

Yes, OMX team task workflows support orderly shutdown and state recovery to resume after restarts. The protocol uses a durable state store with explicit read/write paths, maintaining mailbox communications and task lifecycle status so workers can recover and continue unblocked tasks.

The OMX worker protocol provides MCP tooling guidance for task lifecycle management, but the core workflow relies on parsing inbox and task files. Workers use explicit read/write paths to claim tasks, execute work, and write completion status back to the centralized state store.

Manage task status transitions by having OMX team workers write completion updates and mailbox communications back to a durable state store. The protocol enforces ordered processing, ensuring workers claim unblocked tasks and report status through explicit read/write paths during the task lifecycle.