From 97fe0731747ee68a1fb11647ba0c995bd61069b7 Mon Sep 17 00:00:00 2001 From: Harish Kumar Date: Fri, 13 Nov 2026 14:47:39 +0530 Subject: [PATCH 01/14] docs: the Claude Code plugin's dbt helpers Co-Authored-By: Claude Opus 5.5 --- .../guides/using-with-claude-code.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/docs/docs/data-engineering/guides/using-with-claude-code.md b/docs/docs/data-engineering/guides/using-with-claude-code.md index 08032f933b..e94d8be65d 100644 --- a/docs/docs/data-engineering/guides/using-with-claude-code.md +++ b/docs/docs/data-engineering/guides/using-with-claude-code.md @@ -100,6 +100,20 @@ altimate: The plugin runs `altimate-code run` in your project for each task, with the model provider Altimate Code is set up with. If you have not set one up, run `altimate-code` once and choose a provider, or sign in to Altimate (below). +### dbt helpers beside the chat + +In a dbt project the plugin also does what dbt Power User does in VS Code, inside the Claude Code session. Each helper runs the project's own dbt (its `.venv/bin/dbt` when there is one, else `dbt` on `PATH`) and calls no model: + +| Helper | When it runs | What you see | What Claude is told | +|---|---|---|---| +| Compile and validate | After Claude edits or writes a model's `.sql` file | A line above the prompt: the model compiled and ran (`dbt show`, one row), with the columns `schema.yml` documents but the query did not return, and those it returned undocumented | dbt's own error when the model does not compile or run, or the column differences | +| Explain and Fix | After a `dbt run`, `test`, `build`, `seed` or `snapshot` Claude ran fails | The failed nodes with **Explain** (Claude explains each failure without changing files) and **Fix with Altimate Code** (runs `/altimate-code:altimate` on the failures) | The failure, read from `target/run_results.json`, when you press a button | +| Results pane | After Claude runs `dbt show`, or when you run `/dbt-show ` or `/dbt-show select …` | The rows as a table beside the chat, with **Re-run**, **Bookmark**, the history and your bookmarks (kept across sessions) | Nothing | +| Model context | When Claude reads a model's `.sql` file | A toast with the counts | The model's materialization, columns with their types, descriptions and tests, its parents and children, and how deep it sits upstream and downstream, from `target/manifest.json` | +| Environment doctor | At session start, and `/dbt-doctor` | A line above the prompt when something is wrong: dbt, Python, the profile's adapter, `dbt deps`, and a manifest older than the files it was built from, with **Run dbt parse** | The checks, with the first prompt after they finish | + +The doctor tests the warehouse connection (`dbt debug`) only when you run `/dbt-doctor` or press **Test connection**, never at session start. To turn the helpers off, set the plugin's `dbt_mods` option to false in `/config`. + ### The `/altimate` command, without the plugin Run `/configure-claude` inside altimate to write the command: From a1421121379c6d5430b3bbf4a133c41f9b8f2dd5 Mon Sep 17 00:00:00 2001 From: Harish Kumar Date: Fri, 13 Nov 2026 14:49:43 +0530 Subject: [PATCH 02/14] docs: the dbt check pane Co-Authored-By: Claude Opus 5.5 --- docs/docs/data-engineering/guides/using-with-claude-code.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/data-engineering/guides/using-with-claude-code.md b/docs/docs/data-engineering/guides/using-with-claude-code.md index e94d8be65d..8ae440a222 100644 --- a/docs/docs/data-engineering/guides/using-with-claude-code.md +++ b/docs/docs/data-engineering/guides/using-with-claude-code.md @@ -106,7 +106,7 @@ In a dbt project the plugin also does what dbt Power User does in VS Code, insid | Helper | When it runs | What you see | What Claude is told | |---|---|---|---| -| Compile and validate | After Claude edits or writes a model's `.sql` file | A line above the prompt: the model compiled and ran (`dbt show`, one row), with the columns `schema.yml` documents but the query did not return, and those it returned undocumented | dbt's own error when the model does not compile or run, or the column differences | +| Compile and validate | After Claude edits or writes a model's `.sql` file, and again when the model changes outside Claude's edits | A line above the prompt: the model compiled and ran (`dbt show`, one row), with the columns `schema.yml` documents but the query did not return, and those it returned undocumented. A problem opens the **dbt check** pane with every column, or dbt's whole error | dbt's own error when the model does not compile or run, or the column differences | | Explain and Fix | After a `dbt run`, `test`, `build`, `seed` or `snapshot` Claude ran fails | The failed nodes with **Explain** (Claude explains each failure without changing files) and **Fix with Altimate Code** (runs `/altimate-code:altimate` on the failures) | The failure, read from `target/run_results.json`, when you press a button | | Results pane | After Claude runs `dbt show`, or when you run `/dbt-show ` or `/dbt-show select …` | The rows as a table beside the chat, with **Re-run**, **Bookmark**, the history and your bookmarks (kept across sessions) | Nothing | | Model context | When Claude reads a model's `.sql` file | A toast with the counts | The model's materialization, columns with their types, descriptions and tests, its parents and children, and how deep it sits upstream and downstream, from `target/manifest.json` | From 94d4dd2868618ff80d93a07ef3936e828ff66473 Mon Sep 17 00:00:00 2001 From: Harish Kumar Date: Fri, 13 Nov 2026 15:19:32 +0530 Subject: [PATCH 03/14] docs: dbt helpers review fixes Co-Authored-By: Claude Opus 5.5 --- .../data-engineering/guides/using-with-claude-code.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/docs/data-engineering/guides/using-with-claude-code.md b/docs/docs/data-engineering/guides/using-with-claude-code.md index 8ae440a222..5c35e11770 100644 --- a/docs/docs/data-engineering/guides/using-with-claude-code.md +++ b/docs/docs/data-engineering/guides/using-with-claude-code.md @@ -102,17 +102,17 @@ The plugin runs `altimate-code run` in your project for each task, with the mode ### dbt helpers beside the chat -In a dbt project the plugin also does what dbt Power User does in VS Code, inside the Claude Code session. Each helper runs the project's own dbt (its `.venv/bin/dbt` when there is one, else `dbt` on `PATH`) and calls no model: +In a dbt project the plugin also does what dbt Power User does in VS Code, inside the Claude Code session. Each helper runs the project's own dbt (from a `.venv` or `venv` in the project folder when there is one, else `dbt` on `PATH`) and calls no model: | Helper | When it runs | What you see | What Claude is told | |---|---|---|---| -| Compile and validate | After Claude edits or writes a model's `.sql` file, and again when the model changes outside Claude's edits | A line above the prompt: the model compiled and ran (`dbt show`, one row), with the columns `schema.yml` documents but the query did not return, and those it returned undocumented. A problem opens the **dbt check** pane with every column, or dbt's whole error | dbt's own error when the model does not compile or run, or the column differences | +| Compile and validate | After Claude edits or writes a model's `.sql` file, and again when the model changes outside Claude's edits | A line above the prompt: the model compiled and ran (`dbt show`, one row), with the columns `schema.yml` documents but the query did not return, and those it returned undocumented. When the query returns no row or `schema.yml` documents no columns, it says the columns were not compared. A problem opens the **dbt check** pane with every column, or dbt's whole error | dbt's own error when the model does not compile or run, or the column differences | | Explain and Fix | After a `dbt run`, `test`, `build`, `seed` or `snapshot` Claude ran fails | The failed nodes with **Explain** (Claude explains each failure without changing files) and **Fix with Altimate Code** (runs `/altimate-code:altimate` on the failures) | The failure, read from `target/run_results.json`, when you press a button | -| Results pane | After Claude runs `dbt show`, or when you run `/dbt-show ` or `/dbt-show select …` | The rows as a table beside the chat, with **Re-run**, **Bookmark**, the history and your bookmarks (kept across sessions) | Nothing | +| Results pane | After Claude runs `dbt show`, or when you run `/dbt-show ` or `/dbt-show select …` | The rows as a table beside the chat, with **Re-run**, **Bookmark**, **Clear history**, the history and your bookmarks (kept on this machine across sessions) | Nothing | | Model context | When Claude reads a model's `.sql` file | A toast with the counts | The model's materialization, columns with their types, descriptions and tests, its parents and children, and how deep it sits upstream and downstream, from `target/manifest.json` | -| Environment doctor | At session start, and `/dbt-doctor` | A line above the prompt when something is wrong: dbt, Python, the profile's adapter, `dbt deps`, and a manifest older than the files it was built from, with **Run dbt parse** | The checks, with the first prompt after they finish | +| Environment doctor | At session start, and `/dbt-doctor` | A line above the prompt when something is wrong: dbt, Python, the profile's adapter, `dbt deps`, and a manifest older than the files it was built from, with **Run dbt parse** or **Run dbt deps** | The checks, with the first prompt after they finish | -The doctor tests the warehouse connection (`dbt debug`) only when you run `/dbt-doctor` or press **Test connection**, never at session start. To turn the helpers off, set the plugin's `dbt_mods` option to false in `/config`. +The doctor tests the warehouse connection (`dbt debug`) only when you run `/dbt-doctor` or press **Test connection**, never at session start. Compile and validate runs a query on your warehouse after each model edit, which costs money on a warehouse that bills by bytes scanned or wakes a suspended one. To turn the helpers off, set the plugin's `dbt_mods` option to false in `/config`. ### The `/altimate` command, without the plugin From 2e774c3991c5ade541effd90414104de035a2a49 Mon Sep 17 00:00:00 2001 From: Harish Kumar Date: Fri, 13 Nov 2026 16:09:23 +0530 Subject: [PATCH 04/14] docs: dbt helpers review round 2 Co-Authored-By: Claude Opus 5.5 --- docs/docs/data-engineering/guides/using-with-claude-code.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/docs/data-engineering/guides/using-with-claude-code.md b/docs/docs/data-engineering/guides/using-with-claude-code.md index 5c35e11770..a88100846d 100644 --- a/docs/docs/data-engineering/guides/using-with-claude-code.md +++ b/docs/docs/data-engineering/guides/using-with-claude-code.md @@ -106,9 +106,9 @@ In a dbt project the plugin also does what dbt Power User does in VS Code, insid | Helper | When it runs | What you see | What Claude is told | |---|---|---|---| -| Compile and validate | After Claude edits or writes a model's `.sql` file, and again when the model changes outside Claude's edits | A line above the prompt: the model compiled and ran (`dbt show`, one row), with the columns `schema.yml` documents but the query did not return, and those it returned undocumented. When the query returns no row or `schema.yml` documents no columns, it says the columns were not compared. A problem opens the **dbt check** pane with every column, or dbt's whole error | dbt's own error when the model does not compile or run, or the column differences | +| Compile and validate | After Claude edits or writes a model's `.sql` file, and again after Claude's next command or edit when the model or its schema file changed | A line above the prompt: the model compiled and ran (`dbt show`, one row), with the columns `schema.yml` documents but the query did not return, and those it returned undocumented. When the query returns no row or `schema.yml` documents no columns, it says the columns were not compared. A problem opens the **dbt check** pane with every column, or dbt's whole error | dbt's own error when the model does not compile or run, or the column differences | | Explain and Fix | After a `dbt run`, `test`, `build`, `seed` or `snapshot` Claude ran fails | The failed nodes with **Explain** (Claude explains each failure without changing files) and **Fix with Altimate Code** (runs `/altimate-code:altimate` on the failures) | The failure, read from `target/run_results.json`, when you press a button | -| Results pane | After Claude runs `dbt show`, or when you run `/dbt-show ` or `/dbt-show select …` | The rows as a table beside the chat, with **Re-run**, **Bookmark**, **Clear history**, the history and your bookmarks (kept on this machine across sessions) | Nothing | +| Results pane | After Claude runs `dbt show`, or when you run `/dbt-show ` or `/dbt-show select …` | The rows as a table beside the chat, with **Re-run** (Claude's own command with the same flags and folder, unless it used shell variables; or your query), **Bookmark**, **Clear history**, the history and your bookmarks (kept on this machine across sessions) | Nothing | | Model context | When Claude reads a model's `.sql` file | A toast with the counts | The model's materialization, columns with their types, descriptions and tests, its parents and children, and how deep it sits upstream and downstream, from `target/manifest.json` | | Environment doctor | At session start, and `/dbt-doctor` | A line above the prompt when something is wrong: dbt, Python, the profile's adapter, `dbt deps`, and a manifest older than the files it was built from, with **Run dbt parse** or **Run dbt deps** | The checks, with the first prompt after they finish | From d307043f880113d6a66a6c467c0ac30805233049 Mon Sep 17 00:00:00 2001 From: Harish Kumar Date: Fri, 13 Nov 2026 16:39:56 +0530 Subject: [PATCH 05/14] docs: dbt helpers review round 3 Co-Authored-By: Claude Opus 5.5 --- docs/docs/data-engineering/guides/using-with-claude-code.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/docs/data-engineering/guides/using-with-claude-code.md b/docs/docs/data-engineering/guides/using-with-claude-code.md index a88100846d..e899955141 100644 --- a/docs/docs/data-engineering/guides/using-with-claude-code.md +++ b/docs/docs/data-engineering/guides/using-with-claude-code.md @@ -106,9 +106,9 @@ In a dbt project the plugin also does what dbt Power User does in VS Code, insid | Helper | When it runs | What you see | What Claude is told | |---|---|---|---| -| Compile and validate | After Claude edits or writes a model's `.sql` file, and again after Claude's next command or edit when the model or its schema file changed | A line above the prompt: the model compiled and ran (`dbt show`, one row), with the columns `schema.yml` documents but the query did not return, and those it returned undocumented. When the query returns no row or `schema.yml` documents no columns, it says the columns were not compared. A problem opens the **dbt check** pane with every column, or dbt's whole error | dbt's own error when the model does not compile or run, or the column differences | +| Compile and validate | After Claude edits or writes a model's `.sql` file, and again after Claude's next command or edit when the model, a schema file or another SQL file (a macro) changed | A line above the prompt: the model compiled and ran (`dbt show`, one row), with the columns `schema.yml` documents but the query did not return, and those it returned undocumented. When the query returns no row or `schema.yml` documents no columns, it says the columns were not compared. A problem opens the **dbt check** pane with every column, or dbt's whole error | dbt's own error when the model does not compile or run, or the column differences | | Explain and Fix | After a `dbt run`, `test`, `build`, `seed` or `snapshot` Claude ran fails | The failed nodes with **Explain** (Claude explains each failure without changing files) and **Fix with Altimate Code** (runs `/altimate-code:altimate` on the failures) | The failure, read from `target/run_results.json`, when you press a button | -| Results pane | After Claude runs `dbt show`, or when you run `/dbt-show ` or `/dbt-show select …` | The rows as a table beside the chat, with **Re-run** (Claude's own command with the same flags and folder, unless it used shell variables; or your query), **Bookmark**, **Clear history**, the history and your bookmarks (kept on this machine across sessions) | Nothing | +| Results pane | After Claude runs `dbt show`, or when you run `/dbt-show ` or `/dbt-show select …` | The rows as a table beside the chat, with **Re-run** (Claude's own command with the same flags and folder, unless it depended on its shell, such as a variable or `~`; or your query), **Bookmark**, **Clear history**, the history and your bookmarks (kept on this machine across sessions) | Nothing | | Model context | When Claude reads a model's `.sql` file | A toast with the counts | The model's materialization, columns with their types, descriptions and tests, its parents and children, and how deep it sits upstream and downstream, from `target/manifest.json` | | Environment doctor | At session start, and `/dbt-doctor` | A line above the prompt when something is wrong: dbt, Python, the profile's adapter, `dbt deps`, and a manifest older than the files it was built from, with **Run dbt parse** or **Run dbt deps** | The checks, with the first prompt after they finish | From 27fb00ed3d9e9d32d18e6ad1b8a78d91945bbcb8 Mon Sep 17 00:00:00 2001 From: Harish Kumar Date: Fri, 13 Nov 2026 22:24:42 +0530 Subject: [PATCH 06/14] =?UTF-8?q?docs:=20dbt=20helpers=20=E2=80=94=20retry?= =?UTF-8?q?,=20compound=20and=20preview=20rules?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Claude Opus 5.5 --- docs/docs/data-engineering/guides/using-with-claude-code.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/docs/data-engineering/guides/using-with-claude-code.md b/docs/docs/data-engineering/guides/using-with-claude-code.md index e899955141..8396e45eb1 100644 --- a/docs/docs/data-engineering/guides/using-with-claude-code.md +++ b/docs/docs/data-engineering/guides/using-with-claude-code.md @@ -107,8 +107,8 @@ In a dbt project the plugin also does what dbt Power User does in VS Code, insid | Helper | When it runs | What you see | What Claude is told | |---|---|---|---| | Compile and validate | After Claude edits or writes a model's `.sql` file, and again after Claude's next command or edit when the model, a schema file or another SQL file (a macro) changed | A line above the prompt: the model compiled and ran (`dbt show`, one row), with the columns `schema.yml` documents but the query did not return, and those it returned undocumented. When the query returns no row or `schema.yml` documents no columns, it says the columns were not compared. A problem opens the **dbt check** pane with every column, or dbt's whole error | dbt's own error when the model does not compile or run, or the column differences | -| Explain and Fix | After a `dbt run`, `test`, `build`, `seed` or `snapshot` Claude ran fails | The failed nodes with **Explain** (Claude explains each failure without changing files) and **Fix with Altimate Code** (runs `/altimate-code:altimate` on the failures) | The failure, read from `target/run_results.json`, when you press a button | -| Results pane | After Claude runs `dbt show`, or when you run `/dbt-show ` or `/dbt-show select …` | The rows as a table beside the chat, with **Re-run** (Claude's own command with the same flags and folder, unless it depended on its shell, such as a variable or `~`; or your query), **Bookmark**, **Clear history**, the history and your bookmarks (kept on this machine across sessions) | Nothing | +| Explain and Fix | After a `dbt run`, `test`, `build`, `seed`, `snapshot` or `retry` Claude ran fails | The failed nodes with **Explain** (Claude explains each failure without changing files) and **Fix with Altimate Code** (runs `/altimate-code:altimate` on the failures) | The failure, read from `target/run_results.json` (or dbt's own text when the run wrote none), when you press a button. A passing run of the same kind (or a build) with the same selection and target, or of the whole project, clears it (a passing `dbt retry` never does; a compound command is cleared only by the same command or a whole-project build, and a killed run clears nothing) | +| Results pane | After Claude runs `dbt show`, or when you run `/dbt-show ` or `/dbt-show select …` | The rows as a table beside the chat, with **Re-run** (Claude's own command with the same flags and folder, unless it depended on its shell, such as a variable or `~`; or your query), **Bookmark**, **Clear history**, the history and your bookmarks (kept on this machine across sessions); several different `dbt show`s in one command save no preview | Nothing | | Model context | When Claude reads a model's `.sql` file | A toast with the counts | The model's materialization, columns with their types, descriptions and tests, its parents and children, and how deep it sits upstream and downstream, from `target/manifest.json` | | Environment doctor | At session start, and `/dbt-doctor` | A line above the prompt when something is wrong: dbt, Python, the profile's adapter, `dbt deps`, and a manifest older than the files it was built from, with **Run dbt parse** or **Run dbt deps** | The checks, with the first prompt after they finish | From 94158e074291eea099d9925033310a23879f9b09 Mon Sep 17 00:00:00 2001 From: Harish Kumar Date: Fri, 13 Nov 2026 22:40:30 +0530 Subject: [PATCH 07/14] =?UTF-8?q?docs:=20dbt=20helpers=20=E2=80=94=20unspl?= =?UTF-8?q?ittable=20output?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Claude Opus 5.5 --- docs/docs/data-engineering/guides/using-with-claude-code.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/data-engineering/guides/using-with-claude-code.md b/docs/docs/data-engineering/guides/using-with-claude-code.md index 8396e45eb1..4b073acef4 100644 --- a/docs/docs/data-engineering/guides/using-with-claude-code.md +++ b/docs/docs/data-engineering/guides/using-with-claude-code.md @@ -107,7 +107,7 @@ In a dbt project the plugin also does what dbt Power User does in VS Code, insid | Helper | When it runs | What you see | What Claude is told | |---|---|---|---| | Compile and validate | After Claude edits or writes a model's `.sql` file, and again after Claude's next command or edit when the model, a schema file or another SQL file (a macro) changed | A line above the prompt: the model compiled and ran (`dbt show`, one row), with the columns `schema.yml` documents but the query did not return, and those it returned undocumented. When the query returns no row or `schema.yml` documents no columns, it says the columns were not compared. A problem opens the **dbt check** pane with every column, or dbt's whole error | dbt's own error when the model does not compile or run, or the column differences | -| Explain and Fix | After a `dbt run`, `test`, `build`, `seed`, `snapshot` or `retry` Claude ran fails | The failed nodes with **Explain** (Claude explains each failure without changing files) and **Fix with Altimate Code** (runs `/altimate-code:altimate` on the failures) | The failure, read from `target/run_results.json` (or dbt's own text when the run wrote none), when you press a button. A passing run of the same kind (or a build) with the same selection and target, or of the whole project, clears it (a passing `dbt retry` never does; a compound command is cleared only by the same command or a whole-project build, and a killed run clears nothing) | +| Explain and Fix | After a `dbt run`, `test`, `build`, `seed`, `snapshot` or `retry` Claude ran fails | The failed nodes with **Explain** (Claude explains each failure without changing files) and **Fix with Altimate Code** (runs `/altimate-code:altimate` on the failures) | The failure, read from `target/run_results.json` (or dbt's own text when the run wrote none), when you press a button. A passing run of the same kind (or a build) with the same selection and target, or of the whole project, clears it (a passing `dbt retry` never does; a compound command is cleared only by the same command or a whole-project build, and a killed run or output that cannot be split per command, such as output piped through `tail` with its headers cut off, clears nothing) | | Results pane | After Claude runs `dbt show`, or when you run `/dbt-show ` or `/dbt-show select …` | The rows as a table beside the chat, with **Re-run** (Claude's own command with the same flags and folder, unless it depended on its shell, such as a variable or `~`; or your query), **Bookmark**, **Clear history**, the history and your bookmarks (kept on this machine across sessions); several different `dbt show`s in one command save no preview | Nothing | | Model context | When Claude reads a model's `.sql` file | A toast with the counts | The model's materialization, columns with their types, descriptions and tests, its parents and children, and how deep it sits upstream and downstream, from `target/manifest.json` | | Environment doctor | At session start, and `/dbt-doctor` | A line above the prompt when something is wrong: dbt, Python, the profile's adapter, `dbt deps`, and a manifest older than the files it was built from, with **Run dbt parse** or **Run dbt deps** | The checks, with the first prompt after they finish | From 568e8cb1a18f556cd24c73423ad468ecd90c4e76 Mon Sep 17 00:00:00 2001 From: Harish Kumar Date: Fri, 13 Nov 2026 23:33:03 +0530 Subject: [PATCH 08/14] =?UTF-8?q?docs:=20dbt=20helpers=20=E2=80=94=20where?= =?UTF-8?q?=20failures=20come=20from?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Claude Opus 5.5 --- docs/docs/data-engineering/guides/using-with-claude-code.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/data-engineering/guides/using-with-claude-code.md b/docs/docs/data-engineering/guides/using-with-claude-code.md index 4b073acef4..2ea7e60cc7 100644 --- a/docs/docs/data-engineering/guides/using-with-claude-code.md +++ b/docs/docs/data-engineering/guides/using-with-claude-code.md @@ -107,7 +107,7 @@ In a dbt project the plugin also does what dbt Power User does in VS Code, insid | Helper | When it runs | What you see | What Claude is told | |---|---|---|---| | Compile and validate | After Claude edits or writes a model's `.sql` file, and again after Claude's next command or edit when the model, a schema file or another SQL file (a macro) changed | A line above the prompt: the model compiled and ran (`dbt show`, one row), with the columns `schema.yml` documents but the query did not return, and those it returned undocumented. When the query returns no row or `schema.yml` documents no columns, it says the columns were not compared. A problem opens the **dbt check** pane with every column, or dbt's whole error | dbt's own error when the model does not compile or run, or the column differences | -| Explain and Fix | After a `dbt run`, `test`, `build`, `seed`, `snapshot` or `retry` Claude ran fails | The failed nodes with **Explain** (Claude explains each failure without changing files) and **Fix with Altimate Code** (runs `/altimate-code:altimate` on the failures) | The failure, read from `target/run_results.json` (or dbt's own text when the run wrote none), when you press a button. A passing run of the same kind (or a build) with the same selection and target, or of the whole project, clears it (a passing `dbt retry` never does; a compound command is cleared only by the same command or a whole-project build, and a killed run or output that cannot be split per command, such as output piped through `tail` with its headers cut off, clears nothing) | +| Explain and Fix | After a `dbt run`, `test`, `build`, `seed`, `snapshot` or `retry` Claude ran fails | The failed nodes with **Explain** (Claude explains each failure without changing files) and **Fix with Altimate Code** (runs `/altimate-code:altimate` on the failures) | The failure, read from the `target/run_results.json` the command wrote, together with the errors dbt printed, when you press a button. A passing run of the same kind (or a build) with the same selection and target, or of the whole project, clears it (a passing `dbt retry` never does; a compound command is cleared only by the same command or a whole-project build, and a killed run or output that cannot be split per command, such as output piped through `tail` with its headers cut off, clears nothing) | | Results pane | After Claude runs `dbt show`, or when you run `/dbt-show ` or `/dbt-show select …` | The rows as a table beside the chat, with **Re-run** (Claude's own command with the same flags and folder, unless it depended on its shell, such as a variable or `~`; or your query), **Bookmark**, **Clear history**, the history and your bookmarks (kept on this machine across sessions); several different `dbt show`s in one command save no preview | Nothing | | Model context | When Claude reads a model's `.sql` file | A toast with the counts | The model's materialization, columns with their types, descriptions and tests, its parents and children, and how deep it sits upstream and downstream, from `target/manifest.json` | | Environment doctor | At session start, and `/dbt-doctor` | A line above the prompt when something is wrong: dbt, Python, the profile's adapter, `dbt deps`, and a manifest older than the files it was built from, with **Run dbt parse** or **Run dbt deps** | The checks, with the first prompt after they finish | From 2109bed7acd2d9c953e4576a83c340816e4671fe Mon Sep 17 00:00:00 2001 From: Harish Kumar Date: Fri, 13 Nov 2026 23:44:05 +0530 Subject: [PATCH 09/14] =?UTF-8?q?docs:=20dbt=20helpers=20=E2=80=94=20clear?= =?UTF-8?q?ing=20rule?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Claude Opus 5.5 --- docs/docs/data-engineering/guides/using-with-claude-code.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/data-engineering/guides/using-with-claude-code.md b/docs/docs/data-engineering/guides/using-with-claude-code.md index 2ea7e60cc7..64767744a0 100644 --- a/docs/docs/data-engineering/guides/using-with-claude-code.md +++ b/docs/docs/data-engineering/guides/using-with-claude-code.md @@ -107,7 +107,7 @@ In a dbt project the plugin also does what dbt Power User does in VS Code, insid | Helper | When it runs | What you see | What Claude is told | |---|---|---|---| | Compile and validate | After Claude edits or writes a model's `.sql` file, and again after Claude's next command or edit when the model, a schema file or another SQL file (a macro) changed | A line above the prompt: the model compiled and ran (`dbt show`, one row), with the columns `schema.yml` documents but the query did not return, and those it returned undocumented. When the query returns no row or `schema.yml` documents no columns, it says the columns were not compared. A problem opens the **dbt check** pane with every column, or dbt's whole error | dbt's own error when the model does not compile or run, or the column differences | -| Explain and Fix | After a `dbt run`, `test`, `build`, `seed`, `snapshot` or `retry` Claude ran fails | The failed nodes with **Explain** (Claude explains each failure without changing files) and **Fix with Altimate Code** (runs `/altimate-code:altimate` on the failures) | The failure, read from the `target/run_results.json` the command wrote, together with the errors dbt printed, when you press a button. A passing run of the same kind (or a build) with the same selection and target, or of the whole project, clears it (a passing `dbt retry` never does; a compound command is cleared only by the same command or a whole-project build, and a killed run or output that cannot be split per command, such as output piped through `tail` with its headers cut off, clears nothing) | +| Explain and Fix | After a `dbt run`, `test`, `build`, `seed`, `snapshot` or `retry` Claude ran fails | The failed nodes with **Explain** (Claude explains each failure without changing files) and **Fix with Altimate Code** (runs `/altimate-code:altimate` on the failures) | The failure, read from the `target/run_results.json` the command wrote, together with the errors dbt printed, when you press a button. A passing run of the same kind (or a build) with the same selection and flags (target, vars, `--full-refresh`, …) clears it; display-only flags such as `--log-format` or `--threads` don't matter, and a whole-project run clears only with the same flags (a passing `dbt retry` never does; a compound command is cleared only by the same command or a whole-project build, and a killed run or output that cannot be split per command, such as output piped through `tail` with its headers cut off, clears nothing) | | Results pane | After Claude runs `dbt show`, or when you run `/dbt-show ` or `/dbt-show select …` | The rows as a table beside the chat, with **Re-run** (Claude's own command with the same flags and folder, unless it depended on its shell, such as a variable or `~`; or your query), **Bookmark**, **Clear history**, the history and your bookmarks (kept on this machine across sessions); several different `dbt show`s in one command save no preview | Nothing | | Model context | When Claude reads a model's `.sql` file | A toast with the counts | The model's materialization, columns with their types, descriptions and tests, its parents and children, and how deep it sits upstream and downstream, from `target/manifest.json` | | Environment doctor | At session start, and `/dbt-doctor` | A line above the prompt when something is wrong: dbt, Python, the profile's adapter, `dbt deps`, and a manifest older than the files it was built from, with **Run dbt parse** or **Run dbt deps** | The checks, with the first prompt after they finish | From d6780bf86a2ef5c187da3ab9dceef8daed4b868e Mon Sep 17 00:00:00 2001 From: Harish Kumar Date: Sat, 14 Nov 2026 06:14:18 +0530 Subject: [PATCH 10/14] =?UTF-8?q?docs:=20dbt=20helpers=20=E2=80=94=20same?= =?UTF-8?q?=20folder=20and=20environment=20to=20clear?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Claude Opus 5.5 --- docs/docs/data-engineering/guides/using-with-claude-code.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/data-engineering/guides/using-with-claude-code.md b/docs/docs/data-engineering/guides/using-with-claude-code.md index 64767744a0..c737f67579 100644 --- a/docs/docs/data-engineering/guides/using-with-claude-code.md +++ b/docs/docs/data-engineering/guides/using-with-claude-code.md @@ -107,7 +107,7 @@ In a dbt project the plugin also does what dbt Power User does in VS Code, insid | Helper | When it runs | What you see | What Claude is told | |---|---|---|---| | Compile and validate | After Claude edits or writes a model's `.sql` file, and again after Claude's next command or edit when the model, a schema file or another SQL file (a macro) changed | A line above the prompt: the model compiled and ran (`dbt show`, one row), with the columns `schema.yml` documents but the query did not return, and those it returned undocumented. When the query returns no row or `schema.yml` documents no columns, it says the columns were not compared. A problem opens the **dbt check** pane with every column, or dbt's whole error | dbt's own error when the model does not compile or run, or the column differences | -| Explain and Fix | After a `dbt run`, `test`, `build`, `seed`, `snapshot` or `retry` Claude ran fails | The failed nodes with **Explain** (Claude explains each failure without changing files) and **Fix with Altimate Code** (runs `/altimate-code:altimate` on the failures) | The failure, read from the `target/run_results.json` the command wrote, together with the errors dbt printed, when you press a button. A passing run of the same kind (or a build) with the same selection and flags (target, vars, `--full-refresh`, …) clears it; display-only flags such as `--log-format` or `--threads` don't matter, and a whole-project run clears only with the same flags (a passing `dbt retry` never does; a compound command is cleared only by the same command or a whole-project build, and a killed run or output that cannot be split per command, such as output piped through `tail` with its headers cut off, clears nothing) | +| Explain and Fix | After a `dbt run`, `test`, `build`, `seed`, `snapshot` or `retry` Claude ran fails | The failed nodes with **Explain** (Claude explains each failure without changing files) and **Fix with Altimate Code** (runs `/altimate-code:altimate` on the failures) | The failure, read from the `target/run_results.json` the command wrote, together with the errors dbt printed, when you press a button. A passing run of the same kind (or a build) with the same selection and flags (target, vars, `--full-refresh`, …) clears it; display-only flags such as `--log-format` or `--threads` don't matter, and a whole-project run clears only with the same flags, run from the same folder with the same environment variables set in the command (a passing `dbt retry` never does; a compound command is cleared only by the same command or a whole-project build, and a killed run or output that cannot be split per command, such as output piped through `tail` with its headers cut off, clears nothing) | | Results pane | After Claude runs `dbt show`, or when you run `/dbt-show ` or `/dbt-show select …` | The rows as a table beside the chat, with **Re-run** (Claude's own command with the same flags and folder, unless it depended on its shell, such as a variable or `~`; or your query), **Bookmark**, **Clear history**, the history and your bookmarks (kept on this machine across sessions); several different `dbt show`s in one command save no preview | Nothing | | Model context | When Claude reads a model's `.sql` file | A toast with the counts | The model's materialization, columns with their types, descriptions and tests, its parents and children, and how deep it sits upstream and downstream, from `target/manifest.json` | | Environment doctor | At session start, and `/dbt-doctor` | A line above the prompt when something is wrong: dbt, Python, the profile's adapter, `dbt deps`, and a manifest older than the files it was built from, with **Run dbt parse** or **Run dbt deps** | The checks, with the first prompt after they finish | From 0bf6a3d4a15db5c2217e4bc5f6258b7e6b5c1a3e Mon Sep 17 00:00:00 2001 From: Harish Kumar Date: Sat, 14 Nov 2026 08:01:56 +0530 Subject: [PATCH 11/14] =?UTF-8?q?docs:=20dbt=20helpers=20=E2=80=94=20Query?= =?UTF-8?q?=20results=20pane=20and=20its=20sizes;=20clearing=20rule?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Claude Opus 5.5 --- docs/docs/data-engineering/guides/using-with-claude-code.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/docs/data-engineering/guides/using-with-claude-code.md b/docs/docs/data-engineering/guides/using-with-claude-code.md index c737f67579..06c3954453 100644 --- a/docs/docs/data-engineering/guides/using-with-claude-code.md +++ b/docs/docs/data-engineering/guides/using-with-claude-code.md @@ -107,8 +107,8 @@ In a dbt project the plugin also does what dbt Power User does in VS Code, insid | Helper | When it runs | What you see | What Claude is told | |---|---|---|---| | Compile and validate | After Claude edits or writes a model's `.sql` file, and again after Claude's next command or edit when the model, a schema file or another SQL file (a macro) changed | A line above the prompt: the model compiled and ran (`dbt show`, one row), with the columns `schema.yml` documents but the query did not return, and those it returned undocumented. When the query returns no row or `schema.yml` documents no columns, it says the columns were not compared. A problem opens the **dbt check** pane with every column, or dbt's whole error | dbt's own error when the model does not compile or run, or the column differences | -| Explain and Fix | After a `dbt run`, `test`, `build`, `seed`, `snapshot` or `retry` Claude ran fails | The failed nodes with **Explain** (Claude explains each failure without changing files) and **Fix with Altimate Code** (runs `/altimate-code:altimate` on the failures) | The failure, read from the `target/run_results.json` the command wrote, together with the errors dbt printed, when you press a button. A passing run of the same kind (or a build) with the same selection and flags (target, vars, `--full-refresh`, …) clears it; display-only flags such as `--log-format` or `--threads` don't matter, and a whole-project run clears only with the same flags, run from the same folder with the same environment variables set in the command (a passing `dbt retry` never does; a compound command is cleared only by the same command or a whole-project build, and a killed run or output that cannot be split per command, such as output piped through `tail` with its headers cut off, clears nothing) | -| Results pane | After Claude runs `dbt show`, or when you run `/dbt-show ` or `/dbt-show select …` | The rows as a table beside the chat, with **Re-run** (Claude's own command with the same flags and folder, unless it depended on its shell, such as a variable or `~`; or your query), **Bookmark**, **Clear history**, the history and your bookmarks (kept on this machine across sessions); several different `dbt show`s in one command save no preview | Nothing | +| Explain and Fix | After a `dbt run`, `test`, `build`, `seed`, `snapshot` or `retry` Claude ran fails | The failed nodes with **Explain** (Claude explains each failure without changing files) and **Fix with Altimate Code** (runs `/altimate-code:altimate` on the failures) | The failure, read from the `target/run_results.json` the command wrote, together with the errors dbt printed, when you press a button. A passing run of the same kind (or a build) with the same selection and flags (target, vars, `--full-refresh`, …) clears it; display-only flags such as `--log-format` or `--threads` don't matter, and any clearing run must use the same flags, run from the same folder, with the same environment variables set in the command (a passing `dbt retry` never does; a compound command is cleared only by the same command or a whole-project build, and a killed run or output that cannot be split per command, such as output piped through `tail` with its headers cut off, clears nothing) | +| Query results pane | After Claude runs `dbt show`, or when you run `/dbt-show ` or `/dbt-show select …` | The rows as a table beside the chat, wide by default and resizable with **Min / Default / Max**, with **Re-run** (Claude's own command with the same flags and folder, unless it depended on its shell, such as a variable or `~`; or your query), **Bookmark**, **Clear history**, the history and your bookmarks (kept on this machine across sessions); several different `dbt show`s in one command save no preview | Nothing | | Model context | When Claude reads a model's `.sql` file | A toast with the counts | The model's materialization, columns with their types, descriptions and tests, its parents and children, and how deep it sits upstream and downstream, from `target/manifest.json` | | Environment doctor | At session start, and `/dbt-doctor` | A line above the prompt when something is wrong: dbt, Python, the profile's adapter, `dbt deps`, and a manifest older than the files it was built from, with **Run dbt parse** or **Run dbt deps** | The checks, with the first prompt after they finish | From 04ac97f56c67ae64e212984006a2e5d660e832b2 Mon Sep 17 00:00:00 2001 From: Harish Kumar Date: Sat, 14 Nov 2026 08:16:18 +0530 Subject: [PATCH 12/14] =?UTF-8?q?docs:=20dbt=20helpers=20=E2=80=94=20pane?= =?UTF-8?q?=20sizes?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Claude Opus 5.5 --- docs/docs/data-engineering/guides/using-with-claude-code.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/data-engineering/guides/using-with-claude-code.md b/docs/docs/data-engineering/guides/using-with-claude-code.md index 06c3954453..8ff92b30f2 100644 --- a/docs/docs/data-engineering/guides/using-with-claude-code.md +++ b/docs/docs/data-engineering/guides/using-with-claude-code.md @@ -108,7 +108,7 @@ In a dbt project the plugin also does what dbt Power User does in VS Code, insid |---|---|---|---| | Compile and validate | After Claude edits or writes a model's `.sql` file, and again after Claude's next command or edit when the model, a schema file or another SQL file (a macro) changed | A line above the prompt: the model compiled and ran (`dbt show`, one row), with the columns `schema.yml` documents but the query did not return, and those it returned undocumented. When the query returns no row or `schema.yml` documents no columns, it says the columns were not compared. A problem opens the **dbt check** pane with every column, or dbt's whole error | dbt's own error when the model does not compile or run, or the column differences | | Explain and Fix | After a `dbt run`, `test`, `build`, `seed`, `snapshot` or `retry` Claude ran fails | The failed nodes with **Explain** (Claude explains each failure without changing files) and **Fix with Altimate Code** (runs `/altimate-code:altimate` on the failures) | The failure, read from the `target/run_results.json` the command wrote, together with the errors dbt printed, when you press a button. A passing run of the same kind (or a build) with the same selection and flags (target, vars, `--full-refresh`, …) clears it; display-only flags such as `--log-format` or `--threads` don't matter, and any clearing run must use the same flags, run from the same folder, with the same environment variables set in the command (a passing `dbt retry` never does; a compound command is cleared only by the same command or a whole-project build, and a killed run or output that cannot be split per command, such as output piped through `tail` with its headers cut off, clears nothing) | -| Query results pane | After Claude runs `dbt show`, or when you run `/dbt-show ` or `/dbt-show select …` | The rows as a table beside the chat, wide by default and resizable with **Min / Default / Max**, with **Re-run** (Claude's own command with the same flags and folder, unless it depended on its shell, such as a variable or `~`; or your query), **Bookmark**, **Clear history**, the history and your bookmarks (kept on this machine across sessions); several different `dbt show`s in one command save no preview | Nothing | +| Query results pane | After Claude runs `dbt show`, or when you run `/dbt-show ` or `/dbt-show select …` | The rows as a table beside the chat, wide by default and resizable with **Min / Default / Max** (25%, 35% and 45% of the terminal, the most Claude Code docks; a size you drag the dock to is kept over the buttons), with **Re-run** (Claude's own command with the same flags and folder, unless it depended on its shell, such as a variable or `~`; or your query), **Bookmark**, **Clear history**, the history and your bookmarks (kept on this machine across sessions); several different `dbt show`s in one command save no preview | Nothing | | Model context | When Claude reads a model's `.sql` file | A toast with the counts | The model's materialization, columns with their types, descriptions and tests, its parents and children, and how deep it sits upstream and downstream, from `target/manifest.json` | | Environment doctor | At session start, and `/dbt-doctor` | A line above the prompt when something is wrong: dbt, Python, the profile's adapter, `dbt deps`, and a manifest older than the files it was built from, with **Run dbt parse** or **Run dbt deps** | The checks, with the first prompt after they finish | From c7cba4699dde8fdc09a53724b29cac8b5e117b77 Mon Sep 17 00:00:00 2001 From: Harish Kumar Date: Sat, 14 Nov 2026 08:28:46 +0530 Subject: [PATCH 13/14] =?UTF-8?q?docs:=20dbt=20helpers=20=E2=80=94=20pane?= =?UTF-8?q?=20sizes?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Claude Opus 5.5 --- docs/docs/data-engineering/guides/using-with-claude-code.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/data-engineering/guides/using-with-claude-code.md b/docs/docs/data-engineering/guides/using-with-claude-code.md index 8ff92b30f2..03aaf8970c 100644 --- a/docs/docs/data-engineering/guides/using-with-claude-code.md +++ b/docs/docs/data-engineering/guides/using-with-claude-code.md @@ -108,7 +108,7 @@ In a dbt project the plugin also does what dbt Power User does in VS Code, insid |---|---|---|---| | Compile and validate | After Claude edits or writes a model's `.sql` file, and again after Claude's next command or edit when the model, a schema file or another SQL file (a macro) changed | A line above the prompt: the model compiled and ran (`dbt show`, one row), with the columns `schema.yml` documents but the query did not return, and those it returned undocumented. When the query returns no row or `schema.yml` documents no columns, it says the columns were not compared. A problem opens the **dbt check** pane with every column, or dbt's whole error | dbt's own error when the model does not compile or run, or the column differences | | Explain and Fix | After a `dbt run`, `test`, `build`, `seed`, `snapshot` or `retry` Claude ran fails | The failed nodes with **Explain** (Claude explains each failure without changing files) and **Fix with Altimate Code** (runs `/altimate-code:altimate` on the failures) | The failure, read from the `target/run_results.json` the command wrote, together with the errors dbt printed, when you press a button. A passing run of the same kind (or a build) with the same selection and flags (target, vars, `--full-refresh`, …) clears it; display-only flags such as `--log-format` or `--threads` don't matter, and any clearing run must use the same flags, run from the same folder, with the same environment variables set in the command (a passing `dbt retry` never does; a compound command is cleared only by the same command or a whole-project build, and a killed run or output that cannot be split per command, such as output piped through `tail` with its headers cut off, clears nothing) | -| Query results pane | After Claude runs `dbt show`, or when you run `/dbt-show ` or `/dbt-show select …` | The rows as a table beside the chat, wide by default and resizable with **Min / Default / Max** (25%, 35% and 45% of the terminal, the most Claude Code docks; a size you drag the dock to is kept over the buttons), with **Re-run** (Claude's own command with the same flags and folder, unless it depended on its shell, such as a variable or `~`; or your query), **Bookmark**, **Clear history**, the history and your bookmarks (kept on this machine across sessions); several different `dbt show`s in one command save no preview | Nothing | +| Query results pane | After Claude runs `dbt show`, or when you run `/dbt-show ` or `/dbt-show select …` | The rows as a table beside the chat, resizable with **Min / Default / Max** (Default is the widest dock beside the chat; Min narrows it to a quarter; Max is as wide as Default and taller above the prompt; a size you drag yourself wins), with **Re-run** (Claude's own command with the same flags and folder, unless it depended on its shell, such as a variable or `~`; or your query), **Bookmark**, **Clear history**, the history and your bookmarks (kept on this machine across sessions); several different `dbt show`s in one command save no preview | Nothing | | Model context | When Claude reads a model's `.sql` file | A toast with the counts | The model's materialization, columns with their types, descriptions and tests, its parents and children, and how deep it sits upstream and downstream, from `target/manifest.json` | | Environment doctor | At session start, and `/dbt-doctor` | A line above the prompt when something is wrong: dbt, Python, the profile's adapter, `dbt deps`, and a manifest older than the files it was built from, with **Run dbt parse** or **Run dbt deps** | The checks, with the first prompt after they finish | From 858ec34b2f07b4d4ae2e044f462e7ddcb293ba68 Mon Sep 17 00:00:00 2001 From: Harish Kumar Date: Sat, 14 Nov 2026 09:26:27 +0530 Subject: [PATCH 14/14] =?UTF-8?q?docs:=20dbt=20helpers=20=E2=80=94=20model?= =?UTF-8?q?-provider=20calls=20and=20the=20clearing=20rule=20stated=20once?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Claude Opus 5.5 --- docs/docs/data-engineering/guides/using-with-claude-code.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/docs/data-engineering/guides/using-with-claude-code.md b/docs/docs/data-engineering/guides/using-with-claude-code.md index 03aaf8970c..1142d230b7 100644 --- a/docs/docs/data-engineering/guides/using-with-claude-code.md +++ b/docs/docs/data-engineering/guides/using-with-claude-code.md @@ -102,12 +102,12 @@ The plugin runs `altimate-code run` in your project for each task, with the mode ### dbt helpers beside the chat -In a dbt project the plugin also does what dbt Power User does in VS Code, inside the Claude Code session. Each helper runs the project's own dbt (from a `.venv` or `venv` in the project folder when there is one, else `dbt` on `PATH`) and calls no model: +In a dbt project the plugin also does what dbt Power User does in VS Code, inside the Claude Code session. Each helper runs the project's own dbt (from a `.venv` or `venv` in the project folder when there is one, else `dbt` on `PATH`) and makes no model-provider call on its own (only **Explain** and **Fix with Altimate Code**, when you press them, hand a failure to Claude or Altimate Code): | Helper | When it runs | What you see | What Claude is told | |---|---|---|---| | Compile and validate | After Claude edits or writes a model's `.sql` file, and again after Claude's next command or edit when the model, a schema file or another SQL file (a macro) changed | A line above the prompt: the model compiled and ran (`dbt show`, one row), with the columns `schema.yml` documents but the query did not return, and those it returned undocumented. When the query returns no row or `schema.yml` documents no columns, it says the columns were not compared. A problem opens the **dbt check** pane with every column, or dbt's whole error | dbt's own error when the model does not compile or run, or the column differences | -| Explain and Fix | After a `dbt run`, `test`, `build`, `seed`, `snapshot` or `retry` Claude ran fails | The failed nodes with **Explain** (Claude explains each failure without changing files) and **Fix with Altimate Code** (runs `/altimate-code:altimate` on the failures) | The failure, read from the `target/run_results.json` the command wrote, together with the errors dbt printed, when you press a button. A passing run of the same kind (or a build) with the same selection and flags (target, vars, `--full-refresh`, …) clears it; display-only flags such as `--log-format` or `--threads` don't matter, and any clearing run must use the same flags, run from the same folder, with the same environment variables set in the command (a passing `dbt retry` never does; a compound command is cleared only by the same command or a whole-project build, and a killed run or output that cannot be split per command, such as output piped through `tail` with its headers cut off, clears nothing) | +| Explain and Fix | After a `dbt run`, `test`, `build`, `seed`, `snapshot` or `retry` Claude ran fails | The failed nodes with **Explain** (Claude explains each failure without changing files) and **Fix with Altimate Code** (runs `/altimate-code:altimate` on the failures) | The failure, read from the `target/run_results.json` the command wrote, together with the errors dbt printed, when you press a button. A passing run of the same kind (or a build) clears it when it matches the failed one: the same selection, the same flags (target, vars, `--full-refresh`, …), the same folder and the same environment variables set in the command. Flags that change only the output or the concurrency, such as `--log-format` or `--threads`, are ignored (a passing `dbt retry` never clears it; a compound command is cleared only by the same command or a whole-project build, and a killed run or output that cannot be split per command, such as output piped through `tail` with its headers cut off, clears nothing) | | Query results pane | After Claude runs `dbt show`, or when you run `/dbt-show ` or `/dbt-show select …` | The rows as a table beside the chat, resizable with **Min / Default / Max** (Default is the widest dock beside the chat; Min narrows it to a quarter; Max is as wide as Default and taller above the prompt; a size you drag yourself wins), with **Re-run** (Claude's own command with the same flags and folder, unless it depended on its shell, such as a variable or `~`; or your query), **Bookmark**, **Clear history**, the history and your bookmarks (kept on this machine across sessions); several different `dbt show`s in one command save no preview | Nothing | | Model context | When Claude reads a model's `.sql` file | A toast with the counts | The model's materialization, columns with their types, descriptions and tests, its parents and children, and how deep it sits upstream and downstream, from `target/manifest.json` | | Environment doctor | At session start, and `/dbt-doctor` | A line above the prompt when something is wrong: dbt, Python, the profile's adapter, `dbt deps`, and a manifest older than the files it was built from, with **Run dbt parse** or **Run dbt deps** | The checks, with the first prompt after they finish |