Skip to content
Merged
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.8.1"
"version": "1.8.2"
},
"plugins": [
{
Expand Down
24 changes: 21 additions & 3 deletions 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 17, 2026
**Last revised:** November 19, 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 All @@ -16,11 +16,12 @@ This policy supplements the Altimate AI [Privacy Policy](https://www.altimate.ai
- When a task **is** delegated, your task text is passed to the altimate-code CLI, which sends it to an LLM provider to plan and execute the work — the Altimate LLM Gateway by default, or a provider you configure (BYOK).
- Warehouse queries, dbt commands, and file edits run **locally on your machine, under your credentials**. Your warehouse credentials are never sent to Altimate.
- In a project linked to an Altimate workspace, the plugin copies the workspace's team skills into the project's `.claude/skills/` and refreshes them from Altimate in the background at session start and at most hourly. Their text loads into the Claude Code conversation like any project skill. `ALTIMATE_CLAUDE_SKILL_SYNC=0` turns this off and removes the copies at the next session start.
- The plugin counts its own use anonymously, through the altimate-code CLI's usage telemetry: one event at each session start (plugin and altimate-code versions, OS, a random install id) and one each time a panel or command opens or a gate holds or allows a command (its name and outcome). No session id, project, model, column or file names, SQL or session text, and nothing that links them to your account or to the CLI's other telemetry. `ALTIMATE_TELEMETRY_DISABLED=true` turns it off. See [Plugin usage events](#plugin-usage-events).

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor (Codex and Claude): "anonymously" and "cannot be joined" overclaim.

Every event carries the same persistent install_id. It survives sessions, plugin updates and even uninstall (see the comment on line 120). That makes the events pseudonymous, not anonymous: one install's activity can be linked across sessions and days.

Line 121's "cannot be joined to the CLI's other telemetry" is also too strong. The ingestion endpoint sees the same client IP (Application Insights derives location from it) and near-identical timestamps on these events and on the CLI's other events from the same machine.

Suggested wording: "pseudonymous, keyed to a random per-install id that is not linked to your account or machine id". README line 184 repeats "anonymously" and needs the same change. This is wording only and does not block.

- Installing the plugin is an explicit act — `/plugin marketplace add` does not install it, and `/plugin install` never auto-runs. Nothing is delegated until the plugin is installed and you send a task that matches the skill.

## What the plugin does and does not do

The plugin registers a local stdio MCP server through `.mcp.json`, provides routing skills and slash commands, and runs hooks: SessionStart prints a capability description and, with Stop, keeps the linked workspace's skills copied into the project (see below); in a linked project, the workspace-rules hooks (SessionStart, UserPromptSubmit and Stop) start the local altimate-code CLI (see [Workspace rules](#workspace-rules)); an opt-in PreToolUse guard checks Bash commands locally. The server reads configured connections and runs data tools under your local credentials. The plugin adds no analytics of its own; CLI telemetry is described below.
The plugin registers a local stdio MCP server through `.mcp.json`, provides routing skills and slash commands, and runs hooks: SessionStart prints a capability description and, with Stop, keeps the linked workspace's skills copied into the project (see below); in a linked project, the workspace-rules hooks (SessionStart, UserPromptSubmit and Stop) start the local altimate-code CLI (see [Workspace rules](#workspace-rules)); an opt-in PreToolUse guard checks Bash commands locally. The server reads configured connections and runs data tools under your local credentials. The plugin opens no network connection of its own for analytics: its anonymous usage events go through the altimate-code CLI's telemetry (see [Plugin usage events](#plugin-usage-events)), which is described below.

## Data flows through MCP tools

Expand Down Expand Up @@ -105,7 +106,22 @@ To learn whether the report gets used, the plugin asks the local altimate-code C
- `/lineage-report` was run;
- the report was built, failed to build, or found no browser.

Each event carries the step and the Claude Code session id (`claude:<id>`) only: no model, column, file or project names. It goes through Altimate's usage telemetry, described in [Usage telemetry](#usage-telemetry), and that section's opt-out turns it off. With an altimate-code that predates the command, nothing is sent.
Each event carries the step and the Claude Code session id (`claude:<id>`) only: no model, column, file or project names. It goes through Altimate's usage telemetry, described in [Usage telemetry](#usage-telemetry), and that section's opt-out turns it off; with `ALTIMATE_TELEMETRY_DISABLED` set, the plugin does not start the CLI for it. With an altimate-code that predates the command, nothing is sent.

## Plugin usage events

To count installs, active use and which features are used, the plugin asks the local altimate-code CLI (`altimate-code tool report-event`) to send these events through Altimate's usage telemetry, described in [Usage telemetry](#usage-telemetry). The plugin itself contacts no server for them.

| Event | When | Fields |
|---|---|---|
| `plugin_session_start` | Each time Claude Code starts a session with the plugin enabled | `plugin_version`; `altimate_code_version` (added by the CLI); `host_os` (the plugin passes it as `--os`): `macos`, `linux`, `windows`, `wsl` or `unknown`; `install_id` |
| `plugin_feature_used` | A panel or command opens: `/lineage` or the summary's **Open lineage** (`lineage`), `/dbt-show` (`dbt_show`), `/profile-ctes` (`profile_ctes`), `/scan-cost` (`scan_cost`), `/comments` or the band's **Open** (`comments`), `/sql-graph` (`sql_graph`), `/health` (`health`), `/runs` (`runs`), `/to-model` (`to_model`); the cost check holds a dbt command or `/allow-scan` allows it (`cost_gate`); with "Project health blocks git push" on, the push gate holds or lets through a `git push` (`health_push_gate`). Panes the plugin opens on its own, following Claude, are not counted | `feature` (the name in brackets); `outcome`: `opened`, `failed` (the panel could not open or be shown), `held` or `allowed`; `plugin_version`; `install_id` |

- **`install_id`** is a random UUID the plugin makes the first time it sends an event and keeps in its own Claude Code plugin store (a JSON file under your Claude Code configuration directory), so it stays the same across sessions on this machine. It is not derived from your machine, account or project, and is not made while `ALTIMATE_TELEMETRY_DISABLED` is set. Removing the plugin's store data makes a new one.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor (Claude, Codex accepts): say where the install id is kept, and that uninstalling keeps it.

In Claude Code 2.1.328 $.store is one JSON file per plugin id: ~/.claude/plugins/store/altimate-code_<marketplace>-<sha256[:12]>.json (under CLAUDE_CONFIG_DIR when that is set). It is keyed by name and marketplace, not version, so plugin updates keep it.

I tested this in an isolated config dir. claude plugin uninstall altimate-code@altimate-claude-plugin left the file in place, and so did --keep-data. A reinstall therefore sends the same id. "Removing the plugin's store data makes a new one" is true, but the reader is not told where that file is or that uninstalling does not remove it.

Two related notes:

  • A --plugin-dir load has a different plugin id, so it gets a different store file and a different id.
  • From reading the binary, not tested: the store folder appears to be included in Claude Code's cleanupPeriodDays sweep (30 days by default), so an install left unused that long may get a new id.

Docs only.

- Beside these fields, each event carries only the CLI version (`cli_version`), the client name (`client`: `altimate-code`) and how the CLI was started (`source`: `cli`, unless `ALTIMATE_CLI_CLIENT` names another client). Unlike the CLI's other events, these carry no session id, no machine id, no project id, no per-launch id and never your Altimate account (no user id or tenant), even when you are signed in, so they cannot be joined to the CLI's other telemetry.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor (Codex, verified): the "carries only" list leaves out what the envelope adds, and one opt-out alias.

What the #1775 CLI sent to my local sink for each event:

  • tags: ai.user.id = the install_id, ai.session.id = "", ai.cloud.role, ai.application.ver;
  • the event time;
  • the iKey.

Only cli_version, client and source are listed here.

Also, OPENCODE_DISABLE_TELEMETRY (true/1/TRUE) turns the events off and stops the install id from being made (usage.ts:47). The CHANGELOG names it, but this section and the README don't. Docs only.

- No event contains project, model, column or file names, SQL, query results or session text. The CLI accepts each field only from a fixed list or pattern (a version, a UUID, one of the names above) and refuses anything else.
- **Turning it off:** `ALTIMATE_TELEMETRY_DISABLED=true` (or `1`) in the environment Claude Code starts in: the plugin then starts no CLI for these events, or for the lineage report's, and makes no install id. The CLI also drops them under its own opt-out (`ALTIMATE_TELEMETRY_DISABLED`, or `telemetry.disabled` in its config), as for every other event.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor (Claude, Codex accepts): with only the CLI's config opt-out, the plugin still makes the id and starts the CLI for every event.

usageOff reads only the two environment variables, as it must, because the plugin cannot read altimate-code's config. So with telemetry.disabled: true in that config and no env var set:

  • readOrMakeId still writes usage.installId to the store;
  • every event still starts one altimate tool report-event process. Each took 2–4 s of wall time in my runs of the #1775 build, in the background.

The CLI then drops the event: nothing reached my local sink. But on a machine that already has ~/.altimate/machine-id, the first such launch sends the CLI's one-time telemetry_opted_out event, which carries the machine id. That behaviour predates this PR, and any CLI launch does it.

Suggest one sentence here: "with only the config opt-out, the plugin cannot tell; it still keeps an install id and starts the CLI, which sends nothing." Docs only.

- The events are sent in the background and never delay a hook. An altimate-code that predates them refuses them, and nothing is sent or shown.

## Data flows when a task is delegated

Expand Down Expand Up @@ -157,6 +173,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 19, 2026:** added [Plugin usage events](#plugin-usage-events) (plugin 1.8.2): the anonymous session start and feature-used events, and the plugin's own check of the telemetry opt-out.

**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.
Expand Down
2 changes: 1 addition & 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.8.1",
"version": "1.8.2",
"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 Down
9 changes: 9 additions & 0 deletions plugins/altimate-code/CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,15 @@

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

## [1.8.2] — 2026-11-19

### Added
- Anonymous usage events, sent through altimate-code's usage telemetry (`altimate-code tool report-event`); the plugin opens no network connection of its own for them. `plugin_session_start` at each session start carries the plugin version, the altimate-code version (added by the CLI), the OS (`macos`, `linux`, `windows`, `wsl` or `unknown`) and an install id: a random UUID made on first use and kept in the plugin's Claude Code store, so it stays the same across sessions on the machine. `plugin_feature_used` carries the feature and its outcome when `/lineage`, `/dbt-show`, `/profile-ctes`, `/scan-cost`, `/comments`, `/sql-graph`, `/health`, `/runs` or `/to-model` opens (`opened`, or `failed` when its pane could not open), when the cost check holds a dbt command (`held`) or `/allow-scan` allows it (`allowed`), and, with "Project health blocks git push" on, when the push gate holds or lets through a `git push`. No session id, project, model, column or file names, SQL or session text: the CLI takes each field only from a fixed list or pattern, and sends these events without the account, machine id or project its other events carry. A panel counts when a person opens it (its command, or the band's Open lineage or Open); `failed` when it could not open or be shown. Every event and field is listed in PRIVACY.md.
- The events need an altimate-code with the `plugin_session_start` and `plugin_feature_used` actions; an older one refuses them and nothing is sent or shown. They run in the background and never delay a hook.

### Changed
- With `ALTIMATE_TELEMETRY_DISABLED` (or `OPENCODE_DISABLE_TELEMETRY`) set to `true` or `1`, the plugin no longer starts the CLI for any usage event (the lineage report's included) and makes no install id. The CLI's own opt-out (that variable, or `telemetry.disabled` in its config) still drops them too.

## [1.8.1] — 2026-11-19

### Fixed
Expand Down
2 changes: 2 additions & 0 deletions plugins/altimate-code/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -181,6 +181,8 @@ MCP tools and `tool run` run locally under your credentials; tool results Claude

The dbt helpers run the project's dbt on this machine. What they add to Claude's context (dbt's errors, column names, the manifest's facts about a model) reaches its model provider like any tool result. The rows of the Query results pane are kept on this machine only, in Claude Code's plugin store, until you clear them (bookmarked queries keep their rows through **Clear history**, and turning `dbt_mods` off does not delete them; see PRIVACY.md).

The plugin counts its own use anonymously through the altimate-code CLI's usage telemetry (`altimate-code tool report-event`; no network connection of the plugin's own): `plugin_session_start` at each session start, with the plugin and altimate-code versions, the OS and a random install id kept in the plugin's Claude Code store; and `plugin_feature_used` when `/lineage`, `/dbt-show`, `/profile-ctes`, `/scan-cost`, `/comments`, `/sql-graph`, `/health`, `/runs` or `/to-model` opens, or the cost check or the health push gate holds or allows a command, with the feature's name and the outcome. No session id, project, model, column or file names, SQL or session text, and none of the identifiers altimate-code's other telemetry carries (account, machine id). Set `ALTIMATE_TELEMETRY_DISABLED=true` to turn it off (with altimate-code's other telemetry). An altimate-code that predates these events drops them silently. Every event and field is listed in [PRIVACY.md](../../PRIVACY.md#plugin-usage-events).

Delegating a task with `altimate run` passes your prompt text to the altimate-code CLI, which sends it to your configured LLM provider — the Altimate LLM Gateway by default, or your own provider (BYOK), in which case Altimate never sees it. Warehouse credentials and query results stay on your machine.

Full details: **[PRIVACY.md](../../PRIVACY.md)** · Security policy and disclosure: **[SECURITY.md](../../SECURITY.md)** · Terms: **[TERMS.md](../../TERMS.md)**
Expand Down
3 changes: 2 additions & 1 deletion plugins/altimate-code/hooks/dbt-mods.tsx
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,7 @@ import type { Args, EngineInterface, EventResult, On, PluginOptions, RenderEleme

import type { CheckView, DoctorCheck, DoctorView, FailureView, QueryResult, SavedQuery } from '../types'
import { later } from './altimate-cli'
import { openTracked } from './usage'
import { loadPaneSizesOnce, noteTerminal, paneTerminalColumns, paneRequest, sizeControls, type PaneSpec } from './pane-size'
import {
cellText,
Expand Down Expand Up @@ -1776,7 +1777,7 @@ export function registerDbtMods(on: On, context: { options: PluginOptions }) {
// A /clear while the project or the size was being read ended the conversation that asked: open nothing in the new one.
if (asked !== generation) return { text: 'The conversation was cleared before the query started; run /dbt-show again.' }
try {
await $.ui.open({ id: RESULTS_PANE, title: RESULTS_TITLE, ...request, focus: true, closeOnEscape: true })
await openTracked($, 'dbt_show', () => $.ui.open({ id: RESULTS_PANE, title: RESULTS_TITLE, ...request, focus: true, closeOnEscape: true }))
} catch (error) {
return { text: `Could not open the Query results pane: ${String(error)}` }
}
Expand Down
10 changes: 8 additions & 2 deletions plugins/altimate-code/hooks/features/comments.tsx
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,7 @@ import type { Args, EngineInterface, EventResult, On, RenderElement, ToolCallRes

import type { CommentsState, CommentsThread } from '../../types'
import { later, runTool } from '../altimate-cli'
import { openTracked } from '../usage'
import type { BashCall, ContextLines, EditedFile, FileCall } from '../tool-chain'
import type { BandUi, FeatureContext } from './index'

Expand Down Expand Up @@ -98,7 +99,7 @@ export function register(on: On, context: FeatureContext) {

on('command.run', { command: COMMAND }, async $ => {
try {
await $.ui.open({ id: PANE, title: PANE_TITLE, focus: true, closeOnEscape: true })
await openCommentsPane($)
// Running the command again is how a missing tool is looked for again, after an update.
await change($, current => ({ ...current, needs: null, note: null }))
later($, () => open($))
Expand Down Expand Up @@ -246,7 +247,7 @@ export async function bandLine($: EngineInterface, ui: BandUi): Promise<RenderEl
💬 {current.threads.length} open team comment{current.threads.length === 1 ? '' : 's'}
{current.project ? ` on ${current.project}` : ''}{' '}
</Text>
<Button key="comments-open" label="Open" onPress={() => later($, () => $.ui.open({ id: PANE, title: PANE_TITLE, focus: true, closeOnEscape: true }))} />
<Button key="comments-open" label="Open" onPress={() => later($, () => openCommentsPane($))} />
</Box>
)
}
Expand Down Expand Up @@ -379,6 +380,11 @@ function startPoll($: EngineInterface) {
if (interactive && poll === null) poll = $.clock.every(pollSeconds * 1000, () => later($, () => load($)))
}

/** The pane a person opens (/comments, the band's Open), counted as a use of it. */
function openCommentsPane($: EngineInterface) {
return openTracked($, 'comments', () => $.ui.open({ id: PANE, title: PANE_TITLE, focus: true, closeOnEscape: true }))
}

async function open($: EngineInterface) {
// The project being read stays the pane's project: only a session with none yet looks at its own folder.
if (!(await get($)).root) await attach($, await $.session.cwd())
Expand Down
Loading
Loading