Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
agentworkforce avatar

Agent Relay

  • 1 installs
  • 784 repo stars
  • Updated August 4, 2026
  • agentworkforce/relay

agent-relay is a Codex skill that coordinates multiple agents through Relaycast for peer-to-peer messaging and lead/worker handoffs.

About

agent-relay is a Codex skill for real-time coordination across multiple agents through Relaycast. It teaches a startup protocol for connecting to a workspace, registering an agent, spawning workers, and exchanging direct messages, channel updates, and thread replies. Developers use it when a Codex lead needs peer-to-peer messaging and shared status tracking with its workers instead of parent-only result collection.

  • Gives Codex a repeatable lead/worker coordination protocol over Relaycast
  • Standardizes ACK, STATUS, BLOCKED, and DONE signaling between agents
  • Auto-configures the Relaycast MCP server, hooks, and a relay-worker agent

Agent Relay by the numbers

  • 1 all-time installs (skills.sh)
  • Ranked #14,102 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
At a glance

agent-relay capabilities & compatibility

Optional RELAY_API_KEY to join a specific Relaycast workspace; a new workspace is auto-created if unset.

Capabilities
multi agent coordination · agent messaging · worker orchestration · mcp integration
Works with
openai
Use cases
orchestration
Runs
Local or remote
Pricing
Bring your own API key
From the docs

What agent-relay says it does

Relay fills the peer-to-peer gap in Codex sub-agent workflows.
SKILL.md
keeping lead and worker state synchronized through ACK, STATUS, BLOCKED, and DONE signals
SKILL.md
npx skills add https://github.com/agentworkforce/relay --skill agent-relay

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs1
repo stars784
Last updatedAugust 4, 2026
Repositoryagentworkforce/relay

What it does

Coordinate multiple Codex agents in real time with lead/worker messaging and ACK/DONE status tracking.

Who is it for?

Codex leads that need to spawn workers and coordinate them over a shared Relaycast message bus.

Skip if: Single-agent tasks with no worker delegation or messaging.

When should I use this skill?

When Codex needs real-time coordination across multiple agents.

What you get

Workers coordinate through Relaycast with a repeatable ACK/DONE protocol and shared status.

  • Configured Relaycast MCP server
  • relay-worker agent template
  • ACK/DONE coordination workflow

By the numbers

  • 6-step startup protocol before substantive work
  • 4 status signals: ACK, STATUS, BLOCKED, DONE
  • 4 relay environment variables

Files

SKILL.mdMarkdownGitHub ↗

Agent Relay

Use this skill when Codex needs real-time coordination across multiple agents. It gives Codex a repeatable workflow for:

  • connecting to a Relaycast workspace
  • spawning relay-aware workers
  • sending direct messages, channel updates, and thread replies
  • keeping lead and worker state synchronized through ACK, STATUS, BLOCKED, and DONE signals

Relay fills the peer-to-peer gap in Codex sub-agent workflows. Codex can spawn and collect worker results, but Relaycast gives those workers a shared message bus so they can talk to the lead and to each other.

Auto-setup

On first activation, this skill auto-configures Codex by running scripts/setup.sh. This adds the Agent Relay MCP server to .codex/config.toml, enables hooks, installs hooks.json, and copies the relay-worker.toml agent definition. No manual setup is required after installing the skill.

Startup protocol

Every relay-connected Codex agent must complete these steps IN ORDER before substantive work:

1. Set up a workspace.

  • If RELAY_API_KEY is set in the environment, call set_workspace_key with that key.
  • If no key is available, call create_workspace to auto-create one. This returns a workspace key — save it for workers.

2. Register as an agent. Call register_agent with your agent name and type: "agent". Use RELAY_AGENT_NAME from the environment if set, otherwise derive a name from the task context (e.g., lead, auth-worker).

3. Tell the user they can follow the conversation live at https://agentrelay.com/observer?key=<workspace_key> (use the workspace key from step 1). This lets them watch all agent messages in real time.

