Agents

The agent block describes an agent:

Field	Required	Purpose
instructions	Yes	Tasks, decision rules, and when to use tools
name	No	Display name; defaults to the agent's key
personality	No	Voice and tone; defaults to warm, brief, and clear
tools	No	Tool keys the agent may call; defaults to an empty list
knowledge	No	Knowledge bases this agent reads
links	No	Urls this agent may hand out

There is no agent.key to configure. A workspace written with agent: has one agent, and the runtime calls it main.

business:
  name: Acme
  summary: Acme sells warehouse robotics to distributors in Chile and Peru.
agent:
  instructions: |
    Answer product questions using knowledge_lookup.
    If the knowledge does not answer the question, say what is missing.
  tools: [knowledge_lookup]
  knowledge: [docs]

knowledge: and links: belong to the agent, not to the workspace — every agent states what it reads and which urls it may hand out, even when two agents say the same thing.

Create the docs knowledge base with vatio kb create docs before pushing this example: a referenced base must already exist.

Business context

business belongs at the manifest root. business.name accepts up to 100 characters; business.summary accepts 2,000. Omitting either preserves its current workspace value.

Write instructions about your product and workflow. Vatio adds business context, contact state, tool descriptions, and its platform instructions. The agent normally replies in the visitor's language; specify a language in instructions or personality when your product requires one.