You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
dbt tools: manifest overwritten by tool runs, CTE timings include dbt start-up, unnamed graph clauses, unclear argument errors, stale tool daemon #1780
Found while using altimate-code tool run against a DuckDB dbt project (200k customers, 15M orders) from the Claude Code plugin.
target/manifest.json is overwritten by tool runs.dbt_cte_profile, dbt_sql_graph, dbt_health and the other tools that start the dbt adapter run dbt commands (show, compile, parse) that write to the project's target/. dbt rewrites manifest.json on each command with compiled SQL for only the nodes that command compiled. After dbt compile (19 nodes with compiled_code), one dbt_cte_profile run leaves 0, so other readers of the manifest (the plugin's lineage pane) report no compiled SQL.
dbt_cte_profile times include dbt's start-up. Each count query starts a new dbt process (about 2 s), so a 200k-row CTE is reported at about 2.4 s while the warehouse spends a few milliseconds on it.
dbt_sql_graph join and filter nodes carry the backend's generated keys as their names (Where_1398865…, Join_1398865…).
impact_analysis without change_type fails with SchemaError(Expected <Declaration>, got {...}), which doesn't say which field is wrong. The same applies to every tool defined with a zod schema and no formatter of its own.
A tool daemon started outside the project's virtualenv keeps answering "the dbt adapter didn't load the project" after the caller activates the virtualenv, until altimate-code tool daemon stop. The daemon key ignores VIRTUAL_ENV, so the activated caller reaches the same daemon, and the message doesn't say how to fix it.
Activity
sahrizvi commentedon Nov 21, 2026
Resolved in v0.12.12.