Multiagent Studio

Build agents two ways, publish a coordinator roster, and run one governed Session.

A workspace builds agents two ways — with a form, and by talking to a builder agent whose drafts a human reviews — then publishes one coordinator Agent with an ordered subagent roster and runs one Session.

Source: examples/multiagent-studio in the repository. The index at examples/README.md compares all eight side by side.

Golden journeys

• Build an agent by form, and by builder conversation with a reviewed draft
• Compose and publish a coordinator Agent with a frozen roster
• Run one governed coordinator Session with recorded child attribution
• Approve the calls that matter

Platform surfaces exercised

Principals, Agents and versions, multiagent rosters, PermissionAssignments, Sessions, Model routing profiles, Harness catalog, ActionApprovals.

From the source

The studio’s entire platform port — every capability the app has, stated in one place:

path=examples/multiagent-studio/server/src/platform.ts

export interface StudioPlatform {
	readonly ensurePrincipal: (user: DemoUser, signal?: AbortSignal) => Promise<string>
	readonly readCatalog: () => Promise<StudioCatalog>
	readonly createAgent: (
		draft: AgentDraftInput,
		documentId: string,
		signal?: AbortSignal,
	) => Promise<PlatformAgent>
	readonly updateAgent: (
		agentId: string,
		draft: AgentDraftInput,
		expectedRevision: number,
	) => Promise<PlatformAgent>
	readonly publishAgent: (
		agentId: string,
		expectedRevision: number,
		idempotencyKey: string,
	) => Promise<PlatformAgent>
	readonly publishAgentCallAuthorized: (sessionId: string, toolUseId: string) => Promise<boolean>
	readonly retrieveAgent: (agentId: string) => Promise<PlatformAgent>

This block is quoted from the file, not retyped: pnpm agent-docs:check fails if it drifts.

Honest gaps

Recorded in examples/multiagent-studio/README.md. Counts are deliberately not repeated here — they differ per tree, and examples/README.md carries them with the sha they were measured at.