Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
84 commits
Select commit Hold shift + click to select a range
57bdf7b
feat: `/savings` v2: status line, tool-row notes, saved since, checks…
shreyastelkar Nov 18, 2026
dab7f5f
fix: /savings v2 shows observed spend after a drafted fix, and a /cle…
shreyastelkar Nov 20, 2026
c82b279
feat: /savings opens slim: the three largest findings, the rest behin…
shreyastelkar Nov 20, 2026
9b1d50b
fix: the slim /savings pane keeps a drafted fix's line once, and ever…
shreyastelkar Nov 20, 2026
654a87b
docs: the slim /savings view leaves out the workspace; Show all names it
shreyastelkar Nov 20, 2026
717c00a
fix: the slim /savings pane adds up: three resources shown, plus what…
shreyastelkar Nov 20, 2026
34432ef
fix: the slim /savings line says "more findings": a hidden finding ca…
shreyastelkar Nov 20, 2026
8b61075
Merge feat/savings-via-altimate-code into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
8c1db80
Merge feat/savings-via-altimate-code into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
a36e8b9
Merge feat/savings-via-altimate-code into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
9397a7d
Merge feat/savings-via-altimate-code into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
dea2d1d
fix: /savings keeps source builds out at session start, saves every a…
shreyastelkar Nov 20, 2026
ddca0dd
Merge feat/savings-via-altimate-code into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
36e7059
Merge feat/savings-via-altimate-code into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
653143b
Merge feat/savings-via-altimate-code into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
5debeb7
Merge feat/savings-via-altimate-code into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
6543a25
fix: a /savings total missing a figure is the findings' own
shreyastelkar Nov 20, 2026
9f82f86
Merge feat/savings-via-altimate-code into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
ea7a756
Merge feat/savings-via-altimate-code into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
f2b8b68
Merge feat/savings-via-altimate-code into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
1e02d97
Merge feat/savings-via-altimate-code into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
76f23c3
Merge feat/savings-via-altimate-code into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
39670de
Merge feat/savings-via-altimate-code into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
0046f58
Merge feat/savings-via-altimate-code into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
554805d
Merge feat/savings-via-altimate-code into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
1eacbe8
Merge feat/savings-via-altimate-code into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
118944b
Merge feat/savings-via-altimate-code into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
9da24ba
Merge feat/savings-via-altimate-code into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
8a34079
fix: a pressed /savings run beaten by a /clear never leaves the check…
shreyastelkar Nov 20, 2026
85f970a
Merge feat/savings-via-altimate-code into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
915f764
Merge feat/savings-via-altimate-code into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
64abe4d
fix: every step of a multi-platform /savings run checks it is still c…
shreyastelkar Nov 20, 2026
069d7fb
Merge feat/savings-via-altimate-code into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
edcf4f5
fix: the running flag is written only while its run is current, check…
shreyastelkar Nov 20, 2026
920ac70
Merge feat/savings-via-altimate-code into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
ae62f69
fix: a /clear during the running write or the pane open leaves no pan…
shreyastelkar Nov 20, 2026
4297b94
Merge feat/savings-via-altimate-code into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
8707655
Merge feat/savings-via-altimate-code into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
9c52b4c
fix: Underutilized Cluster reads the fields core sends, and the repor…
shreyastelkar Nov 20, 2026
89992db
Merge feat/savings-via-altimate-code into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
6302f7b
fix: a report the pane cannot write says why on one line
shreyastelkar Nov 20, 2026
a638883
Merge feat/savings-via-altimate-code into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
e1cbc86
test: the band does not pin a Snowflake name flagged in two accounts …
shreyastelkar Nov 20, 2026
df3f439
fix: a drafted fix is followed on its own workspace's warehouse when …
shreyastelkar Nov 20, 2026
f9e49a5
Merge feat/savings-via-altimate-code into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
f65834c
fix: a row from a differently named workspace never stands for a fix'…
shreyastelkar Nov 20, 2026
3be889f
fix: a drafted fix reads an unread size as unread, not as "?" or a re…
shreyastelkar Nov 20, 2026
c8adbef
fix: a fix's kept config names what was not read, and a draft or base…
shreyastelkar Nov 20, 2026
943e408
Merge feat/savings-via-altimate-code into feat/savings-mod-v2; rebuil…
shreyastelkar Nov 20, 2026
9089ae7
Merge feat/savings-via-altimate-code into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
7488651
fix: a fix's finding and its change line match by workspace the same …
shreyastelkar Nov 20, 2026
569c81a
Merge feat/savings-via-altimate-code into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
cd78265
test: one id in two workspaces drives a drafted fix, a what-if press …
shreyastelkar Nov 20, 2026
686d1f1
test: the two-workspace test checks the pressed finding exists and pr…
shreyastelkar Nov 20, 2026
b410fa2
fix: a change a drafted fix saw is not forgotten by a run that did no…
shreyastelkar Nov 20, 2026
61cd120
Merge branch 'feat/savings-via-altimate-code' into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
30bbf3f
Merge branch 'feat/savings-via-altimate-code' into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
646fda7
Merge branch 'feat/savings-via-altimate-code' into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
5900bc8
Merge branch 'feat/savings-via-altimate-code' into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
d588b74
Merge branch 'feat/savings-via-altimate-code' into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
e13b5bb
Merge branch 'feat/savings-via-altimate-code' into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
0ba3d3f
fix: show the copy a drafted fix belongs to; pin both Draft the fix g…
shreyastelkar Nov 20, 2026
3d1ecfe
Merge branch 'feat/savings-via-altimate-code' into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
cb0710e
Merge branch 'feat/savings-via-altimate-code' into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
63ff74c
fix: a drafted fix's line stays under the finding when the other conn…
shreyastelkar Nov 20, 2026
c7970da
Merge branch 'feat/savings-via-altimate-code' into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
e6f4b70
Merge branch 'feat/savings-via-altimate-code' into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
c6ce094
Merge branch 'feat/savings-via-altimate-code' into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
e2cb8f7
Merge branch 'feat/savings-via-altimate-code' into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
edd1a2f
Merge branch 'feat/savings-via-altimate-code' into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
5543e19
Merge branch 'feat/savings-via-altimate-code' into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
fc24fed
test: the run-start tests read this pane's wording, which names no pl…
shreyastelkar Nov 20, 2026
5d1cfc4
Merge branch 'feat/savings-via-altimate-code' into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
eb0170a
Merge branch 'feat/savings-via-altimate-code' into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
c58b99f
Merge branch 'feat/savings-via-altimate-code' into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
ba4c7dd
fix: a refusal before the connection list is read names no platform; …
shreyastelkar Nov 20, 2026
17bcd85
Merge branch 'feat/savings-via-altimate-code' into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
9947ce8
fix: a name the connection list lacks runs no check; "already running…
shreyastelkar Nov 20, 2026
3dde547
Merge branch 'feat/savings-via-altimate-code' into feat/savings-mod-v2
shreyastelkar Nov 20, 2026
54f37f5
fix: only this run's own connection list refuses a name; a listed con…
shreyastelkar Nov 20, 2026
25bf9f8
Merge branch 'feat/savings-via-altimate-code' into feat/savings-mod-v2
shreyastelkar Nov 21, 2026
2b3a9ee
fix: refusals are filed under a platform only when the run covered on…
shreyastelkar Nov 21, 2026
ac60767
fix: a refusal names a platform only when the connection asked for is…
shreyastelkar Nov 21, 2026
c0bb47f
test: a failure for a name the session-start list lacks names no plat…
shreyastelkar Nov 21, 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
12 changes: 8 additions & 4 deletions PRIVACY.md
Original file line number Diff line number Diff line change
Expand Up @@ -122,7 +122,7 @@ To count installs, active use and which features are used, the plugin asks the l
- 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.
- 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.
- **`/savings` sends no usage event.** Typing it, pressing its buttons and opening its pane are not counted, and nothing about the check (its queries, findings or amounts) goes to Altimate. See [The Databricks savings check](#the-databricks-savings-check).
- **`/savings` sends no usage event.** Typing it, pressing its buttons and opening its pane are not counted, and nothing about the check (its queries, findings or amounts) goes to Altimate. See [The savings check](#the-savings-check).

## Data flows when a task is delegated

Expand All @@ -135,9 +135,11 @@ To count installs, active use and which features are used, the plugin asks the l

**Bring Your Own Key (BYOK):** if you configure your own provider (Anthropic, OpenAI, Bedrock, Azure OpenAI, Ollama, and others), your prompts go directly from your machine to that provider. Altimate is not in that delegation path; workspace service requests still go to Altimate.

## The Databricks savings check
## The savings check

`/savings` runs altimate-code's `finops_databricks_savings` tool on your machine, with your own Databricks connection. It reads usage from your workspace's system tables and decides the savings locally. The plugin runs it with telemetry turned off, in altimate-code's assessment mode (`ALTIMATE_ASSESSMENT_MODE=true`) and outside its tool daemon. In assessment mode the CLI sends no usage event, not even the one-time telemetry opt-out event, and does not fetch the model catalog or download ripgrep, so your warehouse is the only host the run contacts; an altimate-code release without assessment mode ignores the setting and would still send that opt-out event and make those fetches, so the plugin first asks `altimate --version` (which sends nothing) and does not start a release older than 0.12.12, or a source build (which prints `local` whatever its age), for the check. The plugin sends no usage event of its own for `/savings` either (see [Plugin usage events](#plugin-usage-events)), so nothing about the check, its queries or its results goes to Altimate. The findings are shown in a pane, not added to the conversation. Not assessed: Databricks Apps spend; a serverless SQL warehouse gets only the over-sized check. The run starts the connection's SQL warehouse if it is stopped, and needs the `@databricks/sql` driver installed. Costs cover the six full billed days before the window's last day, scaled to seven, which read about 7% below the seven billed days on one measured workspace. To show a flagged warehouse's observed spend before and after a later change, the plugin keeps its size, type and weekly cost in Claude Code's local plugin store on your machine. **Draft the fix** puts one finding's details in your prompt box; they reach your model provider only if you send that prompt. When Claude runs the same tool itself, its answer is a tool result like any other and reaches your model provider.
For a Databricks connection, `/savings` runs altimate-code's `finops_databricks_savings` tool on your machine, with your own connection (Snowflake: see below). It reads usage from your workspace's system tables and decides the savings locally. The plugin runs it with telemetry turned off, in altimate-code's assessment mode (`ALTIMATE_ASSESSMENT_MODE=true`) and outside its tool daemon. In assessment mode the CLI sends no usage event, not even the one-time telemetry opt-out event, and does not fetch the model catalog or download ripgrep, so your warehouse is the only host the run contacts; an altimate-code release without assessment mode ignores the setting and would still send that opt-out event and make those fetches, so the plugin first asks `altimate --version` (which sends nothing) and does not start a release older than 0.12.12, or a source build (which prints `local` whatever its age), for the check. The plugin sends no usage event of its own for `/savings` either (see [Plugin usage events](#plugin-usage-events)), so nothing about the check, its queries or its results goes to Altimate. The findings are shown in a pane, not added to the conversation. Not assessed: Databricks Apps spend; a serverless SQL warehouse gets only the over-sized check. The run starts the connection's SQL warehouse if it is stopped, and needs the `@databricks/sql` driver installed. Costs cover the six full billed days before the window's last day, scaled to seven, which read about 7% below the seven billed days on one measured workspace. To show a flagged warehouse's observed spend before and after a later change, the plugin keeps its size, type and weekly cost in Claude Code's local plugin store on your machine. **Draft the fix** puts one finding's details in your prompt box; they reach your model provider only if you send that prompt. When Claude runs the same tool itself, its answer is a tool result like any other and reaches your model provider.

Snowflake connections are checked the same way, with altimate-code's `finops_snowflake_savings` tool. The last answer per connection is kept in that same local plugin store for 7 days (removed at the next session start after that), so the status line, the pane and a one-line note under a tool call on a flagged warehouse can show it without querying anything; **Draft the fix** also keeps the resource, its daily cost and the date there for 90 days, so a later run can say what the change did. At session start the plugin runs altimate-code's `warehouse_list` under the same switches to learn which connections exist; it reaches no warehouse. To tell which warehouse a connection runs on, the plugin reads `~/.altimate-code/connections.json` and the project's `.altimate-code/connections.json`, and for a `dbt run` or `dbt build` the dbt project and `profiles.yml`; those files hold credentials, and only `http_path`, the workspace host, `warehouse`, the Snowflake `account` and the target's type are taken from them. The host or account is kept with the answer in the local plugin store, so that an answer is shown only where the same workspace or account is connected; nothing else from those files is kept. **Share report** writes a local HTML page and opens it; nothing is uploaded. The Altimate button opens the sign-up page with nothing from your run in its address.

## Usage telemetry

Expand Down Expand Up @@ -178,7 +180,9 @@ 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 [The Databricks savings check](#the-databricks-savings-check) (plugin 1.9.0): `/savings` runs altimate-code's savings tool with telemetry off, sends no plugin usage event, and keeps the findings out of the conversation.
**November 19, 2026:** [The savings check](#the-savings-check) now covers Snowflake, the 7-day local copy of the last answer, which local files are read to match a tool call to its warehouse, and the local report page.

**November 19, 2026:** added [The savings check](#the-savings-check) (plugin 1.9.0): `/savings` runs altimate-code's savings tool with telemetry off, sends no plugin usage event, and keeps the findings out of the conversation.

**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.

Expand Down
7 changes: 7 additions & 0 deletions plugins/altimate-code/CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,13 @@ All notable changes to this plugin will be documented in this file.
- A line above the prompt when the session edits Databricks bundle or Terraform files or runs a `databricks` compute command: the flagged resource's saving, or a once-a-session offer of `/savings`.
- One connection checks every workspace the account's system tables show; the pane counts every workspace the CLI read (`workspaces_checked`), one with only clusters or jobs and no finding included, and names each finding's workspace. With a CLI that does not report the count, it counts the workspaces of the warehouses and findings.
- `/savings` asks `altimate --version` first and does not start an altimate-code older than 0.12.12, or a source build, for the check: before assessment mode, its `tool run` would send the one-time telemetry opt-out event.
- A status-line entry: the platforms your altimate-code connections cover plus `/savings`, then the monthly range of the kept answer. The answer is kept on this machine for 7 days, and nothing runs the check but `/savings` or a button you press.
- One line under a tool call that runs on a warehouse with a kept finding: altimate-code's SQL tools by connection, `dbt run` and `dbt build` by their target.
- After a drafted fix: Draft the fix keeps the resource, its daily cost and the date; later runs say it is unchanged, `measuring (n of 7 days)`, or its observed spend a day before and after, from billing (different weeks, so never called saved).
- The pane names the hosted product's checks that did not run, with counts from your own run and one button to Altimate; Share report writes a self-contained local HTML page.
- Snowflake: with both kinds of connection, `/savings` runs `finops_snowflake_savings` too and the pane has a section for each.
- The pane opens slim on every run: the total (each resource counted once, at its largest saving), the three resources with the largest saving across both platforms with one fact each, a line for the other findings (how many, and what the resources not shown add to the total, so the lines add up to the total) and the count of checks Altimate runs beyond these. Show all opens the full detail (every finding and its evidence, what-ifs, checks not run, Run again); Share report keeps the full detail.
- A finished check raises no notice while Claude is working; it comes when the turn ends.
- `runTool` takes an environment and `noDaemon` for one CLI run, and hands back a CLI's raw output when it is not an answer (an altimate-code too old for the tool gets "update").

### Fixed
Expand Down
Loading
Loading