Configure an agentCopy Anchor Link

An agent is a validated manifest plus workspace files and secret environment values. Start with the generator instead of copying the full schema by hand.

Generate and validateCopy Anchor Link

dispach init
dispach validate milo

For an isolated experiment, relocate the entire runtime home:

DISPACH_HOME=/tmp/dispach-sandbox dispach init
DISPACH_HOME=/tmp/dispach-sandbox dispach run

Edit supported settingsCopy Anchor Link

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

The interactive editor and HTTP configuration endpoint use the same field catalogue. Validation happens before a file is replaced. The HTTP response reports persistence and activation separately: applied: false means the file was saved but the running agent could not be replaced, usually because a turn is active. Reload or restart that agent after the turn finishes.

Model endpoint shapeCopy Anchor Link

baseUrl ends at the API version segment. Dispach appends /chat/completions:

model:
  main:
    id: gpt-4.1-mini
    baseUrl: https://api.openai.com/v1
    apiKeyEnv: MODEL_API_KEY

Keep the secret in the named environment variable. A literal key in the manifest fails validation.

The model's tool dialect is explicit configuration. nlt is the default; use native only when you intentionally choose provider-native function calling. Dispach does not change dialect when the model ID changes.

The binding field reference is the Agent manifest specification. The generated starter at examples/reference/agent.yaml shows a complete current manifest.