/relay:agent — single agent
Use /relay:agent when you need one specific agent’s expertise — no team assembly, no coordination overhead.
/relay:agent {agentId} "{instruction}"Examples:
/relay:agent fe "Refactor the CartItem component"/relay:agent be "Security review the user auth API"/relay:agent qa "Write edge case tests for the login feature"/relay:agent designer "UX improvement proposals for the checkout flow"When to use this instead of /relay:relay
Section titled “When to use this instead of /relay:relay”- You need a quick code review or second opinion on a specific file
- You want architecture analysis or technical advice
- You only need one deliverable (tests, docs, a spec) without the full workflow
- The task is focused enough that spinning up the whole team isn’t worth it
Available agents
Section titled “Available agents”Agents come from your configured pool (.relay/agents.pool.yml). If you specify an agent ID that doesn’t exist, relay will show you the available options.
What the agent gets
Section titled “What the agent gets”The agent works with full project context — its personal memory from previous sessions and the shared project.md summary are both injected into the system prompt automatically.