Skip to main content
Connic
Build

Configure an Agent

Define an agent in YAML, validate it locally, and choose the advanced configuration you need.

Last updated

Create an agent file

Add one YAML file per agent under agents/. This minimal LLM agent selects a model and supplies the instructions it should follow:

agents/assistant.yaml
version: "1.0"

name: assistant
type: llm
model: gemini/gemini-2.5-pro
description: "A helpful general-purpose assistant"
system_prompt: |
  You are a helpful assistant.
  Be concise and accurate.

Required fields

  • Every agent needs version, name, and description.
  • An LLM agent also needs model and system_prompt.
  • A sequential agent needs an agents list.
  • A tool agent needs one tool_name.

See Agent Types for choosing an execution model and complete examples.

Validate and iterate

Run connic lint to validate agent configuration before deployment. While building, connic dev reloads changes without a new deployment. Add tests to lock in expected behavior.

Keep shared settings in one place

Put an _defaults.yaml file in an agents directory to share models, guardrails, tools, and other settings with agents below it. See Cascading Defaults.

Agent configuration guides

Agent Types

Choose LLM, sequential, or tool execution

Models and Providers

Configure model identifiers and provider credentials

Runtime Controls

Set retries, concurrency, sessions, and shared defaults

Agent YAML

Look up every supported field and expression