DinoAI - Paradime

DinoAI is Paradime’s AI platform — a suite of agents and tools that help data teams move faster, write better code, and keep their pipelines healthy. Rather than a single feature, DinoAI is a set of surfaces you can use depending on where and how you work.

DinoAI Surfaces

Surface	What it does	Best for
Copilot	AI assistant inside the Paradime IDE	Interactive development, writing and reviewing dbt™ code
MCP Server	Expose Paradime context to any MCP-compatible AI client	Using DinoAI from external tools like Claude or Cursor
Slack Agent	AI agent that runs in the background and posts to Slack	Async monitoring, alerts, and team-wide visibility
Programmable Agents	YAML-defined agents triggered via the Paradime API	Automated, version-controlled, composable AI workflows
Bolt AutoPilot	AI agent embedded in Bolt pipeline runs	Summarising logs, fixing errors, and self-healing pipelines

Key Concepts

Before diving into a specific surface, it helps to understand a few concepts that apply across DinoAI.

.dinorules

.dinorules is a file you commit to your repo that defines rules and constraints for DinoAI agents. Use it to enforce coding standards, naming conventions, or any project-specific guidance that should apply across all agent interactions.

.dinoprompts

.dinoprompts lets you define reusable prompt templates, stored in your repo alongside your dbt™ project. Reference them in agent runs to keep prompts consistent and version-controlled.

Context

DinoAI agents are context-aware. Depending on the surface, they can read your dbt™ project files, query your data warehouse, access run logs, and more. Each surface page documents what context is available.

Choosing the Right Surface

Working in the IDE? → Copilot
Using an external AI client? → MCP Server
Want async updates in Slack? → Slack Agent
Building automated pipelines? → Programmable Agents
Dealing with failing Bolt Pipelines? → Bolt Pipeline Agent

​DinoAI Surfaces

​Key Concepts

​.dinorules

​.dinoprompts

​Context

​Choosing the Right Surface