amq-cli

Topics in the source

• AMQ CLI
• Start in the correct context
• Receive under a live wake
• Send useful handoffs
• Route the task
• Safety and delivery rules

Use the amq CLI for all queue operations. Never edit Maildir files directly. AMQ transports coordination; the caller or orchestrator still owns task planning, worktrees, approvals, and delivery. Inside coop exec, use the environment as provided and run bare amq commands. Do not override --me or reconstruct the root. Outside it, resolve and export the complete context before reading or sending: For a named session, add --session to amq env. Treat the evaluated context as one terminal bound to one session. Use --session or --project for deliberate routing; do not point a participating command at another queue with a raw --root. If session-start context says wake=live(...), or amq wake check --me --json reports livewake: true with an injection mode other than none, the wake delivers a doorbell for you. Run amq drain --include-body when it fires, then act on the messages. The default drain reads at most 20 messages in filename order, including held mail. After a full batch, check amq list --new --limit 1 and continue with bounded drains as needed; do not assume the inbox is empty. Use --limit 0 only for a known, manageable batch. Urgent hold bypass does not change drain order. Do not r

This is an excerpt. Refer to the complete source and its current requirements.