Skip to main content
Start with the JSON envelope’s status, reason, errors, and warnings. A refusal explains a boundary; a successful result may still contain findings or checks that did not run.

​
Choose the symptom

Read what it is asking you to approve. A cost estimate, configuration diff, and file changed since planning require different decisions.For spend, follow cost controls. For a config change, review the diff in dex config. If a planned file has changed, plan again against the current file before applying.Do not treat --confirm as a universal retry flag.
Check uv --version in the terminal your agent uses. Follow Installation if it is missing. A reason: prerequisite response names the extra the command needs; install that extra or use the skill wrapper that selects it. Do not replace the command with a raw warehouse client.
Run from your project directory, inspect dex config get, and run dex config validate. Then use dex connect test to check the selected target. See Connect your data for connector discovery and scope.For dbt, check that Dex can discover one project or that dbt_project_dir selects the intended one. DBT_PROFILES_DIR locates dbt profiles; it does not by itself select Dex’s connector.
Read the PII policy. Only a human clears a flag. If an aggregate answers the question, ask for the aggregate instead of returning individual values. Do not alter flags to make a query pass.
Use a fresh directory outside an existing Dex project. The demo is create-only and will not replace an existing warehouse file. A configuration above the directory can also keep it from creating the demo configuration. See the quickstart.
Read data.verification, including findings and suppressed checks. A successful dbt run does not prove the population, joins, or grain are right. Investigate row loss, fan-out, and NULL columns, fix the plan, then rebuild with --verify. A column_missing, column_undeclared, or column_type_mismatch finding means the built relation and schema.yml disagree: fix whichever is out of date. See Transform a dbt project.
Read the elision counts, skipped objects, suppressed checks, and any optional measurement offer. Narrow the question or request the missing evidence. A check that did not run is not a clean result. See Explore or Maintain.
For the exact response fields, use the command contract.