Workspace and manifest

A workspace contains one agent and its conversations, contacts, knowledge, secrets, and channel connections. Its deployable configuration lives in a directory containing vatio.yml:

support-agent/
  vatio.yml          # required
  tools/*.yml        # tools
  identity.pub       # public key that verifies your JWT (see Authentication)

Only create the files you need. The CLI finds the nearest vatio.yml at or above the current directory and reads workspace to select the remote. Deployment commands have no --workspace flag or VATIO_WORKSPACE override. Your user credentials live separately in ~/.vatio/config.json.

The guides below show configuration fragments. Merge them into your existing manifest, keeping one copy of each root key and preserving the instructions and tool assignments you still need.

Root keys

These are the supported root keys. Unknown root keys fail validation.

Key	Purpose
workspace	Remote slug: lowercase letters and digits separated by hyphens
agent	The agent definition; requires non-empty instructions
agents	Several agents, keyed by slug, instead of agent
entry	Which agent takes a conversation; see Several agents
business	Company name and context for the agent
widget	Web appearance, copy, locale, and allowed origins
auth	Public key that verifies your JWT; see Authentication

knowledge and links are not root keys: each agent declares its own, inside its agent: or agents: block. identity is auth. A manifest still carrying any of the three fails the push with the migration to make.

Use agent: false only for a workspace dedicated to the phone verification API. It cannot also declare widget, authentication, knowledge, links, tools, or shared helpers.