Agents, knowledge bases and connections are definitions like tables and flows. Keep them in your repository, review changes in pull requests, and deploy the same agent to staging and production. For what each one does, see Agents, Knowledge bases and Connections.

Agent

Limits

validate rejects an unknown limit name or a value of the wrong kind. See Approvals and limits.

Tools

Every helper returns one entry for Agent(tools=[...]). Tables, flows, connections and other agents can be passed as the definitions themselves or by name. Anything that changes data waits for a person unless approval="auto" says otherwise; approval="ask" asks every time.

Connection

A connection holds the address and the name of a secret that holds the key, never the key itself. Set the secret in Studio or with the management client, then deploy.

KnowledgeBase

The documents are data, not definitions: add them from Studio or the SDK (ai.knowledge.add_document). See Add documents and search.

Checks before you deploy

pawabase validate checks, offline: that an agent’s model, tools, knowledge bases and policies exist; that limits are valid; that connections referenced by tools exist and have a kind that suits the tool; and that a tool’s table actions are real. Names that don’t exist are reported with the place they were used.

Deploying

Promote and deploy handle these like other definitions: the connection’s secret and the model must exist in the target environment first. A knowledge base arrives empty. See Plan and deploy.

Fields

Vector fields for search by meaning.

Policies

Who may run an agent.