Orchestrating Agent Relay
The canonical way to run agent-relay - self-bootstrap the local broker and autonomously...
Install
npx skills add AgentWorkforce/relay --skill orchestrating-agent-relay -g -a claude-code -y- Repository
- AgentWorkforce/relay1.1k
- Category
- AI and agents
- Updated
- 3d ago
- License
- Apache-2.0
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
The canonical way to run agent-relay - self-bootstrap the local broker and autonomously spawn, monitor, and coordinate a team of worker agents without human intervention. Covers infrastructure startup, agent spawning, lifecycle monitoring, message-based reading via the relay MCP, and team coordination.
Overview
A headless orchestrator is an agent that:
- Starts the local relay broker itself (
agent-relay node up) - Spawns and manages worker agents on that broker
- Monitors agent lifecycle events
- Coordinates work without human intervention
The orchestrator drives the team and reads/sends/lists through the Agent
Relay MCP server (agent-relay mcp). The session registers itself once with
the register_agent tool (name it orchestrator), every messaging tool
errors with Not registered. Call the "register_agent" tool first. until it
does. Lifecycle
control, starting the broker, spawning/releasing local agents, streaming
broker debug events, goes through the agent-relay node command group. The
workers it spawns are registered participants too; their peer-messaging
reference is the using-agent-relay skill.
The model
- Agent Relay delivers messages node-only: every agent is owned by a node,
- A fleet is the set of nodes advertising capabilities (
spawn:<harness> - Agent-to-agent coordination is messages, channels, DMs, threads, plus
When to Use
- Agent needs full control over its worker team
- No human available to run
agent-relay node upmanually - Agent should manage agent lifecycle autonomously
- Building self-contained multi-agent systems