4. Check the relay inbox. Call check_inbox to see if there are any pending messages or task assignments.

5. Send an ACK. If you received a task assignment, send ACK: <one-sentence understanding> to your lead via send_dm. If the assignment is unclear, send BLOCKED: <question> instead of guessing.

6. When the task is complete, send DONE: <summary with evidence> before stopping.

If workspace creation or registration fails, retry once, then report the failure to the user — do not proceed without a relay connection.

Critical rule

Do not assume the current MCP session already has an active Relaycast workspace. Always call set_workspace_key or create_workspace before registering.

Working rules

  • Include as: "<agent-name>" on relay calls that support explicit attribution.
  • Keep the relay identity stable for the whole task. Do not switch names mid-task.
  • Check the inbox again after meaningful milestones, before long-running work, and before stopping.
  • Prefer direct messages for lead/worker coordination. Use channels only when multiple agents need the same update.
  • Keep status messages short, factual, and scoped to the assigned work.
  • Do not spawn additional relay workers unless the lead explicitly asks for more delegation.
  • If the lead updates the task, follow the newest explicit instruction.

Message templates

  • ACK: I understand the assignment and I am starting work on <scope>.
  • STATUS: Finished <milestone>; next I am doing <next-step>.
  • BLOCKED: I cannot continue because <blocker>.
  • DONE: Completed <scope>. Evidence: <files changed, commands run, tests, or decisions>.

Two kinds of workers

There are two ways to create workers. Use the right one for the job:

Relaycast workspace agents (preferred for messaging tasks)

Use add_agent to create a Relaycast-native agent. Best for tasks that are primarily about messaging, inbox checks, coordination, or lightweight work that doesn't need a full Codex sub-agent runtime.

Lead steps:

1. Ensure workspace exists (set_workspace_key or create_workspace). 2. Register the lead (register_agent). 3. Add the worker with add_agent(name: "worker-name", type: "agent"). 4. Send the assignment via send_dm(to: "worker-name", text: "..."). 5. Poll lead inbox for ACK (check_inbox).

Worker steps:

1. Check inbox (check_inbox). 2. Send ACK to lead via send_dm. 3. Perform the assigned scope. 4. Send DONE to lead via send_dm.

Codex sub-agents (for code-heavy tasks)

Use spawn_agent with the relay-worker agent definition for tasks that need full code editing, file access, and tool use. The worker gets its own Codex runtime with Relaycast MCP tools available.

Lead steps:

1. Ensure workspace exists and lead is registered (same as above). 2. Spawn the worker: include relay name, lead name, workspace key, exact scope, and completion criteria in the task prompt. 3. Poll lead inbox for ACK.

Worker steps:

1. Call set_workspace_key with the workspace key from the task prompt. 2. Register with register_agent. 3. Check inbox, send ACK, do work, send DONE.

Worker ACK fallback

If a worker does not ACK within 30 seconds:

1. Check whether the worker appears in list_agents. 2. If not listed, register or add the worker directly with add_agent. 3. Send (or re-send) the assignment via send_dm. 4. Poll the lead inbox again for ACK. 5. If still no ACK after a second attempt, report the exact failed step to the user.

Handoff template

Worker: api-worker
Type: relay workspace agent (use add_agent, not spawn_agent)
Lead: lead
Scope: check the Relaycast inbox and confirm connectivity
Protocol:
  1. Check inbox
  2. DM lead with ACK
  3. Perform scope
  4. DM lead with DONE

For code-heavy tasks, change the type line to:

Type: Codex sub-agent (use spawn_agent with relay-worker)

Related skills

FAQ

What does agent-relay set up on first activation?

It runs scripts/setup.sh to add the Agent Relay MCP server to .codex/config.toml, enable hooks, install hooks.json, and copy the relay-worker.toml agent definition.

What are the two kinds of workers?

Relaycast workspace agents (add_agent) for messaging-heavy tasks, and Codex sub-agents (spawn_agent with relay-worker) for code-heavy tasks.

AI & Agent Buildingagentsautomation

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.