Append driver-to-lead asks to .atmux/driver-inbox.md with best-effort socket and tmux wake-up.
npx skills add https://github.com/geoyws/atmux --skill tell-lead
Please help me install this Agent Skill. Skill: tell-lead Source: https://github.com/geoyws/atmux/tree/main/plugins/atmux/skills/tell-lead Command: npx skills add https://github.com/geoyws/atmux --skill tell-lead
When you need the team lead to act, you need a reliable way to deliver your request even if tmux panes or sockets aren’t currently listening.
Use case: You are in the driver pane and need to escalate a blocker or request a decision from the lead, and you want it queued durably while also trying to get immediate attention.
Run /atmux:tell-lead <message> while you’re in your driver pane to send your request to the team lead and append it to .atmux/driver-inbox.md.
High-intent search queries and answers about installing and using this skill.
To send a task escalation durably across tmux restarts, append your request to a markdown inbox file while issuing a best-effort socket wake-up. This guarantees message delivery even if the listener pane is offline.
Stateful messaging during listener absence relies on a durable file inbox for message persistence, accompanied by a best-effort socket notification. This approach distinguishes expected listener-absent warnings from actual write failures using exit-code semantics.
Socket pubsub provides a best-effort wake-up nudge to the team lead, while a YAML-logged durable delivery to a markdown inbox file serves as the source of truth. The socket notification only alerts the lead if currently listening.
Yes, appending decision requests to a markdown inbox file ensures data persistence without loss. The file acts as a durable source of truth, capturing all driver asks even if tmux panes or sockets experience downtime.
A best-effort wake-up returns a warning exit-code when the lead listener is absent, which is an expected state and not a real failure. True failure exit-codes are reserved for actual write failures to the durable inbox file.
You need durable task orchestration when workflow escalations or decision requests must survive tmux restarts or listener downtime. Direct messaging fails if the receiving pane is inactive, whereas a durable inbox guarantees eventual processing.
sunilkgraoManage email inboxes via REST API with webhook events.
iani-kuliFetches unread GitHub review-requested notifications for open pull requests.
nateaAutomate Gmail inbox processing with GTD triage and task creation.
roanbrasilImplement NATS Core and JetStream messaging with durable streams and consumers.
