Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
57 commits
Select commit Hold shift + click to select a range
56df42a
feat: dbt helpers from dbt Power User in Claude Code sessions (1.6.0)
hkaltai Nov 13, 2026
317fa73
docs: the dbt check pane in the README and changelog
hkaltai Nov 13, 2026
919f4bb
fix: dbt helpers review round 1
hkaltai Nov 13, 2026
c32df61
fix: dbt helpers review round 2
hkaltai Nov 13, 2026
70581b4
fix: dbt helpers review round 3
hkaltai Nov 13, 2026
fe1793d
fix: dbt helpers review round 4
hkaltai Nov 13, 2026
5f9f635
fix: dbt helpers review round 5
hkaltai Nov 13, 2026
73e5378
fix: dbt helpers — per-command failure verdicts, conservative clearin…
hkaltai Nov 13, 2026
9f5861f
fix: dbt helpers — versioned model selection, doctor inventory, flag …
hkaltai Nov 13, 2026
8091017
fix: dbt helpers — doctor inventory scope, versioned model retry, pro…
hkaltai Nov 13, 2026
9e97fa2
fix: dbt helpers — versioned model retry replaces the old name
hkaltai Nov 13, 2026
30d9468
fix: dbt helpers — keep every failure and the full command for Explai…
hkaltai Nov 13, 2026
26555ab
fix: dbt helpers — failure identity covers every flag that changes wh…
hkaltai Nov 13, 2026
bf87c91
fix: dbt helpers — flag order and per-command contexts in failure ide…
hkaltai Nov 13, 2026
db18a23
fix: dbt helpers — invocation folder in failure identity; one failure…
hkaltai Nov 13, 2026
e19bf83
fix: dbt helpers — effective value for boolean flag pairs; environmen…
hkaltai Nov 14, 2026
55e2138
feat: Query results and lineage pane sizes; fix: versioned failures, …
hkaltai Nov 14, 2026
eb3e53c
fix: dbt helpers — one entry per failed version, pane sizes as shares…
hkaltai Nov 14, 2026
d8faec5
fix: dbt helpers — Default pane size is the widest dock; doctor follo…
hkaltai Nov 14, 2026
d02d256
fix: dbt helpers — text previews cut at the table's column rule; doct…
hkaltai Nov 14, 2026
a3a3f23
fix: dbt helpers — doctor reads profiles.yml with a YAML parser; prev…
hkaltai Nov 14, 2026
b41c898
fix: dbt helpers — embedded Python runs in dbt's interpreter and igno…
hkaltai Nov 14, 2026
045fd2d
docs: README — model-provider calls and the clearing rule stated once
hkaltai Nov 14, 2026
1b76a1c
fix: dbt helpers — large run_results through Python, honest manifest …
hkaltai Nov 14, 2026
14d2674
fix: dbt helpers — unreadable manifest named when rows came back; run…
hkaltai Nov 14, 2026
a5e6539
fix: pane sizes from the terminal width, not a docked pane's viewport…
hkaltai Nov 16, 2026
41bcb3f
docs: columnWidths comment matches the order spare room is given
hkaltai Nov 16, 2026
196fea2
Merge origin/main into feat/implement-items-7-8-9-12-15-with-e2e-demo…
hkaltai Nov 17, 2026
6eefc09
fix: dbt helpers — no profiles.yml secret reaches Claude or the panes…
hkaltai Nov 17, 2026
117336f
fix: dbt helpers — dbt unrunnable only when dbt itself is missing; ls…
hkaltai Nov 17, 2026
5da97f2
Merge branch 'main' into feat/implement-items-7-8-9-12-15-with-e2e-demo
hkaltai Nov 17, 2026
cb409cc
fix: dbt helpers — dash-style 'not found' parsed; a query whose SQL a…
hkaltai Nov 17, 2026
2ebe8a6
docs: CHANGELOG — profiles.yml wording
hkaltai Nov 17, 2026
3c4c18f
fix: dbt helpers — every dbt error about the profile replaced at one …
hkaltai Nov 17, 2026
e7e25a6
docs: CHANGELOG — scope of the profiles.yml guarantee
hkaltai Nov 17, 2026
29dc2d0
test: dbt-scripts gets PyYAML from a throwaway venv when the runner's…
hkaltai Nov 17, 2026
11129c0
Merge origin/main into feat/implement-items-7-8-9-12-15-with-e2e-demo…
hkaltai Nov 17, 2026
a2572af
fix: a model's own missing env_var keeps dbt's error; README privacy …
hkaltai Nov 17, 2026
bef5422
fix: /dbt-show opens no pane after a /clear during its first awaits; …
hkaltai Nov 17, 2026
2c196bb
fix: dbt helpers — profiles.yml values redacted from every dbt output…
hkaltai Nov 17, 2026
8b23c76
Merge origin/main and integrate the dbt helpers with the feature foun…
hkaltai Nov 17, 2026
bfcb1d4
fix: dbt helpers — redaction reloads after /clear, follows the profil…
hkaltai Nov 17, 2026
f87d721
fix: dbt helpers — secret profile values redacted from dbt's messages…
hkaltai Nov 17, 2026
2d1541e
fix: dbt helpers — profile templates rendered with Jinja to find env …
hkaltai Nov 17, 2026
a2954ca
fix: dbt helpers — Python repr forms and values set for the command a…
hkaltai Nov 17, 2026
b0fb341
docs: state the bounds of profile value redaction — what it matches a…
hkaltai Nov 17, 2026
5f5af0e
fix: an inherited relative DBT_PROFILES_DIR is read from the folder t…
hkaltai Nov 17, 2026
6b22aae
test: dbt-scripts runs the profile scripts with PyYAML and jinja2, as…
hkaltai Nov 17, 2026
1a9d7c0
Merge origin/main into feat/implement-items-7-8-9-12-15-with-e2e-demo
hkaltai Nov 18, 2026
d793b0e
test: keep the docs tests free of the dbt helpers, and hold the dbt h…
hkaltai Nov 18, 2026
b21ee75
fix: scrub dbt debug's error before cutting it, and load a shared pro…
hkaltai Nov 18, 2026
5a0dcc7
docs: say which artifact folder the dbt helpers read
hkaltai Nov 18, 2026
feb9afa
docs: narrow the artifact folder note
hkaltai Nov 18, 2026
488d2d1
docs: the artifact folder note also covers a Jinja target-path
hkaltai Nov 18, 2026
19a1700
Merge origin/main into feat/implement-items-7-8-9-12-15-with-e2e-demo
hkaltai Nov 18, 2026
a7ff8dc
Merge origin/main into feat/implement-items-7-8-9-12-15-with-e2e-demo
hkaltai Nov 18, 2026
a56d3b6
fix: a call waits for the profile values another is loading, a date-s…
hkaltai Nov 18, 2026
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .claude-plugin/marketplace.json
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@
},
"metadata": {
"description": "Altimate's Claude Code plugin — data tools through the altimate-code MCP server, or the model-free CLI where MCP is disallowed, plus delegation of long dbt jobs to the CLI agent.",
"version": "1.7.0"
"version": "1.8.0"
},
"plugins": [
{
Expand Down
5 changes: 4 additions & 1 deletion CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,10 @@ altimate-claude-plugin/
│ ├── hooks/
│ │ ├── hooks.json # SessionStart, UserPromptSubmit, Stop and PreToolUse hook config
│ │ ├── integrations.tsx # one-click integrations band and /integrations pane (mod)
│ │ └── integrations.test.tsx # its tests (claude plugin test .)
│ │ ├── integrations.test.tsx # its tests (claude plugin test .)
│ │ ├── dbt-mods.tsx # dbt helpers: compile and validate, Explain/Fix, results pane, model context, doctor
│ │ ├── dbt-mods-core.ts # what they read from dbt's output and files
│ │ └── dbt-mods.test.tsx # their tests
│ ├── types/
│ │ └── index.d.ts # types for the mod
│ ├── hooks-handlers/
Expand Down
10 changes: 9 additions & 1 deletion PRIVACY.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
# Privacy Policy — Altimate Code plugin for Claude Code

**Effective date:** November 2, 2026
**Last revised:** November 13, 2026
**Last revised:** November 17, 2026
**Applies to:** the `altimate-code` Claude Code plugin distributed from this repository, and the data flows it initiates through the [altimate-code](https://github.com/AltimateAI/altimate-code) MCP server and CLI.

This policy supplements the Altimate AI [Privacy Policy](https://www.altimate.ai/privacy) and [Terms](https://www.altimate.ai/terms), which govern Altimate services generally. Where this document is silent, the master policy applies. Questions: **info@altimate.ai**.
Expand Down Expand Up @@ -30,6 +30,12 @@ The plugin registers a local stdio MCP server through `.mcp.json`, provides rout
| Schema metadata, sampled column values, and query results returned by tools | Local MCP server → Claude Code conversation → your configured model provider | Governed by Claude Code and your model provider's policies |
| Scratch tables and spilled query results | Local session storage or spill files; any content Claude reads enters the conversation and reaches your model provider | Local artifacts; conversation copies follow Claude Code and provider policies |

## dbt helpers

In a dbt project the plugin's hooks module runs the project's own dbt on this machine (`dbt show`, `dbt parse`, `dbt --version`, and `dbt debug` when you ask): after Claude edits a model, at session start, and when you press a button. Those commands connect to your warehouse with your local profile. What the helpers give Claude (dbt's errors, column names, the manifest's facts about a model, the environment check) enters the Claude Code conversation and reaches your model provider. Rows from `dbt show` that the results pane keeps (up to 50 per query, long cells cut, and the last 20 queries) stay in Claude Code's local plugin store until you press **Clear history**; they are not sent anywhere by the plugin. Bookmarked queries (at most 50) are the exception: **Clear history** keeps them and their rows. They are kept with the plugin's other saved settings in Claude Code's plugin store under the Claude Code configuration directory, in files only your user can read, and turning `dbt_mods` off does not delete them; to delete one, un-bookmark it and press **Clear history**. Set the plugin's `dbt_mods` option to false to turn the helpers off.

Opening a dbt folder runs programs the repository supplies, with no action from you: at session start the plugin runs the project's own `.venv/bin/dbt --version` (a `venv` or `Scripts\dbt.exe` too) and the Python that dbt's launcher names. Secret values from the `profiles.yml` a dbt command reads (the one its `--profiles-dir` or `DBT_PROFILES_DIR` names, else the one in the folder it ran in, the project's, or `~/.dbt`'s: the string fields of its outputs, and the env vars it names with their defaults) are removed from dbt's messages (errors, logs, the doctor's details, the failure band, Explain and Fix, and the error text kept in the query history) that the helpers show, save or send, and dbt's errors about a `profiles.yml` it cannot read, validate or render are replaced with a fixed message. Identifiers such as schema, database, dataset, project, catalog, warehouse, role and user are not treated as secrets, nor are values under 6 characters or the `type`, `threads`, `method` and `port` fields; query results and manifest facts are shown as they are. The plugin reads those values locally, keeps them in memory only, and never logs, stores or sends them. Redaction is best effort, not a guarantee about every text dbt prints: it matches those values as written, JSON-escaped and in Python's string and byte forms, including values set for the command (`NAME=value dbt …`, `env`, `export`); it cannot catch a value dbt or an adapter prints in another form (encoded, transformed or split), or one the profile builds other than through `env_var`. Other dbt errors (a missing target or profile name, a model's own missing `env_var`) are kept, since they carry no secret. Claude's own dbt commands show their output to Claude unchanged; the plugin does not alter Claude's tool results.

Direct local data tools do not invoke a planning model. Workspace tools have the additional service flows below; delegation uses the separate provider path described later.

## Data flows for workspace tools
Expand Down Expand Up @@ -151,6 +157,8 @@ The plugin and the altimate-code CLI are professional developer tools, not direc

We will update this document in this repository and revise the effective date when our practices change. Material changes to Altimate-wide practices are governed by the master [Privacy Policy](https://www.altimate.ai/privacy).

**November 17, 2026:** added [dbt helpers](#dbt-helpers) (plugin 1.8.0): the dbt commands the plugin runs in a dbt project, and what it keeps of their results.

**November 16, 2026:** added [The lineage report](#the-lineage-report) (plugin 1.6.0): the offline report page, and the usage events the altimate-code CLI sends for it.

**November 10, 2026:** added [Workspace rules](#workspace-rules) (the workspace-rules hooks and `/altimate-code:rules` in plugin 1.5.0), and the rules telemetry the altimate-code CLI sends.
Expand Down
8 changes: 7 additions & 1 deletion plugins/altimate-code/.claude-plugin/plugin.json
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
{
"name": "altimate-code",
"displayName": "Altimate Code",
"version": "1.7.0",
"version": "1.8.0",
"description": "Gives Claude Code altimate-code's model-free data tools (column-level lineage, impact analysis, PII detection, data-diff, FinOps, query equivalence, dialect translation, warehouse queries) through its MCP server, or through `altimate tool run` when MCP servers are not allowed, with delegation to the altimate-code agent for long dbt jobs, access to a linked Altimate workspace's knowledge, and the workspace's team rules in each session.",
"author": {
"name": "AltimateAI",
Expand All @@ -22,6 +22,12 @@
],
"types": "./types/index.d.ts",
"userConfig": {
"dbt_mods": {
"type": "boolean",
"title": "dbt helpers",
"description": "Compile and validate each model Claude edits, Explain and Fix on a failed dbt run, the Query results pane, model context on read, and the dbt environment doctor at session start. They run the project's own dbt.",
"default": true
},
"maxScanBytes": {
"type": "number",
"title": "Largest BigQuery scan without asking (not used yet)",
Expand Down
18 changes: 18 additions & 0 deletions plugins/altimate-code/CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,24 @@

All notable changes to this plugin will be documented in this file.

## [1.8.0] — 2026-11-17

### Added
- dbt helpers from dbt Power User, in the Claude Code session. Each runs the project's own dbt (its `.venv/bin/dbt` when there is one) and calls no model:
- **Compile and validate.** After Claude edits or writes a model, the plugin runs it with `dbt show` (one row) against the warehouse. dbt's error, or the columns `schema.yml` documents that the query no longer returns and those it returns undocumented, go to Claude with the edit's result and to a line above the prompt; the **dbt check** pane shows every column, or dbt's whole error. The check says when the columns could not be compared, and runs again when the model or its schema file changes outside Claude's edits.
- **Explain and Fix.** A failed `dbt run`, `test`, `build`, `seed`, `snapshot` or `retry` puts the failed nodes, read from the `run_results.json` the command wrote together with the errors dbt printed, above the prompt with **Explain** and **Fix with Altimate Code** (`/altimate-code:altimate`).
- **Query results pane.** Rows from Claude's `dbt show`, `/dbt-show <model>` and `/dbt-show select …` open 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; or your query), **Bookmark**, **Clear history** and a history kept across sessions on this machine. It opens at the widest dock, and **Min / Default / Max** resize it (the lineage pane has them too); the choice is kept across sessions.
- **Model context.** When Claude reads a model, its materialization, columns (types, descriptions, tests), parents, children and depth upstream and downstream, from `target/manifest.json`, go with the file, once a turn.
- **Environment doctor.** At session start the plugin checks dbt, Python, the profile's adapter, installed packages and whether the manifest is older than the project's files, and offers **Run dbt parse** (or **Run dbt deps**). `/dbt-doctor` runs the checks with the warehouse connection test.
- Compile and validate runs one `dbt show` per edit (with `dbt ls`, which runs no query, first when the manifest does not name the model). It skips a model whose path holds a space, says "dbt could not be run here" when dbt cannot be started, and asks Claude to fix the model only for errors that are the model's own.
- Secret values from the `profiles.yml` a dbt command reads (the one its `--profiles-dir` or `DBT_PROFILES_DIR` names, else the one in the folder it ran in, the project's, or `~/.dbt`'s: the string fields of its outputs, and the env vars it names with their defaults) are removed from dbt's messages (errors, logs, the doctor's details, the failure band, Explain and Fix, and the error text kept in the query history) that the helpers show, save or send, and dbt's errors about a `profiles.yml` it cannot read, validate or render are replaced with a fixed message. Identifiers such as schema, database, dataset, project, catalog, warehouse, role and user are not treated as secrets, nor are values under 6 characters or the `type`, `threads`, `method` and `port` fields; query results and manifest facts are shown as they are. The plugin reads those values locally, keeps them in memory only, and never logs, stores or sends them. Redaction is best effort, not a guarantee about every text dbt prints: it matches those values as written, JSON-escaped and in Python's string and byte forms, including values set for the command (`NAME=value dbt …`, `env`, `export`); it cannot catch a value dbt or an adapter prints in another form (encoded, transformed or split), or one the profile builds other than through `env_var`. Other dbt errors (a missing target or profile name, a model's own missing `env_var`) are kept, since they carry no secret. A dbt command Claude runs itself shows its output to Claude unchanged. The fixed message is "profiles.yml could not be parsed; run `dbt debug` yourself to see the error"; it replaces the error on every surface: the compile-and-validate note, the check pane, the band, Explain and Fix, `/dbt-show` and its saved history, and the doctor.
- Saved queries cut long cells and drop rows to stay within 32 KiB each (a query whose SQL alone is larger is kept whole, within the history's 2 MiB total); bookmarks are capped at 50.
- Artifacts are read from the `target-path` of `dbt_project.yml`; `DBT_TARGET_PATH`, `--target-path` and a Jinja `target-path` are not followed.
- The `dbt_mods` option turns the dbt helpers off.

### Privacy
- README and PRIVACY say that opening a dbt folder runs the project's `.venv` dbt `--version` and its Python at session start, and that bookmarked queries keep their rows after **Clear history** in Claude Code's plugin store.

## [1.7.0] — 2026-11-17

### Added
Expand Down
Loading
Loading