## TL;DR
For agents and automation, dbt Core (the open-source CLI) is usually the better pick: it runs anywhere, scripts cleanly, and costs nothing per run. dbt Cloud adds a managed scheduler, hosted IDE, and job APIs, which help human teams but add a service dependency an agent does not need. Choose Cloud when the humans want the UI and managed runs; choose Core when a machine is driving.

## The query
```text
dbt cloud vs dbt core for agents
```

## Use this when
- An agent or CI system needs to run dbt build, test, or docs generate
- Deciding whether dbt Cloud's job API is worth it for automation
- Standardizing how scheduled dbt runs execute

## Not for
- Deciding which SQL dialect to write (same on both)
- Teams choosing purely on IDE preference
- Getting exact current pricing

## Steps

1. List what the automation actually needs: run commands, read artifacts (run_results.json, manifest.json), trigger on schedule or on merge. dbt Core covers all of these with shell commands and files on disk.

Expected output: a requirements list with no item that needs a hosted UI.

2. Check what dbt Cloud adds for your case: managed scheduling with retries and alerting, the job API for triggering runs remotely, and Slim CI with state selection. If an external orchestrator (Airflow, GitHub Actions) already handles scheduling and alerting, Cloud's scheduler is redundant.

Expected output: a clear statement of which Cloud features you would actually use.

3. Consider failure modes an agent must handle. With Core, the agent sees full logs and exit codes directly. With Cloud, the agent must poll the job API and fetch logs through it, which adds failure modes and latency.

Expected output: the simpler observability story wins for agent-driven runs.

4. Decide and document: Core plus your existing orchestrator for agent-driven work; Cloud if the human team wants the hosted experience. Do not run both schedulers against the same project.

Expected output: one named platform per project, with the runner documented in the repo README.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_IW8rHdreLfq-XchXBlCysg