Dispatch and escalate tmux-based atmux team nudges via /atmux:whip.
npx skills add https://github.com/geoyws/atmux --skill whip
Please help me install this Agent Skill. Skill: whip Source: https://github.com/geoyws/atmux/tree/main/plugins/atmux/skills/whip Command: npx skills add https://github.com/geoyws/atmux --skill whip
Keeps an atmux team moving by repeatedly nudging the lead to dispatch work, escalate only true blockers, and re-arm itself until progress resumes, without the user manually babysitting every 5-minute window.
Tell the system to start the autonomous loop with the command /loop /atmux:whip.
High-intent search queries and answers about installing and using this skill.
Agent orchestration for tmux teams is automated by running an autonomous whip loop that nudges the team lead to dispatch work every five minutes. It adapts re-arm cadence over idle time and only sends Discord pings when true blockers require escalation.
A watchdog liveness check in autonomous coordination is a manual, one-shot diagnostic scan that detects stalled behavior in a tmux team lead. It pages the user through Discord escalation only when progress has genuinely halted and intervention is required.
Cadence scheduling for tmux coordination is configured by reading team context and cadence settings from per-team files, then using ScheduleWakeup to re-arm the loop automatically. You can tune the dispatch cycle speed adaptively or apply manual overrides.
Discord integration is not required for the core autonomous loop to function, but is necessary for escalation. The loop uses a shared ping-discord script to send alerts exclusively when specific blocker conditions are met during team coordination.
You can manually override the adaptive re-arm cadence by using the specific cadence control command. This allows you to tune how quickly the autonomous dispatch loop re-arms per team, overriding the default idle-time adaptation behavior.
You should avoid using an autonomous dispatch loop for team coordination when tasks require continuous manual oversight or lack clear blocker conditions. The loop is designed for ongoing sessions where the lead can work independently and only needs escalation on true blockers.
geoywsManage atmux team lifecycle by starting, stopping, adding members, and refreshing context.
GenproMMCreate, list, and resume persistent context threads for cross-session work.
pmarreckSend markdown notes between Claude Code sessions via shared files and tmux notifications.
ZeiZelCoordinates agent-to-lead communication via five structured message types.
