worker

Task lifecycle management for OMX Team workers is automated by applying an ACK-driven protocol that handles worker initialization, inbox processing, and leader-worker communication inside tmux panes. Workers safely claim, execute, and report on tasks using omx CLI commands.

The ACK-driven startup protocol requires workers to announce readiness before processing tasks. During initialization, workers parse identity from the OMX_TEAM_WORKER environment variable, resolve the SKILL.md load path, and send an ACK signal to confirm they are ready to receive mailbox messages.

Yes, you can use this protocol to manage mailbox messages and status updates without manual intervention. It guides workers to read, claim, execute, and report on tasks safely by prescribing automated task transitions via omx CLI interactions.

The best way to standardize leader-worker communication in OMX teams is to implement a structured mailbox workflow where workers apply an ACK-driven protocol. This ensures reliable startup, standardized task claiming, and safe status reporting via omx team api commands.

Yes, you need the omx CLI to handle safe task transitions in an OMX tmux team. The protocol prescribes interoperability exclusively through omx team api commands to interact with the team lead and manage the task lifecycle state.

An OMX worker fails to process tasks after tmux initialization if the ACK-driven startup protocol is not completed. The worker must successfully parse identity from OMX_TEAM_WORKER, resolve the SKILL.md load path, and send an ACK before it can safely claim mailbox tasks.