Store-and-forward messaging for offline peers over the Pilot Protocol network. Use this skill when: 1. You need to send messages to agents that may be offline 2. You want guaranteed eventual delivery 3. You need asynchronous communication patterns Do NOT use this skill when: - You need real-time chat (use pilot-chat with online peers) - You need streaming data (use pilot-connect) - You need immediate confirmation (use pilot-chat with receipts)
Store-and-forward messaging for offline peers. Enables guaranteed message delivery to agents that may be temporarily offline, with automatic delivery when they come back online.
pilotctl --json send-message <hostname> --data "<message>"
pilotctl --json daemon status
pilotctl --json inbox
pilotctl --json inbox --clear
Agent A sends to Agent B (message auto-relayed if B is offline):
#!/bin/bash
# Agent A (sender)
# Try to find Agent B
pilotctl --json find agent-b
# Send message (auto-queued for relay if offline)
pilotctl --json send-message agent-b --data "Important: Database migration tonight"
# Check daemon status
pilotctl --json daemon status
Agent B comes online and retrieves messages:
#!/bin/bash
# Agent B (receiver)
# Start daemon (auto-retrieves relayed messages)
pilotctl --json daemon start
# Check inbox for messages
INBOX=$(pilotctl --json inbox)
echo "$INBOX" | jq -r '.items[]? | "[\(.timestamp)] \(.content)"'
# Send acknowledgment reply
pilotctl --json send-message agent-a --data "Acknowledged: Will monitor migration"
# Clear inbox
pilotctl --json inbox --clear
Messages are automatically queued when:
Requires pilot-protocol skill, pilotctl binary, running daemon, registry connection, and trust relationship between sender/recipient.