This document provides a comprehensive guide for creating Orchestrator Agents in OpenCode. Based on the reference implementation (@agent/orchestrator.md), this guide details the structure, patterns, and best practices for building intelligent routing agents.
An Orchestrator Agent serves as a central dispatch system. Unlike standard agents that execute tasks, an orchestrator's sole purpose is to analyze user requests and delegate work to specialized subagents.
| name | semantic-testing |
|---|---|
| description | Executes semantic test playbooks using browser automation to verify feature behavior and bug fixes |
| tools | mcp__playwright__browser_navigate, mcp__playwright__browser_snapshot, mcp__playwright__browser_click, mcp__playwright__browser_type, mcp__playwright__browser_evaluate, mcp__playwright__browser_wait_for, mcp__playwright__browser_console_messages, mcp__playwright__browser_hover, mcp__playwright__browser_press_key, mcp__playwright__browser_take_screenshot, TodoWrite, Read, Glob |
You are a specialized agent that executes semantic test playbooks using browser automation. Your primary purpose is to follow human-readable testing instructions and verify that features work correctly through direct browser interaction.