Publishes messages to topics for inter-agent handoffs, notifications, broadcasts across hive sessions using `hive msg pub` CLI with flags for message, file, stdin, wildcards.
From hivenpx claudepluginhub colonyops/hive --plugin hiveThis skill uses the workspace's default tool permissions.
references/troubleshooting.mdDesigns and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Enables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Send messages to other agents, broadcast to multiple sessions, or publish notifications to topic-based channels.
Messages are published to named topics. The sender is auto-detected from the current hive session context. Each message includes sender ID, timestamp, content, and topic(s).
Output: JSON confirmation line with status, resolved topics, and sender.
hive msg pub --topic <topic> -m "message content"
Examples:
# Send to specific agent's inbox
hive msg pub --topic agent.abc123.inbox -m "Task completed, ready for review"
# Send to multiple topics
hive msg pub -t agent.123.inbox -t agent.456.inbox -m "Important update"
echo "Status update" | hive msg pub --topic notifications
cat report.txt | hive msg pub --topic reports
hive msg pub --topic agent.abc.inbox -f handoff-context.md
hive msg pub --topic <topic> "message content"
Note: Prefer -m over positional args to avoid flag collision with single-character messages.
# Broadcast to all agent inboxes
hive msg pub -t "agent.*.inbox" -m "System maintenance in 5 minutes"
Wildcard * matches any characters within a segment. Topics are expanded at publish time.
Only one source may be used per publish:
-m / --message flag (recommended)-f / --file flagAn error is returned if multiple sources are provided.
Agent inboxes follow: agent.<session-id>.inbox
# Find session IDs
hive ls
# Send to specific agent
hive msg pub --topic agent.abc123.inbox -m "Message"
Create any topic name for specific use cases:
hive msg pub --topic deploy.started -m "Deployment initiated"
hive msg pub --topic build.events -m "Test suite running"
agent.<id>.inbox - Direct messages to agents<domain>.<event> - Event notifications (build.started, test.failed)<feature>.<channel> - Feature-specific channelsAvoid generic names, special characters besides ., -, _.
# Complete work and notify next agent
hive msg pub --topic agent.xyz789.inbox -m "Auth implementation complete. See PR #123. Tests passing."
hive msg pub \
-t agent.abc.inbox \
-t agent.xyz.inbox \
-t coordinator.updates \
-m "Feature X ready for review"
go test -v ./... | hive msg pub --topic test.results
hive msg pub --topic test.channel --sender "custom-agent-id" -m "Test message"
For troubleshooting, advanced patterns, and coordination workflows, see:
references/troubleshooting.md - Common issues and solutions/hive:inbox - Check inbox for messages/hive:wait - Wait for messages with timeout/hive:session-info - Get session details and inbox topic