Skip to content

feat: anonymous install, version and per-feature usage events (1.8.2) - #40

Merged
hkaltai merged 8 commits into
mainfrom
feat/usage-tracking
Nov 19, 2026
Merged

hkaltai merged 8 commits into
mainfrom
feat/usage-tracking

Conversation

@hkaltai

@hkaltai hkaltai commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

What

Anonymous, opt-out usage events for the plugin, so launch posts can be measured: distinct installs per day or week, plugin and altimate-code versions, OS, and how often each panel and gate is used. They go through the altimate-code CLI's existing telemetry (altimate tool report-event). The plugin opens no network connection of its own.

Depends on AltimateAI/altimate-code#1775, which adds the two actions to tool report-event with a field allow-list. Until that release is installed, the CLI refuses them and nothing is sent or shown.

Design

Events. Two new actions for altimate tool report-event, sent by the Claude Code plugin:

Event When Fields (the whole payload)
plugin_session_start each Claude Code session start plugin_version, altimate_code_version (stamped by the CLI), host_os (macos, linux, windows, wsl, unknown; apart from the os other events carry as process.platform), install_id
plugin_feature_used a person opened a panel or command, or a gate held or allowed a command plugin_version, install_id, feature, outcome
  • feature is one of lineage, dbt_show, profile_ctes, scan_cost, comments, sql_graph, health, runs, to_model, cost_gate, health_push_gate.
  • outcome is one of opened, failed (the panel could not open, or Claude Code could not place it), held, allowed.
  • install_id is a random UUID the plugin creates on first run and keeps in its own Claude Code plugin store. It is not derived from the machine, the user or the project.

Allow-list. The CLI builds each event from these fields only, each checked against a fixed pattern or enum: plugin_version is a SemVer 2.0 version of up to 64 characters (any number of digits per part) (or unknown), install_id a lowercase v4 UUID, and os, feature and outcome enums. The plugin actions take no --session, and each action refuses a flag it does not take. Anything else, including any other flag, is refused with exit 1 and nothing is tracked. No project names, SQL, paths, column names or session text can reach the event.

Transport and anonymity. The events go through the CLI's existing telemetry (Telemetry.track to Azure Application Insights, flushed on exit). No new network host. They are unlinkable: unlike every other CLI event, they carry no account (user_id, tenant), no machine id, no project id, no session id and no launch_id, which the same process's first_launch row would share. ai.user.id is the plugin's install id, so they cannot be joined to a signed-in row. Only cli_version, client and source come from the envelope.

Opt-out. ALTIMATE_TELEMETRY_DISABLED (or OPENCODE_DISABLE_TELEMETRY) and telemetry.disabled in the altimate-code config turn it off in the CLI, as for every other event. The plugin also checks ALTIMATE_TELEMETRY_DISABLED / OPENCODE_DISABLE_TELEMETRY itself and then starts no CLI process and creates no install id.

Older CLI. An altimate-code without these actions exits 1 with a message on stderr. The plugin runs every event in the background (scheduled with later, never awaited by a hook), ignores the exit code and output, and shows nothing: no toast, no log line outside the debug log.

