Dispach
Runtime reference

Configuration

agent.yaml is the declarative source for an agent. The loader rejects unknown or invalid values and reports a corrective hint.

AreaControls
modelRoles, model IDs, endpoints, key environment names, and capabilities, including promptStyle and its examplesIn placement
contextWorkspace tiers, budgets, soul selection, compaction thresholds, output reserve, and observation size
toolsDialect, pinned providers and tools, policy, untrusted-write behavior, and provider settings
phasesPer-phase instructions, transitions, and visible tools
skillsSkill directories, selection, and which skills' scripts become tools
knowledgeKeyword-gated reference entries and their per-turn budget
limitsmaxSteps, noProgress, turn and tool timeouts, maxParallelTools, maxConcurrentTurns, reloadHoldMs, maxHops, and tokens
memoryStore and retrieval behavior
schedulesCron, interval, and one-shot inbound triggers
channelsTransport configuration and inbound allowlists
deliveryDefault and named outbound routing targets
teamMembers a supervisor agent delegates to
subagentsThrowaway children of the same agent that tool calls are routed to
mediaTranscription, image generation, and spoken replies (experimental in 0.2.0)
standInAnswering for a member while they are away (experimental in 0.2.0)
delegationDelegation between members' agents (experimental in 0.2.0)
pluginsPackages loaded at boot and their configuration
serverHTTP binding and server behavior for the agent runtime

Use the CLI field catalogue when possible:

dispach config list milo
dispach config set milo model.main.id gpt-4.1-mini
dispach validate milo

Secrets are values in the environment; configuration stores only their variable names. Plugins resolve at boot, and the runtime never installs packages on demand.

The authoritative field-by-field contracts are the Agent manifest specification and Workspace specification. The current full example is examples/reference/agent.yaml.

On this page