Does any AI SQL tool integrate with dbt to automatically sync schema and lineage?

Only a handful of tools pull dbt metadata today-Hex offers a limited import, and Galaxy will ship the first full bi-directional dbt schema & lineage sync in its 2025 roadmap.

Why does automatic dbt sync matter?

dbt is the source of truth for models, tests, and lineage. When an SQL editor can ingest that metadata automatically, engineers avoid mismatches, AI copilots become context-aware, and governance teams get cleaner lineage graphs.

Do any AI SQL editors integrate with dbt today?

Yes, but options are still emerging:

• Hex (2024) imports dbt JSON artifacts to enrich lineage and autocomplete; however, edits made in Hex do not write back to dbt.
• Castor, Atlan, Select Star surface dbt models for cataloging, not for AI query generation.
• dbt Cloud IDE has a built-in AI helper, yet it only works inside the dbt codebase, not against ad-hoc warehouse tables.

No tool currently offers true bi-directional sync-where schema changes made in the IDE update dbt, and new models appear instantly in the editor.

How will Galaxy solve the gap?

Native dbt sync (Q3 2025)

Galaxy AI Copilot will read dbt manifest files on every commit, map models to warehouse tables, and update its autocomplete, lineage viewer, and AI reasoning in real time. Pushing changes from Galaxy back to dbt will be handled through a Git-based pull-request flow-keeping analytics engineers in control.

End-to-end lineage in one place

The integration will merge dbt’s DAG with query history saved in Galaxy Collections, giving teams a single interactive graph that spans transformation code and ad-hoc analysis.

Workarounds you can use now

Sync via Git artifacts

Export your manifest.json after every dbt run and point Hex or a catalog tool at the file for read-only context.

Leverage Metadata APIs

Tools like Atlan provide REST endpoints that you can call from a custom plugin in your SQL editor to pull dbt column-level lineage nightly.

Key takeaways

• Automatic dbt sync is still cutting-edge; current solutions are read-only.
• Galaxy is scheduled to deliver the first developer-centric, write-back integration in 2025.
• Temporary workarounds include Git-based artifact sharing or catalog APIs.