Where each event comes from

  • hooks/usage.ts (new) has sessionStarted($), featureUsed($, feature, outcome), openTracked($, feature, open), usageOff($) and installId($).
    • Each event is scheduled with later and never awaited. The helpers never throw into the hook that calls them.
    • No session id is sent.
    • The plugin version is read from ${$.plugin.root}/.claude-plugin/plugin.json. It must be SemVer, as the CLI reads it, or it is sent as unknown.
    • The OS comes from $.session.info().platform.
    • The install id is kept under usage.installId in $.store. One lookup is in flight per plugin load, so events sent together on a first run share it. After writing, the stored value is read back, so sessions starting at the same moment converge on one id. A stored value that is not a v4 UUID is replaced.
  • integrations.tsx: sessionStarted($) in session.start.
  • Panels go through openTracked: opened once the pane opens, or failed when $.ui.open throws or answers isPlaced: false.
    • /lineage and the task summary's Open lineage button (lineage.tsx openPane).
    • /dbt-show (dbt-mods.tsx).
    • /comments and the band's Open button (features/comments.tsx).
    • /runs (a list that cannot be read counts as failed), /sql-graph, /profile-ctes and /to-model (its pane, once the mapping is in).
    • Panes the plugin opens on its own (the lineage pane following Claude, Query results after Claude's dbt show) are not counted: these count a person's use.
  • /health and /scan-cost answer in text, so they send opened when run.
  • features/cost.tsx: cost_gate held for every refusal of the gate. That covers over the limit, an estimate still coming in, and a project that could not be read. cost_gate allowed is sent when /allow-scan allows the held command, and nothing when nothing is held.
  • features/health.tsx: with "Project health blocks git push" on, health_push_gate held or allowed for each git push the gate decides. Nothing is sent with the gate off, or for a command that is not a push.
  • task-impact.tsx: the existing lineage_report events now check the same opt-out, so no CLI is started for them under it.
  • PRIVACY.md has a new "Plugin usage events" section listing every event and field. Its short version, the "What the plugin does" paragraph, the lineage report section and the change log are updated too. The plugin README's "Data handling" covers the events as well.
  • Version 1.8.2 in plugin.json and .claude-plugin/marketplace.json, with a CHANGELOG entry.

Verification

  • claude plugin test plugins/altimate-code: 1225 pass, 1 fail at the head (earlier runs of this branch: 0 fail). The one failure is features/runs.test.tsx › "a dbt call that starts while another call reads its artifact". That test waits on two 20 ms real-time sleeps and fails on main too: 2 of 6 runs of main's runs.test.tsx alone, and once in a full run of main's sources with this PR's tests. Every other test passes on each run; earlier full runs of this branch had 0 fail.
  • The new tests on main's sources: every test that expects an event fails, and so does the lineage opt-out test. The opt-out tests for the cost check and the push gate pass on main, since nothing is sent there.
  • Review fixes: each regression test failed on the head before its fix: every cost hold, the comments band's Open, Open lineage, /to-model counting only its pane, an unplaced pane counting as failed, one install id for events sent together, no session id, and version and UUID rules.
  • Tests by acceptance item:
    • One plugin_session_start per session start, with the plugin version, the OS and a v4 install id that matches the store, and no session id (usage.test.tsx).
      • A second session sends the same id. An id kept from before is reused. A path, a version 0 UUID or a number in the store is replaced.
      • Events sent while the first id is still being made share it.
      • The OS and version cases: wsl, 1.8.2+build.7, and 1.8.2-01 → unknown.
    • One plugin_feature_used per panel and command: /lineage, /dbt-show, /profile-ctes, /scan-cost, /comments, /sql-graph, /health, /runs and /to-model each send exactly one, with their feature name and opened.
      • A pane that throws, or that Claude Code could not place, sends failed. A bad argument before any pane sends nothing.
      • Open lineage (task-impact.test.tsx) and the comments band's Open each send one. The pane following Claude's edit sends none.
      • Cost gate (cost.test.tsx): held over the limit, held while the estimate is still coming in, /allow-scan allowed, /scan-cost opened, and nothing when nothing is held.
      • Push gate (health.test.tsx): a push held, /health opened, a push allowed, and nothing with the gate off.
    • Opt-out: ALTIMATE_TELEMETRY_DISABLED set to true, 1 or TRUE, or OPENCODE_DISABLE_TELEMETRY=1, starts no CLI for any event and makes no install id. The cost and health gates still hold under it and send nothing. The lineage report still opens and sends no lineage_report. false and 0 leave usage on, as the CLI reads them. The CLI's own opt-out is proven end to end in feat: tool report-event takes the Claude Code plugin's session start and feature-used events altimate-code#1775.
    • Payload allow-list: in a project at /work/acme_secret_project, with a model fct_orders, a column secret_column and SQL passed to /dbt-show, every event's argv has only the allowed flags, each value matching its pattern. None contains the project, model, column, SQL, path or session id. On the CLI side, the events are sent without account, machine id, project or session, and are keyed to the install id (#1775).
    • Older CLI: an altimate-code that exits 1 with "the action must be one of …" leaves the command's answer unchanged. There is no toast and nothing in the log outside debug. The same holds with no altimate on PATH and an altimate-code without report-event.
    • Fire-and-forget: a CLI that never answers holds neither the session start nor /runs.
  • claude plugin validate --strict . passes. The env reads it lists are ALTIMATE_TELEMETRY_DISABLED, OPENCODE_DISABLE_TELEMETRY and WSL_DISTRO_NAME.
  • bash tests/*.sh: all 8 pass.
  • End to end with the CLI from #1775 and its telemetry pointed at a local sink: see that PR. The sink receives both events with exactly the allow-listed fields, and nothing when the opt-out is set.

🤖 Generated with Claude Code

plugin_session_start at each session start (plugin and altimate-code versions,
OS, a random install id kept in the plugin store) and plugin_feature_used for
each panel, command and gate, sent in the background through altimate-code's
`tool report-event`. ALTIMATE_TELEMETRY_DISABLED starts no CLI for any usage
event and makes no install id; an older CLI's refusal is silent.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

/** The anonymous install id: made on first run and kept in this plugin's store, so it stays the same across sessions. */
export async function installId($: EngineInterface): Promise<string> {
const kept = await $.store.get(INSTALL_ID_KEY)

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

SUGGESTION: Concurrent first sends can create two different install ids

installId has no in-flight guard, so two send calls that start before the first write lands (the session-start event and the first feature/gate event, or two feature events) each read no stored id, each generate a UUID, and each write it. The event that already went out keeps the id that lost the write, so one machine can be counted as two installs on its first session — the exact metric this field feeds. Memoizing the promise (the same way ownVersion memoizes the version below) would make concurrent callers share one id and one write.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Fixed in e1bd950. installId keeps one lookup in flight per plugin load, so events sent together on a first run share the id the first one makes. After writing, it reads the stored value back and uses that, so two sessions starting at the same moment converge on the id the store kept. Regression test: "events sent together on a first run share one install id" holds the store read while /runs sends a second event. It fails on the previous head.

expect([...store.keys()].filter(key => key === 'usage.installId')).toHaveLength(1)
})

