Skip to main content
import { Panel } from "smithers-orchestrator";

​
Props

PropTypeDefaultDescription
idstring"panel"ID prefix for generated task ids.
panelistsPanelistConfig[] | AgentLike[](required)Specialist agents. Each entry is { agent, role?, label? } or a bare AgentLike.
moderatorAgentLike(required)Agent that synthesizes all panelist outputs into a final result.
panelistOutputOutputTarget(required)Output schema for each panelist task.
moderatorOutputOutputTarget(required)Output schema for the moderator synthesis task.
strategy"synthesize" | "vote" | "consensus""synthesize"How the moderator combines results. "synthesize" merges freely; "vote" counts agreement; "consensus" requires convergence.
minAgreenumberundefinedMinimum panelists that must agree (used with "vote" and "consensus" strategies).
maxConcurrencynumberInfinityMaximum panelists running in parallel.
skipIfbooleanfalseSkip the entire panel. Returns null.
childrenstring | ReactNode(required)Prompt or input sent to every panelist.

​
Basic usage

<Workflow name="code-review-panel">
  <Panel
    panelists={[
      { agent: securityAgent, role: "Security Reviewer" },
      { agent: qualityAgent, role: "Code Quality Reviewer" },
      { agent: architectureAgent, role: "Architecture Reviewer" },
    ]}
    moderator={moderatorAgent}
    panelistOutput={outputs.review}
    moderatorOutput={outputs.synthesis}
  >
    Review the changes in src/auth/ for security, quality, and architecture concerns.
  </Panel>
</Workflow>
This renders as:
  1. Three panelist tasks run in parallel, each receiving the same prompt.
  2. A moderator task runs after all panelists complete, receiving their outputs via needs.

​
Voting strategy

Use strategy="vote" with minAgree to require quorum: 
<Panel
  panelists={[
    { agent: reviewer1, role: "Reviewer A" },
    { agent: reviewer2, role: "Reviewer B" },
    { agent: reviewer3, role: "Reviewer C" },
  ]}
  moderator={moderatorAgent}
  panelistOutput={outputs.review}
  moderatorOutput={outputs.verdict}
  strategy="vote"
  minAgree={2}
>
  Should we approve this RFC? Evaluate the proposal and vote approve or reject.
</Panel>
The moderator receives the vote strategy and minimum agreement threshold in its prompt context.

​
Consensus strategy

Use strategy="consensus" to require panelists to converge on a shared answer. The moderator checks whether panelists agree and, if minAgree is set, enforces a minimum threshold: 
<Panel
  panelists={[
    { agent: analyst1, role: "Risk Analyst A" },
    { agent: analyst2, role: "Risk Analyst B" },
    { agent: analyst3, role: "Risk Analyst C" },
  ]}
  moderator={moderatorAgent}
  panelistOutput={outputs.assessment}
  moderatorOutput={outputs.consensus}
  strategy="consensus"
  minAgree={3}
>
  Assess the risk level of deploying the new payment gateway to production this week.
</Panel>
The moderator receives the consensus strategy and threshold in its prompt context, and is responsible for determining whether the panelists have converged.

​
Bare agent shorthand

When you don’t need per-panelist roles, pass an array of agents directly: 
<Panel
  panelists={[agent1, agent2, agent3]}
  moderator={moderatorAgent}
  panelistOutput={outputs.review}
  moderatorOutput={outputs.synthesis}
>
  Analyze the quarterly report for discrepancies.
</Panel>
Each agent is auto-labeled panelist-0, panelist-1, etc.

​
Limiting concurrency

<Panel
  panelists={specialists}
  moderator={moderatorAgent}
  panelistOutput={outputs.review}
  moderatorOutput={outputs.synthesis}
  maxConcurrency={2}
>
  Review the deployment plan.
</Panel>
At most two panelists run at a time. The rest queue until a slot opens.

​
Generated structure

<Panel> is a composite component. It does not create a new host element type. Internally it renders: 
Sequence
  Parallel (maxConcurrency)
    Task (panelist 0)
    Task (panelist 1)
    ...
  Task (moderator, needs: all panelist ids)

​
Notes

  • Each panelist task id is {prefix}-{label|role|panelist-N}. The moderator task id is {prefix}-moderator.
  • The moderator task uses needs to depend on all panelist tasks, so it runs only after every panelist completes.
  • strategy and minAgree are passed as prompt context to the moderator. The moderator agent is responsible for interpreting and applying the strategy.
  • Panelist outputs all write to the same panelistOutput schema, differentiated by their task id.