YAML Configuration

Agents are defined as YAML files committed to your repo under .dinoai/agents/. Each file defines one agent.

The agent builder in the app writes this same format: when deploying from Creating Agents in the App you choose whether the agent is saved to the workspace only or committed to your repo with this schema through a pull request.

Full Example

name: pr-reviewer        # must match file name
version: 1               # schema version (currently 1)

environment: analytics-prod   # optional: run in this Agent environment

role: >
  PR Review Orchestrator responsible for assessing all aspects of a pull
  request across dbt™ models.

goal: >
  Review incoming PRs for quality, coverage, and correctness.
  Delegate specialist work where needed.

backstory: >
  You coordinate reviews across multiple quality dimensions and know when
  to call in specialists.

tools:
  mode: allowlist         # "allowlist" or "denylist"
  list:
    - read_file
    - search_files_and_directories
    - ripgrep_search
    - post_slack_message
    - invoke_agent        # required to delegate to sub-agents

agents_squad:             # sub-agents this agent may invoke
  - test-maintainer

slack:
  channel: "#pr-reviews"
  answer_in: thread       # optional: "thread" (default) or "channel"
  updates: all            # optional: "all" (default) or "final"

To review pull requests with an agent like this one, pick it as a custom reviewer in DinoAI Code Review. Give it its own name: pr-reviewer is the name of the reviewer that Paradime manages. Either way, Paradime posts the review, so the agent doesn’t need Slack or a GitHub Actions workflow.

Field Reference

Field	Required	Description
`name`	Yes	Unique identifier. Must match the YAML file name (without `.yml`).
`version`	Yes	Schema version for forward compatibility. Currently `1`.
`role`	Yes	What the agent is (injected into the system prompt each turn).
`goal`	Yes	What the agent is trying to achieve.
`backstory`	Yes	How the agent approaches problems.
`tools.mode`	If `tools` present	`allowlist` (only listed tools available) or `denylist` (all tools except listed).
`tools.list`	If `tools` present	Tool names to allow or deny.
`slack.channel`	No	If present, the agent posts to this Slack channel. By default, it starts a thread at run start and posts all its messages there. Requires Slack integration configured and Paradime bot invited to the slack channel
`slack.answer_in`	No	`thread` (default) or `channel`. Where the agent answers. See Slack output.
`slack.updates`	No	`all` (default) or `final`. What the agent posts. See Slack output.
`agents_squad`	No	Names of sub-agents this agent is permitted to invoke via `invoke_agent`.
`model_family`	No	Slug of the model family the agent runs on. Omit it to use the workspace default. An unknown slug falls back to the default family and warns in the run output.
`environment`	No	Slug of the Agent environment the agent runs in, deciding its warehouse connection, dbt™ version, and partial parsing. Omit it to use the workspace’s default Agent environment. An unknown slug fails the session at startup.

Slack output

When slack.channel is set, two optional fields decide how the agent posts there. You can also set them on the Output step of the agent builder. slack.answer_in decides where the agent answers:

thread (default): the run opens a thread with a “Starting agent” message, and the agent answers in that thread.
channel: there is no starter message. The agent’s first message is posted to the channel as a message of its own, and later messages go into its thread. Mention @Paradime in that thread to follow up. Use this for agents whose answer is the news, such as a daily report.

slack.updates decides what the agent posts:

all (default): the agent posts its progress as it works.
final: the thread shows one “Working on it” status, then only the agent’s last message of the turn. Questions, approval requests, and notices that a run failed or stopped still post. Warnings stay out of Slack.

slack:
  channel: "#data-reports"
  answer_in: channel
  updates: final

The agent’s Slack thread tools, find_slack_thread and attach_session_to_slack_thread, work only in the agent’s own channels: the one in slack.channel, and the channel its session is bound to. An agent with neither can use them in any channel the Paradime bot is in.

Important: If the tools block is omitted entirely, the agent has access to all available tools. Use an allowlist for production agents to limit blast radius.

Tool Modes

allowlist — only the tools listed are available to the agent. Recommended for production agents.

tools:
  mode: allowlist
  list:
    - read_file
    - run_sql_query

denylist — all tools are available except the ones listed.

tools:
  mode: denylist
  list:
    - write_file
    - run_terminal_command

A small set of core tools is always available regardless of mode: an allowlist does not need to name them, and a denylist cannot remove them. See Always-available tools. Sub-agents started with run_subagent inherit the parent agent’s tool gating.

MCP tools

List tools from external MCP servers under tools, like any other tool. MCP tool names look like mcp__<server>__<tool>, and mcp__<server>__* matches every tool from one server. Without a tools block, or with a denylist that doesn’t name them, the agent gets every MCP tool its server and environment allow. The separate mcpTools block that agents used to limit MCP tools is deprecated. If an agent still has one, it keeps limiting the agent’s MCP tools on top of tools.

Connect external MCP servers: connecting servers, choosing their tools, and MCP tool names
Tools Reference — Full list of tool names for tools.list
Agent-to-Agent Delegation — Using agents_squad and invoke_agent

Code Review

Slack Bot Agent

Programmable Agent

Bolt Pipeline Agent

Copilot

MCP Server

Context & Customization

DinoAI Tools

Settings & Credits

YAML Configuration

Full Example

Field Reference

Slack output

Tool Modes

MCP tools

​Full Example

​Field Reference

​Slack output

​Tool Modes

​MCP tools

​Related

Full Example

Field Reference

Slack output

Tool Modes

MCP tools

Related