test('an install id kept from an earlier run is sent as it is; one that is not a UUID is replaced', async ($, on) => {

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

SUGGESTION: Test name promises coverage it does not provide

The title says "one that is not a UUID is replaced", but this test only asserts that a stored UUID is sent unchanged; the replacement half is the next test (line 143). A future regression in the replacement path would look covered by this name.

Suggested change
test('an install id kept from an earlier run is sent as it is; one that is not a UUID is replaced', async ($, on) => {
test('an install id kept from an earlier run is sent as it is', async ($, on) => {

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Fixed in 9d46b90: renamed to "an install id kept from an earlier run is sent as it is". The replacement cases are their own tests now: a path, a version 0 UUID, and a number.

@kilo-code-bot

kilo-code-bot Bot commented Nov 19, 2026 •

Copy link
Copy Markdown

Code Review Summary

Status: No Issues Found | Recommendation: Merge

This incremental pass covers 4da9c8d..238fb92. All three carried findings are now resolved on current code:

  • PRIVACY.md:117 now states that the host_os field is passed by the plugin as --os, so the published field list no longer silently disagrees with the argv the CLI receives.
  • plugins/altimate-code/hooks/features/runs.tsx:598 moves load(...) inside the openTracked callback, so an unreadable runs list both answers "Could not open the dbt runs" and sends runs failed; the new regression test at plugins/altimate-code/hooks/usage.test.tsx:396 pins it (it fails on the previous head).
  • plugins/altimate-code/hooks/usage.test.tsx:123 hoists the seven-row panel table to the PANELS constant, which both the openFails and isPlaced: false outcome tests now walk.

Deep checks on the new code: the store key the test throws on (runs) matches STORE_KEY in runs.tsx:20, so the test exercises the real held() read; the throw is a genuine store failure path, not a synthetic open failure. The remaining pre-open gap noted earlier for lineage (paneRequest, an in-memory atom read) and cte-profile (an update of an in-memory atom) only covers operations that do not perform I/O, unlike the fixed runs read, so no further finding is raised. No redundant or simplifiable code was found in the changed lines.

Files Reviewed (3 files)
  • PRIVACY.md - no issues; carried finding resolved
  • plugins/altimate-code/hooks/features/runs.tsx - no issues; carried finding fixed and covered by a new test
  • plugins/altimate-code/hooks/usage.test.tsx - no issues; duplication removed, new regression test verified against the fix
Previous Review Summaries (6 snapshots, latest commit 4da9c8d)

Current summary above is authoritative. Previous snapshots are kept for context only.

Previous review (commit 4da9c8d)

Status: 3 Issues Found | Recommendation: Address before merge

This incremental pass covers a8b96f7..4da9c8d, a single PRIVACY.md sentence that now names the envelope fields (cli_version, client, source). The sentence matches the PR body's description of the CLI-side envelope, and nothing in this repository contradicts it (the plugin sends no such flags itself; runAltimate passes only the argv), so no new finding arises. The three carried suggestions below were re-verified against current code and remain open; none is resolved by the new commit.

Overview

Severity Count
CRITICAL 0
WARNING 0
SUGGESTION 3
Issue Details (click to expand)

SUGGESTION

File Line Issue
PRIVACY.md 117 (carried) The row documents host_os, but sessionStarted sends --os (hooks/usage.ts:104) and the payload allow-list test only knows --os (hooks/usage.test.tsx:14). Nothing else in the repo mentions host_os, and the other cells track the flag names (plugin_version/--plugin-version, install_id/--install-id). Rename the flag everywhere or keep the cell as os, so the published field list matches what the CLI receives.
plugins/altimate-code/hooks/features/runs.tsx 598 (carried) openTracked only reports the open, but this try also wraps await load(...). A load failure answers "Could not open the dbt runs" while sending no event, where an open failure sends runs failed; PRIVACY.md says failed covers a panel that could not open. cte-profile (the update before openPane) and lineage (paneRequest before the tracked call) share the gap.
plugins/altimate-code/hooks/usage.test.tsx 359 (carried) The notPlaced test repeats the openFails test's seven-row [command, args, feature] table (lines 211-219) verbatim; a panel added to one list would get only one outcome covered. Hoist the table to a module constant and reuse it in both tests.
Files Reviewed (3 files)
  • PRIVACY.md - no new issues; 1 carried (line 117), new line 121 check passed
  • plugins/altimate-code/hooks/features/runs.tsx - 1 carried (targeted re-check)
  • plugins/altimate-code/hooks/usage.test.tsx - 1 carried (targeted re-check)

Fix these issues in Kilo Cloud

Previous review (commit a8b96f7)

Status: 3 Issues Found | Recommendation: Address before merge

This incremental pass covers 1c6af5b..a8b96f7, which only rewrites one PRIVACY.md sentence (the events no longer claim a per-launch id). That line is consistent with the plugin's argv (no launch id is sent) and with the PR body, so no new finding arises from it. The three carried suggestions below were re-verified against current code and remain open; none is resolved by the new commit.

Overview

Severity Count
CRITICAL 0
WARNING 0
SUGGESTION 3
Issue Details (click to expand)

SUGGESTION

File Line Issue
PRIVACY.md 117 (carried) The row documents host_os, but sessionStarted sends --os (hooks/usage.ts:104) and the payload allow-list test only knows --os (hooks/usage.test.tsx:14). Nothing else in the repo mentions host_os, and the other cells track the flag names (plugin_version/--plugin-version, install_id/--install-id). Rename the flag everywhere or keep the cell as os, so the published field list matches what the CLI receives.
plugins/altimate-code/hooks/features/runs.tsx 598 (carried) openTracked only reports the open, but this try also wraps await load(...). A load failure answers "Could not open the dbt runs" while sending no event, where an open failure sends runs failed; PRIVACY.md says failed covers a panel that could not open. cte-profile (the update before openPane) and lineage (paneRequest before the tracked call) share the gap.
plugins/altimate-code/hooks/usage.test.tsx 359 (carried) The notPlaced test repeats the openFails test's seven-row [command, args, feature] table (lines 211-219) verbatim; a panel added to one list would get only one outcome covered. Hoist the table to a module constant and reuse it in both tests.
Files Reviewed (3 files)
  • PRIVACY.md - no new issues; 1 carried (line 117), new line 121 check passed
  • plugins/altimate-code/hooks/features/runs.tsx - 1 carried (targeted re-check)
  • plugins/altimate-code/hooks/usage.test.tsx - 1 carried (targeted re-check)

Fix these issues in Kilo Cloud

Previous review (commit 1c6af5b)

Status: 3 Issues Found | Recommendation: Address before merge

The two earlier test-quality findings are resolved: the fixture now counts writes of usage.installId and the "share one install id" test expects exactly one, which fails with idInFlight removed (each held caller's read is snapshotted before the first write lands), and a new test presses the comments band's Open with openFails and gets one comments failed. The SemVer digit cap removal is safe: isVersion checks length <= 64 before running the regex, so the unbounded numeric component stays bounded. Remaining are one new documentation mismatch and two carried suggestions.

Overview

Severity Count
CRITICAL 0
WARNING 0
SUGGESTION 3
Issue Details (click to expand)

SUGGESTION

File Line Issue
PRIVACY.md 117 (new) The row now documents host_os, but sessionStarted sends --os (hooks/usage.ts:104) and the payload allow-list test only knows --os (hooks/usage.test.tsx:14). Nothing else in the repo mentions host_os, and the other cells track the flag names (plugin_version/--plugin-version, install_id/--install-id). Rename the flag everywhere or keep the cell as os, so the published field list matches what the CLI receives.
plugins/altimate-code/hooks/features/runs.tsx 598 (carried) openTracked only reports the open, but this try also wraps await load(...). A load failure answers "Could not open the dbt runs" while sending no event, where an open failure sends runs failed; PRIVACY.md says failed covers a panel that could not open. cte-profile (the update before openPane) and lineage (paneRequest before the tracked call) share the gap.
plugins/altimate-code/hooks/usage.test.tsx 359 (carried) The notPlaced test repeats the openFails test's seven-row [command, args, feature] table (lines 211-219) verbatim; a panel added to one list would get only one outcome covered. Hoist the table to a module constant and reuse it in both tests.
Files Reviewed (5 files)
  • PRIVACY.md - 1 issue
  • plugins/altimate-code/hooks/usage.ts - no issues
  • plugins/altimate-code/hooks/usage.test.tsx - 1 issue
  • plugins/altimate-code/hooks/features/runs.tsx - 1 issue (carried, re-verified)
  • plugins/altimate-code/hooks/features/comments.tsx - no issues (targeted check of the band's Open path)

Fix these issues in Kilo Cloud

Previous review (commit bb32c12)

Status: 3 Issues Found | Recommendation: Address before merge

The openTracked consolidation holds up: each person-opened pane reports through one helper, the lineage pane that follows Claude and the Query results pane re-opened by runShow stay uncounted, isPlaced: false is counted as failed, and the new tests cover both the openFails and notPlaced paths. The comments band's former failed branch is now shared and exercised through the /comments case, so that earlier finding is resolved. Remaining are one carried test-quality finding and two new suggestions.

Overview

Severity Count
CRITICAL 0
WARNING 0
SUGGESTION 3
Issue Details (click to expand)

SUGGESTION

File Line Issue
plugins/altimate-code/hooks/usage.test.tsx 324 (carried) The "share one install id" test still passes with idInFlight deleted: now that readOrMakeId writes and then reads back, both callers converge on the last write, so it proves the read-back, not the memoization. Count store.set calls for usage.installId (or assert only one store.get) to pin the guard.
plugins/altimate-code/hooks/features/runs.tsx 598 openTracked only reports the open, but this try also wraps await load(...). A load failure answers "Could not open the dbt runs" while sending no event, where the previous head sent runs failed; PRIVACY.md says failed covers a panel that could not open. cte-profile (the update before openPane) and lineage (paneRequest before the tracked call) share the gap.
plugins/altimate-code/hooks/usage.test.tsx 354 The new notPlaced test repeats the openFails test's seven-row panel table verbatim; a panel added to one list would get only one outcome covered. Hoist the table to a module constant and reuse it in both tests.
Files Reviewed (13 files)
  • PRIVACY.md - no issues
  • plugins/altimate-code/CHANGELOG.md - no issues
  • plugins/altimate-code/README.md - no issues
  • plugins/altimate-code/hooks/dbt-mods.tsx - no issues
  • plugins/altimate-code/hooks/features/comments.tsx - no issues
  • plugins/altimate-code/hooks/features/cte-profile.tsx - no issues
  • plugins/altimate-code/hooks/features/runs.tsx - 1 issue
  • plugins/altimate-code/hooks/features/sql-graph.tsx - no issues
  • plugins/altimate-code/hooks/features/to-model.tsx - no issues
  • plugins/altimate-code/hooks/lineage.tsx - no issues
  • plugins/altimate-code/hooks/task-impact.test.tsx - no issues
  • plugins/altimate-code/hooks/usage.test.tsx - 2 issues
  • plugins/altimate-code/hooks/usage.ts - no issues

Fix these issues in Kilo Cloud

Previous review (commit 9d46b90)

Status: 2 Issues Found | Recommendation: Address before merge

The two findings from the previous review are fixed: installId now shares one lookup in flight (usage.ts:54-72) and the install-id test was renamed with its replacement cases split out. The items below are new, both test quality.

Overview

Severity Count
CRITICAL 0
WARNING 0
SUGGESTION 2
Issue Details (click to expand)

SUGGESTION

File Line Issue
plugins/altimate-code/hooks/usage.test.tsx 321 The new "share one install id" test passes with the in-flight guard removed: now that readOrMakeId writes then reads back, both callers converge on the last write, so the test proves the read-back rather than the memoization it is named for. Count store writes to pin the guard.
plugins/altimate-code/hooks/usage.test.tsx 343 The band test only covers the opened branch, so the new failed branch in comments.tsx (send event, then rethrow) is never exercised. The fixture's openFails option can cover it.
Files Reviewed (7 files)
  • PRIVACY.md - no issues
  • plugins/altimate-code/hooks/features/comments.tsx - no issues
  • plugins/altimate-code/hooks/features/cost.test.tsx - no issues
  • plugins/altimate-code/hooks/features/cost.tsx - no issues
  • plugins/altimate-code/hooks/features/to-model.tsx - no issues
  • plugins/altimate-code/hooks/usage.test.tsx - 2 issues
  • plugins/altimate-code/hooks/usage.ts - no issues

Fix these issues in Kilo Cloud

Previous review (commit 8cc0051)

Status: 2 Issues Found | Recommendation: Address before merge

No critical or warning-level defects found: the event payloads match the documented allow-list, the opt-out is checked before any CLI process or install id, every event is scheduled through later so no hook waits on it, and the gate events fire only on the paths that actually decide a command.

Overview

Severity Count
CRITICAL 0
WARNING 0
SUGGESTION 2
Issue Details (click to expand)

SUGGESTION

File Line Issue
plugins/altimate-code/hooks/usage.ts 51 installId has no in-flight guard, so two send calls that overlap before the first store write can each mint and store a different UUID; the session-start event would then disagree with later events and one machine can look like two installs on its first session. Memoize the promise (as pluginVersion does).
plugins/altimate-code/hooks/usage.test.tsx 137 Test name says "one that is not a UUID is replaced" but only asserts the kept-id case; replacement is covered by the next test, so the name overstates coverage.
Files Reviewed (21 files)
  • .claude-plugin/marketplace.json - no issues
  • PRIVACY.md - no issues
  • plugins/altimate-code/.claude-plugin/plugin.json - no issues
  • plugins/altimate-code/CHANGELOG.md - no issues
  • plugins/altimate-code/README.md - no issues
  • plugins/altimate-code/hooks/dbt-mods.tsx - no issues
  • plugins/altimate-code/hooks/features/comments.tsx - no issues
  • plugins/altimate-code/hooks/features/cost.test.tsx - no issues
  • plugins/altimate-code/hooks/features/cost.tsx - no issues
  • plugins/altimate-code/hooks/features/cte-profile.tsx - no issues
  • plugins/altimate-code/hooks/features/health.tsx - no issues
  • plugins/altimate-code/hooks/features/runs.tsx - no issues
  • plugins/altimate-code/hooks/features/sql-graph.tsx - no issues
  • plugins/altimate-code/hooks/features/to-model.tsx - no issues
  • plugins/altimate-code/hooks/health.test.tsx - no issues
  • plugins/altimate-code/hooks/integrations.tsx - no issues
  • plugins/altimate-code/hooks/lineage.tsx - no issues
  • plugins/altimate-code/hooks/task-impact.test.tsx - no issues
  • plugins/altimate-code/hooks/task-impact.tsx - no issues
  • plugins/altimate-code/hooks/usage.test.tsx - 1 issue
  • plugins/altimate-code/hooks/usage.ts - 1 issue

Fix these issues in Kilo Cloud


Reviewed by deepseek-v4.1-flash-1017 · Input: 0 · Output: 0 · Cached: 0

hkaltai and others added 2 commits November 19, 2026 17:01
…re counted once; one install id per first run

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…4 UUID)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
await clock.settle()
const ids = usage().map(argv => flag(argv, '--install-id'))
expect(usage().map(argv => argv[3])).toEqual(['plugin_session_start', 'plugin_feature_used'])
expect(new Set(ids).size).toBe(1)

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

SUGGESTION: This test cannot fail if the in-flight guard is removed

With readOrMakeId now writing the id and then reading it back, both callers converge on the last write even without idInFlight: the held store.get releases both callers, both store.set calls land before either read-back, and both send the same id. So the assertion holds if the memoization at usage.ts:56 is deleted — it proves the read-back, not that the second event waited. Counting writes would pin the guard, e.g. wrap store.set in the fixture and expect exactly one write for usage.installId, or assert the second store.get never runs.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Fixed in 1c6af5b. The fixture counts writes of usage.installId, and the test expects exactly one. With the in-flight guard removed, the test fails (two writes), checked by removing the memo from a copy of usage.ts.

surface: 'terminal',
} as any)
const before = usage().length
await band.press({ key: 'comments-open' })

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

SUGGESTION: The band's new failed branch is untested

This test only presses Open with $.ui.open resolving, so the rejection handler added in comments.tsx (send comments failed, then rethrow) never runs; deleting that branch would keep the suite green. The fixture already supports openFails: true, so a second case pressing the button under it would cover the failed event and confirm the rethrow still reaches later's debug log.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Fixed in 1c6af5b. A new test presses the band's Open with $.ui.open failing and expects one comments failed. Since bb32c12 the button goes through openCommentsPane → openTracked, the same path as /comments.

…d count; an unplaced pane is failed

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
try {
await load($, await $.session.root())
await $.ui.open({ id: PANE, title: PANE_TITLE, ...PANE_SIZE, focus: true, closeOnEscape: true })
await openTracked($, 'runs', () => $.ui.open({ id: PANE, title: PANE_TITLE, ...PANE_SIZE, focus: true, closeOnEscape: true }))

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

SUGGESTION: A failure before the open is now counted as nothing

openTracked only reports on the open itself, but this try also wraps await load(...). If load throws, the command still answers Could not open the dbt runs (the catch below), yet no plugin_feature_used is sent: the previous head sent runs failed from that catch. PRIVACY.md describes failed as covering a panel that "could not open", so this failure is now invisible. cte-profile (an update before openPane) and lineage (paneRequest inside openPane, before the tracked call) have the same gap; either send failed from those catches or narrow the docs.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Fixed in 238fb92. /runs now reads its list inside openTracked, so a list that cannot be read sends runs failed, as the previous head did. Regression test: "/runs whose list cannot be read answers that it could not open, and sends runs failed". It fails on the previous head.


test('a pane Claude Code could not place (isPlaced: false) is counted as failed, not opened', async ($, on) => {
const { clock, usage, flag } = await start($, on, { notPlaced: true })
for (const [command, args, feature] of [

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

SUGGESTION: The panel table is duplicated from the openFails test

These seven [command, args, feature] rows repeat the openFails test's table verbatim. A panel added to one list and not the other would get only one of opened/failed covered. Hoisting the table to a module constant and reusing it in both tests keeps the two outcome paths in step.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Fixed in 238fb92: the panel table is one module constant, PANELS, which the openFails and isPlaced: false tests both walk.

…d's failed open; any SemVer number

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Comment thread PRIVACY.md Outdated

| 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`: `macos`, `linux`, `windows`, `wsl` or `unknown`; `install_id` |

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

SUGGESTION: The documented field host_os is not the one the plugin sends

This row now names the field host_os, but sessionStarted sends --os (plugins/altimate-code/hooks/usage.ts:104) and the payload allow-list test only knows --os (plugins/altimate-code/hooks/usage.test.tsx:14). Nothing else in the repository mentions host_os, and the field names in this column track the flag names (plugin_version/--plugin-version, install_id/--install-id, feature/--feature). Either the flag and the allow-list need the same rename, or this cell should stay os; as written, the published field list disagrees with what the CLI receives.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Fixed in 238fb92. The column lists the event fields as the CLI sends them, and the CLI names this one host_os so it stays apart from the os its other events carry as process.platform (#1775). The row now says the plugin passes it as --os.

hkaltai and others added 3 commits November 19, 2026 17:26
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…e for both outcome tests

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@hkaltai

hkaltai commented Nov 19, 2026

Copy link
Copy Markdown
Contributor Author

review-loop: APPROVED at 238fb92 (reviewers: gpt-6-astra high, gpt-6.1-sol high)

@sahrizvi sahrizvi left a comment

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.

Consensus review: APPROVE. Panel: Claude (lead) and Codex (codex exec -s read-only, default model). Both Codex runs finished: the independent pass and the cross-check. Head 238fb92; merge base fc3e5d4 (current main).

No critical or major finding. What I checked:

  • every event fires once per person action, with the right outcome;
  • no hook waits on an event: a CLI that never answers, is missing, exits 1 or prints 10 MB changes nothing;
  • the argv carries only the allowed flags, even under a secret-looking project path and with SQL, a model and a column given to /dbt-show;
  • under the env opt-out no CLI starts and no install id is written;
  • end to end, the altimate-code #1775 build sends both events to a local sink with exactly the allowed fields, and the npm 0.12.11 CLI exits 1 silently.

The 5 remaining minors are inline. Why none of them blocks:

  1. usage.ts:68, two plugin loads can each make their own install id on a first run: an edge case (two sessions starting at the same moment on a first run).
  2. PRIVACY.md:19, "anonymous" and "cannot be joined" overclaim: wording, safe in a follow-up.
  3. PRIVACY.md:121, the field list misses the timestamp, ai.user.id and the OPENCODE_DISABLE_TELEMETRY alias: docs only.
  4. PRIVACY.md:120, the install id outlives claude plugin uninstall: docs only.
  5. PRIVACY.md:123, under the CLI's config-only opt-out the plugin still writes an id and starts the CLI each time: docs only, and nothing is sent.

Nits, tables and the merge-order note are in the PR comment that follows.

async function readOrMakeId($: EngineInterface): Promise<string> {
const kept = await $.store.get(INSTALL_ID_KEY)
if (typeof kept === 'string' && UUID.test(kept)) return kept
await $.store.set(INSTALL_ID_KEY, crypto.randomUUID().toLowerCase())

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): the read-back does not make two sessions that start together agree on one install id.

idInFlight only guards events inside one plugin load. Take two Claude Code sessions starting at the same moment on a first run, sharing one store:

  1. A and B both read nothing.
  2. A writes UUID-A, reads it back, and sends UUID-A.
  3. B writes UUID-B, reads it back, and sends UUID-B.

The store keeps UUID-B, so later sessions converge, but that first run counts two installs. Codex reproduced this with two separate imports of the helper. I reproduced it in the test kit by having "another session" write after this one's read-back: the ids went [ce1f…, 1111…]. The test at usage.test.tsx:322 covers only events inside one load.

Edge case: it needs two first-run sessions racing. A fix could be a write-if-absent, or re-reading once after a short delay. Or just say in the comment that the ids converge from the next session.

Comment thread PRIVACY.md
- 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.

Comment thread PRIVACY.md
| `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.
- 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.

Comment thread PRIVACY.md
| `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.

Comment thread PRIVACY.md
- **`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.
- 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.
- 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.

@sahrizvi

Copy link
Copy Markdown
Collaborator

Consensus review (Claude + Codex): nits, test tables and the merge-order note. The approval and its 5 inline minors are in the review above.

Nits

# Where Nit Edge case or real
N1 cost.tsx:227, health.tsx:716 held is sent once per refusal. When Claude retries the same held command 3 times, that's 3 cost_gate held events, then 1 allowed (test kit). So a held count is a count of refused attempts, not of commands held. This matches "every refusal"; it's only a note for whoever reads the numbers Real, interpretation only
N2 integrations.tsx:576 plugin_session_start fires on every session.start. That includes /clear and /resume (kit: start, then clear, then resume gives 3 events) and claude -p/SDK runs, and no field tells them apart Real, counting only
N3 health.tsx:630, cost.tsx:159, cte-profile.tsx:266 /health and /scan-cost send opened before they check anything, including when they answer that there is no project or no estimate. /profile-ctes run again while one is running sends a second opened Edge case
N4 docs.tsx:533, dbt-mods.tsx:1363, dbt-mods.tsx:1367, integrations.tsx:343 Some panes and commands send no plugin_feature_used: /docs and its Propagate button, /dbt-doctor and its Details button, the dbt check pane, /integrations. (/lineage-report is counted, through lineage_report command_run.) The documented list is accurate, so this is coverage only Real, coverage
N5 PR body; usage.test.tsx:147 The body says 1225 pass, 1 fail, and that validate --strict passes. I got 1226 pass, 0 fail at head. claude plugin validate --strict plugins/altimate-code fails at head and at base (ICON_MISSING, which predates this PR), and head adds one new warning: TS18048 'argv' is possibly 'undefined' at usage.test.tsx:147 Cosmetic, test-only
N6 runs.test.tsx "a dbt call that starts while another call reads its artifact" depends on timing. Run alone 3 times, it failed 1 of 3 at head and 2 of 3 at base Happens at base too

Event table: what each person action sends (test kit, with the head's hooks)

Feature Trigger Events sent Outcome Correct
session start session.start 1 plugin_session_start – yes (also /clear, /resume, -p: N2)
lineage /lineage, the summary's Open lineage 1 opened / failed yes; the follow-up open with open: true and the auto-opened pane send nothing
dbt_show /dbt-show (with a model, or with SQL) 1 per run opened / failed yes; the auto-reopen at dbt-mods.tsx:783 sends nothing
comments /comments, the band's Open 1 opened / failed yes
runs /runs 1 opened; failed when the open fails, the pane is unplaced or the list can't be read yes
sql_graph /sql-graph <model> 1; none without a model opened / failed yes
profile_ctes /profile-ctes <model> 1; another while one is running (N3) opened / failed yes
to_model /to-model once its pane opens 1; none for a bad argument opened / failed yes
health /health 1 always opened (N3) per the claim
scan_cost /scan-cost 1 always opened per the claim
cost_gate each refusal (over the limit, estimate pending, project unreadable) 1 per refusal (N1) held yes
cost_gate /allow-scan with a hold 1 allowed yes; nothing with nothing held
health_push_gate a git push decided, setting on 1 held / allowed yes; nothing with the setting off, or for a non-push

Hook timing: head vs base (test kit, wall ms; the event's CLI is faked)

Hook CLI behaviour Base Head
session start (with settle) answers / never / missing / exit 1 / 10 MB 198–205 224–275
/lineage, /dbt-show, /runs, /health, /scan-cost, /comments, /sql-graph any of the 5 0.3–8.9 each 0.4–4.3 each
cost gate, held ×3 off / never answers 4.8, 2.3, 2.1 4.7, 5.7, 3.2
cost gate, allowed run off / never answers 57.8 58.8
health push gate, held ×2 off / never answers 1.9, 1.2 2.2, 1.8

In the gate rows, "Base" means the same head code with the opt-out set, so the gate behaves as at base. The session-start gap comes from the kit running the event's own work during settle; the hook itself awaits nothing new. In every case: no toast, and no log line outside debug. Throws inside the helper (store.set, session.info, env.get) reach only the debug log ("scheduled work failed"), and the command answers as before.

Argv capture

Setup: project at /Users/pat/AWS_SECRET_ACCESS_KEY_prod/acme_secret_project. /dbt-show was given select secret_column, 'sk-live-123' from raw.orders where email = 'pat@example.com', and /lineage was given fct_orders.secret_column.

Every argv the plugin built has this shape:

altimate tool report-event plugin_session_start --plugin-version 1.8.2 --install-id <v4> --os linux
altimate tool report-event plugin_feature_used --plugin-version 1.8.2 --install-id <v4> --feature <name> --outcome opened
  • Flags used: --plugin-version, --install-id, --os, --feature, --outcome.
  • Grep for secret|acme|AWS|orders|select|pat@|sk-live|/Users|fct_ over all argv: no hits.
  • Versions: 1.8.2-rc.1 and 1.8.2+build.7 pass through; 1.8.2-01 and non-SemVer become unknown.
  • OS: Claude Code's own platform (it maps WSL_DISTRO_NAME/WSL_INTEROP to wsl).
  • Stored ids: an uppercase v4, a v1, a path, a number and free text are all replaced with a fresh v4.

End to end: #1775 build (a0e1395d21) and a local sink

  • Both events arrive. Every captured argv was run through the #1775 CLI with an isolated HOME, and each event arrived. Each carries only:
    • properties: cli_version, client, source, plugin_version, install_id, altimate_code_version + host_os (session start) or feature + outcome (feature used);
    • tags: ai.user.id (= install_id), an empty ai.session.id, ai.cloud.role, ai.application.ver.
  • No other identifier. No machine_id, user_id, tenant, project_id, launch_id or session id.
  • Old CLI. npm 0.12.11 exits 1 on every action and sends nothing.

Opt-out table

Setting CLI started by the plugin Install id written Sink
ALTIMATE_TELEMETRY_DISABLED = true / 1 / TRUE no no nothing
OPENCODE_DISABLE_TELEMETRY=1 no no nothing
ALTIMATE_TELEMETRY_DISABLED = false / 0 yes yes events
$.env.get throws no (treated as off) no nothing
config telemetry.disabled: true only yes, once per event yes no plugin event; the one-time telemetry_opted_out if a machine id exists (inline minor)
lineage_report under the env opt-out no – nothing

Test results (run one after another)

Check Head Base
claude plugin test plugins/altimate-code 1226 pass, 0 fail 1184 pass, 3 fail (load timing: "great many dbt calls", "a dbt call that starts…", "drawLayered 500-node")
runs.test.tsx alone ×3 1 of 3 failed 2 of 3 failed
validate --strict . passes passes
validate --strict plugins/altimate-code fails: ICON_MISSING plus one new TS18048 (N5) fails: ICON_MISSING
env reads listed by validate ALTIMATE_TELEMETRY_DISABLED, OPENCODE_DISABLE_TELEMETRY, WSL_DISTRO_NAME (the last predates this PR) WSL_DISTRO_NAME
tests/*.sh (8) all pass all pass
pytest tests/ 65 pass 65 pass
new tests on main's sources 29 fail in usage, cost and health, and 2 in task-impact (no usage events exist there); the opt-out-only tests pass –

I ran no live claude --plugin-dir session: an isolated config stops at the login screen. The test kit, plus the real CLI and a local sink, stand in for it.

Merge-order note

These events need altimate-code #1775 (plugin_session_start / plugin_feature_used). No released altimate-code has those actions yet. Until one does, every event starts a CLI that exits 1 silently, so nothing is sent or shown. Merge #1775 and release it before, or together with, this plugin release. This is not a block.

@hkaltai
hkaltai merged commit 2a9cbaf into main Nov 19, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants