What problem does it solve?
It prevents tmux-based Omagy team workers from drifting out of sync by standardizing how each worker identifies itself, reads inbox/mailbox messages, claims tasks, performs work, and records durable lifecycle evidence through the team API.
Core Features & Use Cases
- Deterministic startup ACK: Sends a one-time initialization acknowledgement to the leader mailbox before doing any task work.
- API-driven team state: Reads and writes all team state exclusively via omagy team api to avoid corrupting runtime JSON files under .omagy/state/team.
- Task lifecycle with claims: Lists tasks, claims an eligible task, transitions status using a claim token, and records PASS/FAIL evidence in the transition result.
- Durable mailbox workflow: Treats mailbox messages as durable state, marking delivery after handling and optionally sending concise updates back to the leader.
- Heartbeat and graceful shutdown: Records heartbeat evidence during long work and acknowledges shutdown requests safely.
Quick Start
Start a tmux Omagy team worker session with OMAGY_TEAM_WORKER set to <team-name>/worker-<n>, then run the worker protocol by using omagy team api to ACK startup, pull available tasks, claim one, transition it to completed, and mark any mailbox messages delivered.
