feat(telemetry): notify users of telemetry collection on first run by Hweinstock · Pull Request #10 · Hweinstock/agentcore-cli

Hweinstock · 2026-08-31T20:00:45Z

Summary

Notify users of telemetry collection (and how to opt out) on the first run of the CLI — when no installationId has yet been persisted to ~/.agentcore/config.json. The notice is printed to stderr and never shown again once an installationId exists.

Spec

Problem: The user is never notified of telemetry collection, or of ways to opt out.

Definition of Done:

On fresh install (no installationId in ~/.agentcore/config.json), print a notice that the CLI collects usage analytics, mirroring the message style of src/cli/notices.ts on main.
The message must NOT display on installs where an installationId already exists.
A unit test exercises both paths.

Base branch: refactor.

Implementation

First-run detection is done explicitly at the root; the config accessor no longer mutates config as a side effect.

installationId defaults to unset.DEFAULT_GLOBAL_CONFIG.installationId is undefined and GlobalConfig.installationId is optional. DefaultGlobalConfigAccessor.get() no longer generates or persists an id.
Root check (src/index.ts): const isFirstRun = config.installationId === undefined. On first run, generate crypto.randomUUID() and persist it via globalConfigAccessor.set(...) (best-effort) before routing — telemetry validates installation_id as a required UUID, so a value must exist by the time metrics emit. The notice is then printed in the finally block.
src/telemetry/notice.ts: a single printFirstRunNotice(isFirstRun, out).

Fallout from making the default id unset

Removed two config.test.tsx tests that asserted the previous accessor auto-population — that behavior is intentionally relocated to the root (still exercised end-to-end below).
Three telemetry tests now supply an explicit installationId (they model an already-installed CLI, whose resource attributes require a UUID).

Verification

Automated

bun test — 2557 pass, 0 fail.
bun run typecheck — clean.
bun run lint:check — clean.

Manual (end-to-end, isolated `HOME`)

$ TH=$(mktemp -d)
# Run 1 — fresh install: notice on stderr, config.json created with an installationId
$ HOME="$TH" bun run src/index.ts config telemetry.enabled
<command output on stdout>
# stderr:
The AgentCore CLI collects aggregated, anonymous usage analytics to help improve the tool.
To opt out: agentcore config telemetry.enabled false
To audit: agentcore config telemetry.audit true
$ cat "$TH/.agentcore/config.json"
{ "installationId": "<uuid>", ... }
# Run 2 — installationId now exists: no notice
$ HOME="$TH" bun run src/index.ts config telemetry.enabled
<command output on stdout, no notice on stderr>

Notice count on stderr — Run 1: 1, Run 2: 0.

How to reproduce

git fetch fork feat/telemetry-first-run-notice && git checkout feat/telemetry-first-run-notice
bun install
bun test src/telemetry/notice.test.ts
TH=$(mktemp -d); HOME="$TH" bun run src/index.ts config telemetry.enabled # prints notice on stderr
HOME="$TH" bun run src/index.ts config telemetry.enabled # silent
rm -rf "$TH"

Hweinstock

lets simplify this approach. Lets just remove the logic that globalConfigAccessor populates the installationId as a side effect, then ecplicitly at the root level check,

does installationId exist in global config?

if no, set it to a random uuid, and set isFirstRun (a local variable) to true.
if yes, do nothing.

This will require updating the default installationId to undefined.

Hweinstock · 2026-08-31T22:07:56Z

 exit_reason: "success",
 });

+ // Capture first-run state up front: routing and telemetry emission both read


remove these useless comments. Also the isFirstRun should still return true, even if the installationId was written as a side effect.

Hweinstock · 2026-08-31T22:08:20Z


 /**
- * In-memory GlobalConfigAccessor for tests.
+ * In-memory GlobalConfigAccessor for tests. Represents an already-installed


no need to change this comment.

Hweinstock · 2026-08-31T22:09:13Z

+}
+
+/** Writes the telemetry notice to the given stream, but only on a first run. */
+export function printFirstRunNotice(isFirstRun: boolean, out: { write(text: string): void }): void {


lets just inline the function above here, and only have one function.

Hweinstock · 2026-08-31T22:10:44Z

@@ -0,0 +1,34 @@
+import { test, describe, expect } from "bun:test";


we only need one test, a test.each that checks verifies isFirstRun prints, and isFirstRun false doesn't.

Hweinstock · 2026-08-31T22:11:20Z

 set(newConfig: GlobalConfig): Promise<GlobalConfig>;
+ /**
+ * Returns true on the first run of the CLI, i.e. when no installationId has
+ * yet been persisted to the config file. Reflects the state before {@link get}


just replace this with Returns true on the first run of the CLI on a new machine.

Hweinstock · 2026-08-31T22:11:37Z

+ public async isFirstRun(): Promise<boolean> {
+ if (this.firstRun !== undefined) return this.firstRun;
+
+ // A first run is one where no installationId has been persisted yet. A


avoid all these comments.

Hweinstock · 2026-08-31T22:12:41Z

@@ -0,0 +1,69 @@
+import { test, describe, beforeEach, afterEach, expect } from "bun:test";


remove these tests.

Hweinstock · 2026-08-31T22:13:58Z


 const configFileData = await this.readConfigFile();

+ // capture first-run state before we populate an installationId below, so a


remove these comments

Hweinstock · 2026-09-01T00:04:07Z


 /**
- * Default values for the global config. Includes a unique installationId for each process.
+ * Default values for the global config. installationId is unset by default and


remove the installationId part of this comment.

Hweinstock · 2026-09-01T00:05:34Z

+ try {
+ await globalConfigAccessor.set({ ...globalConfig, installationId: crypto.randomUUID() });
+ } catch {
+ // best effort


we should log the error here, using the pattern below.

Hweinstock · 2026-08-31T20:00:45Z

Summary

Notify users of telemetry collection (and how to opt out) on the first run of the CLI — when no installationId has yet been persisted to ~/.agentcore/config.json. The notice is printed to stderr and never shown again once an installationId exists.

Spec

Problem: The user is never notified of telemetry collection, or of ways to opt out.

Definition of Done:

On fresh install (no installationId in ~/.agentcore/config.json), print a notice that the CLI collects usage analytics, mirroring the message style of src/cli/notices.ts on main.
The message must NOT display on installs where an installationId already exists.
A unit test exercises both paths.

Base branch: refactor.

Implementation

First-run detection is done explicitly at the root; the config accessor no longer mutates config as a side effect.

installationId defaults to unset.DEFAULT_GLOBAL_CONFIG.installationId is undefined and GlobalConfig.installationId is optional. DefaultGlobalConfigAccessor.get() no longer generates or persists an id.
Root check (src/index.ts): const isFirstRun = config.installationId === undefined. On first run, generate crypto.randomUUID() and persist it via globalConfigAccessor.set(...) (best-effort) before routing — telemetry validates installation_id as a required UUID, so a value must exist by the time metrics emit. The notice is then printed in the finally block.
src/telemetry/notice.ts: a single printFirstRunNotice(isFirstRun, out).

Fallout from making the default id unset

Removed two config.test.tsx tests that asserted the previous accessor auto-population — that behavior is intentionally relocated to the root (still exercised end-to-end below).
Three telemetry tests now supply an explicit installationId (they model an already-installed CLI, whose resource attributes require a UUID).

Verification

Automated

bun test — 2557 pass, 0 fail.
bun run typecheck — clean.
bun run lint:check — clean.

Manual (end-to-end, isolated `HOME`)

$ TH=$(mktemp -d)
# Run 1 — fresh install: notice on stderr, config.json created with an installationId
$ HOME="$TH" bun run src/index.ts config telemetry.enabled
<command output on stdout>
# stderr:
The AgentCore CLI collects aggregated, anonymous usage analytics to help improve the tool.
To opt out: agentcore config telemetry.enabled false
To audit: agentcore config telemetry.audit true
$ cat "$TH/.agentcore/config.json"
{ "installationId": "<uuid>", ... }
# Run 2 — installationId now exists: no notice
$ HOME="$TH" bun run src/index.ts config telemetry.enabled
<command output on stdout, no notice on stderr>

Notice count on stderr — Run 1: 1, Run 2: 0.

How to reproduce

git fetch fork feat/telemetry-first-run-notice && git checkout feat/telemetry-first-run-notice
bun install
bun test src/telemetry/notice.test.ts
TH=$(mktemp -d); HOME="$TH" bun run src/index.ts config telemetry.enabled # prints notice on stderr
HOME="$TH" bun run src/index.ts config telemetry.enabled # silent
rm -rf "$TH"

Hweinstock

lets simplify this approach. Lets just remove the logic that globalConfigAccessor populates the installationId as a side effect, then ecplicitly at the root level check,

does installationId exist in global config?

if no, set it to a random uuid, and set isFirstRun (a local variable) to true.
if yes, do nothing.

This will require updating the default installationId to undefined.

Hweinstock · 2026-08-31T22:07:56Z

 exit_reason: "success",
 });

+ // Capture first-run state up front: routing and telemetry emission both read


remove these useless comments. Also the isFirstRun should still return true, even if the installationId was written as a side effect.

Hweinstock · 2026-08-31T22:08:20Z


 /**
- * In-memory GlobalConfigAccessor for tests.
+ * In-memory GlobalConfigAccessor for tests. Represents an already-installed


no need to change this comment.

Hweinstock · 2026-08-31T22:09:13Z

+}
+
+/** Writes the telemetry notice to the given stream, but only on a first run. */
+export function printFirstRunNotice(isFirstRun: boolean, out: { write(text: string): void }): void {


lets just inline the function above here, and only have one function.

Hweinstock · 2026-08-31T22:10:44Z

@@ -0,0 +1,34 @@
+import { test, describe, expect } from "bun:test";


we only need one test, a test.each that checks verifies isFirstRun prints, and isFirstRun false doesn't.

Hweinstock · 2026-08-31T22:11:20Z

 set(newConfig: GlobalConfig): Promise<GlobalConfig>;
+ /**
+ * Returns true on the first run of the CLI, i.e. when no installationId has
+ * yet been persisted to the config file. Reflects the state before {@link get}


just replace this with Returns true on the first run of the CLI on a new machine.

Hweinstock · 2026-08-31T22:11:37Z

+ public async isFirstRun(): Promise<boolean> {
+ if (this.firstRun !== undefined) return this.firstRun;
+
+ // A first run is one where no installationId has been persisted yet. A


avoid all these comments.

Hweinstock · 2026-08-31T22:12:41Z

@@ -0,0 +1,69 @@
+import { test, describe, beforeEach, afterEach, expect } from "bun:test";


remove these tests.

Hweinstock · 2026-08-31T22:13:58Z


 const configFileData = await this.readConfigFile();

+ // capture first-run state before we populate an installationId below, so a


remove these comments

Hweinstock · 2026-09-01T00:04:07Z


 /**
- * Default values for the global config. Includes a unique installationId for each process.
+ * Default values for the global config. installationId is unset by default and


remove the installationId part of this comment.

Hweinstock · 2026-09-01T00:05:34Z

+ try {
+ await globalConfigAccessor.set({ ...globalConfig, installationId: crypto.randomUUID() });
+ } catch {
+ // best effort


we should log the error here, using the pattern below.

Hweinstock · 2026-08-31T20:00:45Z

Summary

Notify users of telemetry collection (and how to opt out) on the first run of the CLI — when no installationId has yet been persisted to ~/.agentcore/config.json. The notice is printed to stderr and never shown again once an installationId exists.

Spec

Problem: The user is never notified of telemetry collection, or of ways to opt out.

Definition of Done:

On fresh install (no installationId in ~/.agentcore/config.json), print a notice that the CLI collects usage analytics, mirroring the message style of src/cli/notices.ts on main.
The message must NOT display on installs where an installationId already exists.
A unit test exercises both paths.

Base branch: refactor.

Implementation

First-run detection is done explicitly at the root; the config accessor no longer mutates config as a side effect.

installationId defaults to unset.DEFAULT_GLOBAL_CONFIG.installationId is undefined and GlobalConfig.installationId is optional. DefaultGlobalConfigAccessor.get() no longer generates or persists an id.
Root check (src/index.ts): const isFirstRun = config.installationId === undefined. On first run, generate crypto.randomUUID() and persist it via globalConfigAccessor.set(...) (best-effort) before routing — telemetry validates installation_id as a required UUID, so a value must exist by the time metrics emit. The notice is then printed in the finally block.
src/telemetry/notice.ts: a single printFirstRunNotice(isFirstRun, out).

Fallout from making the default id unset

Removed two config.test.tsx tests that asserted the previous accessor auto-population — that behavior is intentionally relocated to the root (still exercised end-to-end below).
Three telemetry tests now supply an explicit installationId (they model an already-installed CLI, whose resource attributes require a UUID).

Verification

Automated

bun test — 2557 pass, 0 fail.
bun run typecheck — clean.
bun run lint:check — clean.

Manual (end-to-end, isolated `HOME`)

$ TH=$(mktemp -d)
# Run 1 — fresh install: notice on stderr, config.json created with an installationId
$ HOME="$TH" bun run src/index.ts config telemetry.enabled
<command output on stdout>
# stderr:
The AgentCore CLI collects aggregated, anonymous usage analytics to help improve the tool.
To opt out: agentcore config telemetry.enabled false
To audit: agentcore config telemetry.audit true
$ cat "$TH/.agentcore/config.json"
{ "installationId": "<uuid>", ... }
# Run 2 — installationId now exists: no notice
$ HOME="$TH" bun run src/index.ts config telemetry.enabled
<command output on stdout, no notice on stderr>

Notice count on stderr — Run 1: 1, Run 2: 0.

How to reproduce

git fetch fork feat/telemetry-first-run-notice && git checkout feat/telemetry-first-run-notice
bun install
bun test src/telemetry/notice.test.ts
TH=$(mktemp -d); HOME="$TH" bun run src/index.ts config telemetry.enabled # prints notice on stderr
HOME="$TH" bun run src/index.ts config telemetry.enabled # silent
rm -rf "$TH"

Hweinstock

lets simplify this approach. Lets just remove the logic that globalConfigAccessor populates the installationId as a side effect, then ecplicitly at the root level check,

does installationId exist in global config?

if no, set it to a random uuid, and set isFirstRun (a local variable) to true.
if yes, do nothing.

This will require updating the default installationId to undefined.

Hweinstock · 2026-08-31T22:07:56Z

 exit_reason: "success",
 });

+ // Capture first-run state up front: routing and telemetry emission both read


remove these useless comments. Also the isFirstRun should still return true, even if the installationId was written as a side effect.

Hweinstock · 2026-08-31T22:08:20Z


 /**
- * In-memory GlobalConfigAccessor for tests.
+ * In-memory GlobalConfigAccessor for tests. Represents an already-installed


no need to change this comment.

Hweinstock · 2026-08-31T22:09:13Z

+}
+
+/** Writes the telemetry notice to the given stream, but only on a first run. */
+export function printFirstRunNotice(isFirstRun: boolean, out: { write(text: string): void }): void {


lets just inline the function above here, and only have one function.

Hweinstock · 2026-08-31T22:10:44Z

@@ -0,0 +1,34 @@
+import { test, describe, expect } from "bun:test";


we only need one test, a test.each that checks verifies isFirstRun prints, and isFirstRun false doesn't.

Hweinstock · 2026-08-31T22:11:20Z

 set(newConfig: GlobalConfig): Promise<GlobalConfig>;
+ /**
+ * Returns true on the first run of the CLI, i.e. when no installationId has
+ * yet been persisted to the config file. Reflects the state before {@link get}


just replace this with Returns true on the first run of the CLI on a new machine.

Hweinstock · 2026-08-31T22:11:37Z

+ public async isFirstRun(): Promise<boolean> {
+ if (this.firstRun !== undefined) return this.firstRun;
+
+ // A first run is one where no installationId has been persisted yet. A


avoid all these comments.

Hweinstock · 2026-08-31T22:12:41Z

@@ -0,0 +1,69 @@
+import { test, describe, beforeEach, afterEach, expect } from "bun:test";


remove these tests.

Hweinstock · 2026-08-31T22:13:58Z


 const configFileData = await this.readConfigFile();

+ // capture first-run state before we populate an installationId below, so a


remove these comments

Hweinstock · 2026-09-01T00:04:07Z


 /**
- * Default values for the global config. Includes a unique installationId for each process.
+ * Default values for the global config. installationId is unset by default and


remove the installationId part of this comment.

Hweinstock · 2026-09-01T00:05:34Z

+ try {
+ await globalConfigAccessor.set({ ...globalConfig, installationId: crypto.randomUUID() });
+ } catch {
+ // best effort


we should log the error here, using the pattern below.

Hweinstock · 2026-08-31T20:00:45Z

Summary

Notify users of telemetry collection (and how to opt out) on the first run of the CLI — when no installationId has yet been persisted to ~/.agentcore/config.json. The notice is printed to stderr and never shown again once an installationId exists.

Spec

Problem: The user is never notified of telemetry collection, or of ways to opt out.

Definition of Done:

On fresh install (no installationId in ~/.agentcore/config.json), print a notice that the CLI collects usage analytics, mirroring the message style of src/cli/notices.ts on main.
The message must NOT display on installs where an installationId already exists.
A unit test exercises both paths.

Base branch: refactor.

Implementation

First-run detection is done explicitly at the root; the config accessor no longer mutates config as a side effect.

installationId defaults to unset.DEFAULT_GLOBAL_CONFIG.installationId is undefined and GlobalConfig.installationId is optional. DefaultGlobalConfigAccessor.get() no longer generates or persists an id.
Root check (src/index.ts): const isFirstRun = config.installationId === undefined. On first run, generate crypto.randomUUID() and persist it via globalConfigAccessor.set(...) (best-effort) before routing — telemetry validates installation_id as a required UUID, so a value must exist by the time metrics emit. The notice is then printed in the finally block.
src/telemetry/notice.ts: a single printFirstRunNotice(isFirstRun, out).

Fallout from making the default id unset

Removed two config.test.tsx tests that asserted the previous accessor auto-population — that behavior is intentionally relocated to the root (still exercised end-to-end below).
Three telemetry tests now supply an explicit installationId (they model an already-installed CLI, whose resource attributes require a UUID).

Verification

Automated

bun test — 2557 pass, 0 fail.
bun run typecheck — clean.
bun run lint:check — clean.

Manual (end-to-end, isolated `HOME`)

$ TH=$(mktemp -d)
# Run 1 — fresh install: notice on stderr, config.json created with an installationId
$ HOME="$TH" bun run src/index.ts config telemetry.enabled
<command output on stdout>
# stderr:
The AgentCore CLI collects aggregated, anonymous usage analytics to help improve the tool.
To opt out: agentcore config telemetry.enabled false
To audit: agentcore config telemetry.audit true
$ cat "$TH/.agentcore/config.json"
{ "installationId": "<uuid>", ... }
# Run 2 — installationId now exists: no notice
$ HOME="$TH" bun run src/index.ts config telemetry.enabled
<command output on stdout, no notice on stderr>

Notice count on stderr — Run 1: 1, Run 2: 0.

How to reproduce

git fetch fork feat/telemetry-first-run-notice && git checkout feat/telemetry-first-run-notice
bun install
bun test src/telemetry/notice.test.ts
TH=$(mktemp -d); HOME="$TH" bun run src/index.ts config telemetry.enabled # prints notice on stderr
HOME="$TH" bun run src/index.ts config telemetry.enabled # silent
rm -rf "$TH"

Hweinstock

lets simplify this approach. Lets just remove the logic that globalConfigAccessor populates the installationId as a side effect, then ecplicitly at the root level check,

does installationId exist in global config?

if no, set it to a random uuid, and set isFirstRun (a local variable) to true.
if yes, do nothing.

This will require updating the default installationId to undefined.

Hweinstock · 2026-08-31T22:07:56Z

 exit_reason: "success",
 });

+ // Capture first-run state up front: routing and telemetry emission both read


remove these useless comments. Also the isFirstRun should still return true, even if the installationId was written as a side effect.

Hweinstock · 2026-08-31T22:08:20Z


 /**
- * In-memory GlobalConfigAccessor for tests.
+ * In-memory GlobalConfigAccessor for tests. Represents an already-installed


no need to change this comment.

Hweinstock · 2026-08-31T22:09:13Z

+}
+
+/** Writes the telemetry notice to the given stream, but only on a first run. */
+export function printFirstRunNotice(isFirstRun: boolean, out: { write(text: string): void }): void {


lets just inline the function above here, and only have one function.

Hweinstock · 2026-08-31T22:10:44Z

@@ -0,0 +1,34 @@
+import { test, describe, expect } from "bun:test";


we only need one test, a test.each that checks verifies isFirstRun prints, and isFirstRun false doesn't.

Hweinstock · 2026-08-31T22:11:20Z

 set(newConfig: GlobalConfig): Promise<GlobalConfig>;
+ /**
+ * Returns true on the first run of the CLI, i.e. when no installationId has
+ * yet been persisted to the config file. Reflects the state before {@link get}


just replace this with Returns true on the first run of the CLI on a new machine.

Hweinstock · 2026-08-31T22:11:37Z

+ public async isFirstRun(): Promise<boolean> {
+ if (this.firstRun !== undefined) return this.firstRun;
+
+ // A first run is one where no installationId has been persisted yet. A


avoid all these comments.

Hweinstock · 2026-08-31T22:12:41Z

@@ -0,0 +1,69 @@
+import { test, describe, beforeEach, afterEach, expect } from "bun:test";


remove these tests.

Hweinstock · 2026-08-31T22:13:58Z


 const configFileData = await this.readConfigFile();

+ // capture first-run state before we populate an installationId below, so a


remove these comments

Hweinstock · 2026-09-01T00:04:07Z


 /**
- * Default values for the global config. Includes a unique installationId for each process.
+ * Default values for the global config. installationId is unset by default and


remove the installationId part of this comment.

Hweinstock · 2026-09-01T00:05:34Z

+ try {
+ await globalConfigAccessor.set({ ...globalConfig, installationId: crypto.randomUUID() });
+ } catch {
+ // best effort


we should log the error here, using the pattern below.

Hweinstock · 2026-08-31T20:00:45Z

Summary

Notify users of telemetry collection (and how to opt out) on the first run of the CLI — when no installationId has yet been persisted to ~/.agentcore/config.json. The notice is printed to stderr and never shown again once an installationId exists.

Spec

Problem: The user is never notified of telemetry collection, or of ways to opt out.

Definition of Done:

On fresh install (no installationId in ~/.agentcore/config.json), print a notice that the CLI collects usage analytics, mirroring the message style of src/cli/notices.ts on main.
The message must NOT display on installs where an installationId already exists.
A unit test exercises both paths.

Base branch: refactor.

Implementation

First-run detection is done explicitly at the root; the config accessor no longer mutates config as a side effect.

installationId defaults to unset.DEFAULT_GLOBAL_CONFIG.installationId is undefined and GlobalConfig.installationId is optional. DefaultGlobalConfigAccessor.get() no longer generates or persists an id.
Root check (src/index.ts): const isFirstRun = config.installationId === undefined. On first run, generate crypto.randomUUID() and persist it via globalConfigAccessor.set(...) (best-effort) before routing — telemetry validates installation_id as a required UUID, so a value must exist by the time metrics emit. The notice is then printed in the finally block.
src/telemetry/notice.ts: a single printFirstRunNotice(isFirstRun, out).

Fallout from making the default id unset

Removed two config.test.tsx tests that asserted the previous accessor auto-population — that behavior is intentionally relocated to the root (still exercised end-to-end below).
Three telemetry tests now supply an explicit installationId (they model an already-installed CLI, whose resource attributes require a UUID).

Verification

Automated

bun test — 2557 pass, 0 fail.
bun run typecheck — clean.
bun run lint:check — clean.

Manual (end-to-end, isolated `HOME`)

$ TH=$(mktemp -d)
# Run 1 — fresh install: notice on stderr, config.json created with an installationId
$ HOME="$TH" bun run src/index.ts config telemetry.enabled
<command output on stdout>
# stderr:
The AgentCore CLI collects aggregated, anonymous usage analytics to help improve the tool.
To opt out: agentcore config telemetry.enabled false
To audit: agentcore config telemetry.audit true
$ cat "$TH/.agentcore/config.json"
{ "installationId": "<uuid>", ... }
# Run 2 — installationId now exists: no notice
$ HOME="$TH" bun run src/index.ts config telemetry.enabled
<command output on stdout, no notice on stderr>

Notice count on stderr — Run 1: 1, Run 2: 0.

How to reproduce

git fetch fork feat/telemetry-first-run-notice && git checkout feat/telemetry-first-run-notice
bun install
bun test src/telemetry/notice.test.ts
TH=$(mktemp -d); HOME="$TH" bun run src/index.ts config telemetry.enabled # prints notice on stderr
HOME="$TH" bun run src/index.ts config telemetry.enabled # silent
rm -rf "$TH"

Hweinstock

lets simplify this approach. Lets just remove the logic that globalConfigAccessor populates the installationId as a side effect, then ecplicitly at the root level check,

does installationId exist in global config?

if no, set it to a random uuid, and set isFirstRun (a local variable) to true.
if yes, do nothing.

This will require updating the default installationId to undefined.

Hweinstock · 2026-08-31T22:07:56Z

 exit_reason: "success",
 });

+ // Capture first-run state up front: routing and telemetry emission both read


remove these useless comments. Also the isFirstRun should still return true, even if the installationId was written as a side effect.

Hweinstock · 2026-08-31T22:08:20Z


 /**
- * In-memory GlobalConfigAccessor for tests.
+ * In-memory GlobalConfigAccessor for tests. Represents an already-installed


no need to change this comment.

Hweinstock · 2026-08-31T22:09:13Z

+}
+
+/** Writes the telemetry notice to the given stream, but only on a first run. */
+export function printFirstRunNotice(isFirstRun: boolean, out: { write(text: string): void }): void {


lets just inline the function above here, and only have one function.

Hweinstock · 2026-08-31T22:10:44Z

@@ -0,0 +1,34 @@
+import { test, describe, expect } from "bun:test";


we only need one test, a test.each that checks verifies isFirstRun prints, and isFirstRun false doesn't.

Hweinstock · 2026-08-31T22:11:20Z

 set(newConfig: GlobalConfig): Promise<GlobalConfig>;
+ /**
+ * Returns true on the first run of the CLI, i.e. when no installationId has
+ * yet been persisted to the config file. Reflects the state before {@link get}


just replace this with Returns true on the first run of the CLI on a new machine.

Hweinstock · 2026-08-31T22:11:37Z

+ public async isFirstRun(): Promise<boolean> {
+ if (this.firstRun !== undefined) return this.firstRun;
+
+ // A first run is one where no installationId has been persisted yet. A


avoid all these comments.

Hweinstock · 2026-08-31T22:12:41Z

@@ -0,0 +1,69 @@
+import { test, describe, beforeEach, afterEach, expect } from "bun:test";


remove these tests.

Hweinstock · 2026-08-31T22:13:58Z


 const configFileData = await this.readConfigFile();

+ // capture first-run state before we populate an installationId below, so a


remove these comments

Hweinstock · 2026-09-01T00:04:07Z


 /**
- * Default values for the global config. Includes a unique installationId for each process.
+ * Default values for the global config. installationId is unset by default and


remove the installationId part of this comment.

Hweinstock · 2026-09-01T00:05:34Z

+ try {
+ await globalConfigAccessor.set({ ...globalConfig, installationId: crypto.randomUUID() });
+ } catch {
+ // best effort


we should log the error here, using the pattern below.

Hweinstock · 2026-08-31T20:00:45Z

Summary

Notify users of telemetry collection (and how to opt out) on the first run of the CLI — when no installationId has yet been persisted to ~/.agentcore/config.json. The notice is printed to stderr and never shown again once an installationId exists.

Spec

Problem: The user is never notified of telemetry collection, or of ways to opt out.

Definition of Done:

On fresh install (no installationId in ~/.agentcore/config.json), print a notice that the CLI collects usage analytics, mirroring the message style of src/cli/notices.ts on main.
The message must NOT display on installs where an installationId already exists.
A unit test exercises both paths.

Base branch: refactor.

Implementation

First-run detection is done explicitly at the root; the config accessor no longer mutates config as a side effect.

installationId defaults to unset.DEFAULT_GLOBAL_CONFIG.installationId is undefined and GlobalConfig.installationId is optional. DefaultGlobalConfigAccessor.get() no longer generates or persists an id.
Root check (src/index.ts): const isFirstRun = config.installationId === undefined. On first run, generate crypto.randomUUID() and persist it via globalConfigAccessor.set(...) (best-effort) before routing — telemetry validates installation_id as a required UUID, so a value must exist by the time metrics emit. The notice is then printed in the finally block.
src/telemetry/notice.ts: a single printFirstRunNotice(isFirstRun, out).

Fallout from making the default id unset

Removed two config.test.tsx tests that asserted the previous accessor auto-population — that behavior is intentionally relocated to the root (still exercised end-to-end below).
Three telemetry tests now supply an explicit installationId (they model an already-installed CLI, whose resource attributes require a UUID).

Verification

Automated

bun test — 2557 pass, 0 fail.
bun run typecheck — clean.
bun run lint:check — clean.

Manual (end-to-end, isolated `HOME`)

$ TH=$(mktemp -d)
# Run 1 — fresh install: notice on stderr, config.json created with an installationId
$ HOME="$TH" bun run src/index.ts config telemetry.enabled
<command output on stdout>
# stderr:
The AgentCore CLI collects aggregated, anonymous usage analytics to help improve the tool.
To opt out: agentcore config telemetry.enabled false
To audit: agentcore config telemetry.audit true
$ cat "$TH/.agentcore/config.json"
{ "installationId": "<uuid>", ... }
# Run 2 — installationId now exists: no notice
$ HOME="$TH" bun run src/index.ts config telemetry.enabled
<command output on stdout, no notice on stderr>

Notice count on stderr — Run 1: 1, Run 2: 0.

How to reproduce

git fetch fork feat/telemetry-first-run-notice && git checkout feat/telemetry-first-run-notice
bun install
bun test src/telemetry/notice.test.ts
TH=$(mktemp -d); HOME="$TH" bun run src/index.ts config telemetry.enabled # prints notice on stderr
HOME="$TH" bun run src/index.ts config telemetry.enabled # silent
rm -rf "$TH"

Hweinstock

lets simplify this approach. Lets just remove the logic that globalConfigAccessor populates the installationId as a side effect, then ecplicitly at the root level check,

does installationId exist in global config?

if no, set it to a random uuid, and set isFirstRun (a local variable) to true.
if yes, do nothing.

This will require updating the default installationId to undefined.

Hweinstock · 2026-08-31T22:07:56Z

 exit_reason: "success",
 });

+ // Capture first-run state up front: routing and telemetry emission both read


remove these useless comments. Also the isFirstRun should still return true, even if the installationId was written as a side effect.

Hweinstock · 2026-08-31T22:08:20Z


 /**
- * In-memory GlobalConfigAccessor for tests.
+ * In-memory GlobalConfigAccessor for tests. Represents an already-installed


no need to change this comment.

Hweinstock · 2026-08-31T22:09:13Z

+}
+
+/** Writes the telemetry notice to the given stream, but only on a first run. */
+export function printFirstRunNotice(isFirstRun: boolean, out: { write(text: string): void }): void {


lets just inline the function above here, and only have one function.

Hweinstock · 2026-08-31T22:10:44Z

@@ -0,0 +1,34 @@
+import { test, describe, expect } from "bun:test";


we only need one test, a test.each that checks verifies isFirstRun prints, and isFirstRun false doesn't.

Hweinstock · 2026-08-31T22:11:20Z

 set(newConfig: GlobalConfig): Promise<GlobalConfig>;
+ /**
+ * Returns true on the first run of the CLI, i.e. when no installationId has
+ * yet been persisted to the config file. Reflects the state before {@link get}


just replace this with Returns true on the first run of the CLI on a new machine.

Hweinstock · 2026-08-31T22:11:37Z

+ public async isFirstRun(): Promise<boolean> {
+ if (this.firstRun !== undefined) return this.firstRun;
+
+ // A first run is one where no installationId has been persisted yet. A


avoid all these comments.

Hweinstock · 2026-08-31T22:12:41Z

@@ -0,0 +1,69 @@
+import { test, describe, beforeEach, afterEach, expect } from "bun:test";


remove these tests.

Hweinstock · 2026-08-31T22:13:58Z


 const configFileData = await this.readConfigFile();

+ // capture first-run state before we populate an installationId below, so a


remove these comments

Hweinstock · 2026-09-01T00:04:07Z


 /**
- * Default values for the global config. Includes a unique installationId for each process.
+ * Default values for the global config. installationId is unset by default and


remove the installationId part of this comment.

Hweinstock · 2026-09-01T00:05:34Z

+ try {
+ await globalConfigAccessor.set({ ...globalConfig, installationId: crypto.randomUUID() });
+ } catch {
+ // best effort


we should log the error here, using the pattern below.

Hweinstock · 2026-08-31T20:00:45Z

Summary

Notify users of telemetry collection (and how to opt out) on the first run of the CLI — when no installationId has yet been persisted to ~/.agentcore/config.json. The notice is printed to stderr and never shown again once an installationId exists.

Spec

Problem: The user is never notified of telemetry collection, or of ways to opt out.

Definition of Done:

On fresh install (no installationId in ~/.agentcore/config.json), print a notice that the CLI collects usage analytics, mirroring the message style of src/cli/notices.ts on main.
The message must NOT display on installs where an installationId already exists.
A unit test exercises both paths.

Base branch: refactor.

Implementation

First-run detection is done explicitly at the root; the config accessor no longer mutates config as a side effect.

installationId defaults to unset.DEFAULT_GLOBAL_CONFIG.installationId is undefined and GlobalConfig.installationId is optional. DefaultGlobalConfigAccessor.get() no longer generates or persists an id.
Root check (src/index.ts): const isFirstRun = config.installationId === undefined. On first run, generate crypto.randomUUID() and persist it via globalConfigAccessor.set(...) (best-effort) before routing — telemetry validates installation_id as a required UUID, so a value must exist by the time metrics emit. The notice is then printed in the finally block.
src/telemetry/notice.ts: a single printFirstRunNotice(isFirstRun, out).

Fallout from making the default id unset

Removed two config.test.tsx tests that asserted the previous accessor auto-population — that behavior is intentionally relocated to the root (still exercised end-to-end below).
Three telemetry tests now supply an explicit installationId (they model an already-installed CLI, whose resource attributes require a UUID).

Verification

Automated

bun test — 2557 pass, 0 fail.
bun run typecheck — clean.
bun run lint:check — clean.

Manual (end-to-end, isolated `HOME`)

$ TH=$(mktemp -d)
# Run 1 — fresh install: notice on stderr, config.json created with an installationId
$ HOME="$TH" bun run src/index.ts config telemetry.enabled
<command output on stdout>
# stderr:
The AgentCore CLI collects aggregated, anonymous usage analytics to help improve the tool.
To opt out: agentcore config telemetry.enabled false
To audit: agentcore config telemetry.audit true
$ cat "$TH/.agentcore/config.json"
{ "installationId": "<uuid>", ... }
# Run 2 — installationId now exists: no notice
$ HOME="$TH" bun run src/index.ts config telemetry.enabled
<command output on stdout, no notice on stderr>

Notice count on stderr — Run 1: 1, Run 2: 0.

How to reproduce

git fetch fork feat/telemetry-first-run-notice && git checkout feat/telemetry-first-run-notice
bun install
bun test src/telemetry/notice.test.ts
TH=$(mktemp -d); HOME="$TH" bun run src/index.ts config telemetry.enabled # prints notice on stderr
HOME="$TH" bun run src/index.ts config telemetry.enabled # silent
rm -rf "$TH"

Hweinstock

lets simplify this approach. Lets just remove the logic that globalConfigAccessor populates the installationId as a side effect, then ecplicitly at the root level check,

does installationId exist in global config?

if no, set it to a random uuid, and set isFirstRun (a local variable) to true.
if yes, do nothing.

This will require updating the default installationId to undefined.

Hweinstock · 2026-08-31T22:07:56Z

 exit_reason: "success",
 });

+ // Capture first-run state up front: routing and telemetry emission both read


remove these useless comments. Also the isFirstRun should still return true, even if the installationId was written as a side effect.

Hweinstock · 2026-08-31T22:08:20Z


 /**
- * In-memory GlobalConfigAccessor for tests.
+ * In-memory GlobalConfigAccessor for tests. Represents an already-installed


no need to change this comment.

Hweinstock · 2026-08-31T22:09:13Z

+}
+
+/** Writes the telemetry notice to the given stream, but only on a first run. */
+export function printFirstRunNotice(isFirstRun: boolean, out: { write(text: string): void }): void {


lets just inline the function above here, and only have one function.

Hweinstock · 2026-08-31T22:10:44Z

@@ -0,0 +1,34 @@
+import { test, describe, expect } from "bun:test";


we only need one test, a test.each that checks verifies isFirstRun prints, and isFirstRun false doesn't.

Hweinstock · 2026-08-31T22:11:20Z

 set(newConfig: GlobalConfig): Promise<GlobalConfig>;
+ /**
+ * Returns true on the first run of the CLI, i.e. when no installationId has
+ * yet been persisted to the config file. Reflects the state before {@link get}


just replace this with Returns true on the first run of the CLI on a new machine.

Hweinstock · 2026-08-31T22:11:37Z

+ public async isFirstRun(): Promise<boolean> {
+ if (this.firstRun !== undefined) return this.firstRun;
+
+ // A first run is one where no installationId has been persisted yet. A


avoid all these comments.

Hweinstock · 2026-08-31T22:12:41Z

@@ -0,0 +1,69 @@
+import { test, describe, beforeEach, afterEach, expect } from "bun:test";


remove these tests.

Hweinstock · 2026-08-31T22:13:58Z


 const configFileData = await this.readConfigFile();

+ // capture first-run state before we populate an installationId below, so a


remove these comments

Hweinstock · 2026-09-01T00:04:07Z


 /**
- * Default values for the global config. Includes a unique installationId for each process.
+ * Default values for the global config. installationId is unset by default and


remove the installationId part of this comment.

Hweinstock · 2026-09-01T00:05:34Z

+ try {
+ await globalConfigAccessor.set({ ...globalConfig, installationId: crypto.randomUUID() });
+ } catch {
+ // best effort


we should log the error here, using the pattern below.

Hweinstock · 2026-08-31T20:00:45Z

Summary

Notify users of telemetry collection (and how to opt out) on the first run of the CLI — when no installationId has yet been persisted to ~/.agentcore/config.json. The notice is printed to stderr and never shown again once an installationId exists.

Spec

Problem: The user is never notified of telemetry collection, or of ways to opt out.

Definition of Done:

On fresh install (no installationId in ~/.agentcore/config.json), print a notice that the CLI collects usage analytics, mirroring the message style of src/cli/notices.ts on main.
The message must NOT display on installs where an installationId already exists.
A unit test exercises both paths.

Base branch: refactor.

Implementation

First-run detection is done explicitly at the root; the config accessor no longer mutates config as a side effect.

installationId defaults to unset.DEFAULT_GLOBAL_CONFIG.installationId is undefined and GlobalConfig.installationId is optional. DefaultGlobalConfigAccessor.get() no longer generates or persists an id.
Root check (src/index.ts): const isFirstRun = config.installationId === undefined. On first run, generate crypto.randomUUID() and persist it via globalConfigAccessor.set(...) (best-effort) before routing — telemetry validates installation_id as a required UUID, so a value must exist by the time metrics emit. The notice is then printed in the finally block.
src/telemetry/notice.ts: a single printFirstRunNotice(isFirstRun, out).

Fallout from making the default id unset

Removed two config.test.tsx tests that asserted the previous accessor auto-population — that behavior is intentionally relocated to the root (still exercised end-to-end below).
Three telemetry tests now supply an explicit installationId (they model an already-installed CLI, whose resource attributes require a UUID).

Verification

Automated

bun test — 2557 pass, 0 fail.
bun run typecheck — clean.
bun run lint:check — clean.

Manual (end-to-end, isolated `HOME`)

$ TH=$(mktemp -d)
# Run 1 — fresh install: notice on stderr, config.json created with an installationId
$ HOME="$TH" bun run src/index.ts config telemetry.enabled
<command output on stdout>
# stderr:
The AgentCore CLI collects aggregated, anonymous usage analytics to help improve the tool.
To opt out: agentcore config telemetry.enabled false
To audit: agentcore config telemetry.audit true
$ cat "$TH/.agentcore/config.json"
{ "installationId": "<uuid>", ... }
# Run 2 — installationId now exists: no notice
$ HOME="$TH" bun run src/index.ts config telemetry.enabled
<command output on stdout, no notice on stderr>

Notice count on stderr — Run 1: 1, Run 2: 0.

How to reproduce

git fetch fork feat/telemetry-first-run-notice && git checkout feat/telemetry-first-run-notice
bun install
bun test src/telemetry/notice.test.ts
TH=$(mktemp -d); HOME="$TH" bun run src/index.ts config telemetry.enabled # prints notice on stderr
HOME="$TH" bun run src/index.ts config telemetry.enabled # silent
rm -rf "$TH"

Hweinstock

lets simplify this approach. Lets just remove the logic that globalConfigAccessor populates the installationId as a side effect, then ecplicitly at the root level check,

does installationId exist in global config?

if no, set it to a random uuid, and set isFirstRun (a local variable) to true.
if yes, do nothing.

This will require updating the default installationId to undefined.

Hweinstock · 2026-08-31T22:07:56Z

 exit_reason: "success",
 });

+ // Capture first-run state up front: routing and telemetry emission both read


remove these useless comments. Also the isFirstRun should still return true, even if the installationId was written as a side effect.

Hweinstock · 2026-08-31T22:08:20Z


 /**
- * In-memory GlobalConfigAccessor for tests.
+ * In-memory GlobalConfigAccessor for tests. Represents an already-installed


no need to change this comment.

Hweinstock · 2026-08-31T22:09:13Z

+}
+
+/** Writes the telemetry notice to the given stream, but only on a first run. */
+export function printFirstRunNotice(isFirstRun: boolean, out: { write(text: string): void }): void {


lets just inline the function above here, and only have one function.

Hweinstock · 2026-08-31T22:10:44Z

@@ -0,0 +1,34 @@
+import { test, describe, expect } from "bun:test";


we only need one test, a test.each that checks verifies isFirstRun prints, and isFirstRun false doesn't.

Hweinstock · 2026-08-31T22:11:20Z

 set(newConfig: GlobalConfig): Promise<GlobalConfig>;
+ /**
+ * Returns true on the first run of the CLI, i.e. when no installationId has
+ * yet been persisted to the config file. Reflects the state before {@link get}


just replace this with Returns true on the first run of the CLI on a new machine.

Hweinstock · 2026-08-31T22:11:37Z

+ public async isFirstRun(): Promise<boolean> {
+ if (this.firstRun !== undefined) return this.firstRun;
+
+ // A first run is one where no installationId has been persisted yet. A


avoid all these comments.

Hweinstock · 2026-08-31T22:12:41Z

@@ -0,0 +1,69 @@
+import { test, describe, beforeEach, afterEach, expect } from "bun:test";


remove these tests.

Hweinstock · 2026-08-31T22:13:58Z


 const configFileData = await this.readConfigFile();

+ // capture first-run state before we populate an installationId below, so a


remove these comments

Hweinstock · 2026-09-01T00:04:07Z


 /**
- * Default values for the global config. Includes a unique installationId for each process.
+ * Default values for the global config. installationId is unset by default and


remove the installationId part of this comment.

Hweinstock · 2026-09-01T00:05:34Z

+ try {
+ await globalConfigAccessor.set({ ...globalConfig, installationId: crypto.randomUUID() });
+ } catch {
+ // best effort


we should log the error here, using the pattern below.

Hweinstock commented Aug 31, 2026
View reviewed changes

Hweinstock commented Sep 1, 2026
View reviewed changes

Hweinstock added 3 commits September 1, 2026 00:24

feat(globalConfig): detect first run via persisted installationId
d92c666

feat(telemetry): notify users of telemetry collection on first run
e4213e7

refactor(globalConfig): persist installationId at root on first run
e37e4d7

Hweinstock force-pushed the feat/telemetry-first-run-notice branch from 1e8a58f to cfb9da2Compare September 1, 2026 00:25

refactor(telemetry): simplify first-run notice to a single function
8254946

Hweinstock force-pushed the feat/telemetry-first-run-notice branch from cfb9da2 to 8254946Compare September 1, 2026 00:29

Hweinstock closed this Sep 1, 2026

Hweinstock commented Aug 31, 2026
View reviewed changes

Hweinstock commented Sep 1, 2026
View reviewed changes

Hweinstock added 3 commits September 1, 2026 00:24

feat(globalConfig): detect first run via persisted installationId
d92c666

feat(telemetry): notify users of telemetry collection on first run
e4213e7

refactor(globalConfig): persist installationId at root on first run
e37e4d7

Hweinstock force-pushed the feat/telemetry-first-run-notice branch from 1e8a58f to cfb9da2Compare September 1, 2026 00:25

refactor(telemetry): simplify first-run notice to a single function
8254946

Hweinstock force-pushed the feat/telemetry-first-run-notice branch from cfb9da2 to 8254946Compare September 1, 2026 00:29

Hweinstock closed this Sep 1, 2026

Hweinstock commented Aug 31, 2026
View reviewed changes

Hweinstock commented Sep 1, 2026
View reviewed changes

Hweinstock added 3 commits September 1, 2026 00:24

feat(globalConfig): detect first run via persisted installationId
d92c666

feat(telemetry): notify users of telemetry collection on first run
e4213e7

refactor(globalConfig): persist installationId at root on first run
e37e4d7

Hweinstock force-pushed the feat/telemetry-first-run-notice branch from 1e8a58f to cfb9da2Compare September 1, 2026 00:25

refactor(telemetry): simplify first-run notice to a single function
8254946

Hweinstock force-pushed the feat/telemetry-first-run-notice branch from cfb9da2 to 8254946Compare September 1, 2026 00:29

Hweinstock closed this Sep 1, 2026

Hweinstock commented Aug 31, 2026
View reviewed changes

Hweinstock commented Sep 1, 2026
View reviewed changes

Hweinstock added 3 commits September 1, 2026 00:24

feat(globalConfig): detect first run via persisted installationId
d92c666

feat(telemetry): notify users of telemetry collection on first run
e4213e7

refactor(globalConfig): persist installationId at root on first run
e37e4d7

Hweinstock force-pushed the feat/telemetry-first-run-notice branch from 1e8a58f to cfb9da2Compare September 1, 2026 00:25

refactor(telemetry): simplify first-run notice to a single function
8254946

Hweinstock force-pushed the feat/telemetry-first-run-notice branch from cfb9da2 to 8254946Compare September 1, 2026 00:29

Hweinstock closed this Sep 1, 2026

Hweinstock commented Aug 31, 2026
View reviewed changes

Hweinstock commented Sep 1, 2026
View reviewed changes

Hweinstock added 3 commits September 1, 2026 00:24

feat(globalConfig): detect first run via persisted installationId
d92c666

feat(telemetry): notify users of telemetry collection on first run
e4213e7

refactor(globalConfig): persist installationId at root on first run
e37e4d7

Hweinstock force-pushed the feat/telemetry-first-run-notice branch from 1e8a58f to cfb9da2Compare September 1, 2026 00:25

refactor(telemetry): simplify first-run notice to a single function
8254946

Hweinstock force-pushed the feat/telemetry-first-run-notice branch from cfb9da2 to 8254946Compare September 1, 2026 00:29

Hweinstock closed this Sep 1, 2026

Hweinstock commented Aug 31, 2026
View reviewed changes

Hweinstock commented Sep 1, 2026
View reviewed changes

Hweinstock added 3 commits September 1, 2026 00:24

feat(globalConfig): detect first run via persisted installationId
d92c666

feat(telemetry): notify users of telemetry collection on first run
e4213e7

refactor(globalConfig): persist installationId at root on first run
e37e4d7

Hweinstock force-pushed the feat/telemetry-first-run-notice branch from 1e8a58f to cfb9da2Compare September 1, 2026 00:25

refactor(telemetry): simplify first-run notice to a single function
8254946

Hweinstock force-pushed the feat/telemetry-first-run-notice branch from cfb9da2 to 8254946Compare September 1, 2026 00:29

Hweinstock closed this Sep 1, 2026

Hweinstock commented Aug 31, 2026
View reviewed changes

Hweinstock commented Sep 1, 2026
View reviewed changes

Hweinstock added 3 commits September 1, 2026 00:24

feat(globalConfig): detect first run via persisted installationId
d92c666

feat(telemetry): notify users of telemetry collection on first run
e4213e7

refactor(globalConfig): persist installationId at root on first run
e37e4d7

Hweinstock force-pushed the feat/telemetry-first-run-notice branch from 1e8a58f to cfb9da2Compare September 1, 2026 00:25

refactor(telemetry): simplify first-run notice to a single function
8254946

Hweinstock force-pushed the feat/telemetry-first-run-notice branch from cfb9da2 to 8254946Compare September 1, 2026 00:29

Hweinstock closed this Sep 1, 2026

Hweinstock commented Aug 31, 2026
View reviewed changes

Hweinstock commented Sep 1, 2026
View reviewed changes

Hweinstock added 3 commits September 1, 2026 00:24

feat(globalConfig): detect first run via persisted installationId
d92c666

feat(telemetry): notify users of telemetry collection on first run
e4213e7

refactor(globalConfig): persist installationId at root on first run
e37e4d7

Hweinstock force-pushed the feat/telemetry-first-run-notice branch from 1e8a58f to cfb9da2Compare September 1, 2026 00:25

refactor(telemetry): simplify first-run notice to a single function
8254946

Hweinstock force-pushed the feat/telemetry-first-run-notice branch from cfb9da2 to 8254946Compare September 1, 2026 00:29

Hweinstock closed this Sep 1, 2026

		@@ -0,0 +1,34 @@
		import { test, describe, expect } from "bun:test";

		@@ -0,0 +1,69 @@
		import { test, describe, beforeEach, afterEach, expect } from "bun:test";


		const configFileData = await this.readConfigFile();

		// capture first-run state before we populate an installationId below, so a

Conversation

Hweinstock commented Aug 31, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Spec

Implementation

Fallout from making the default id unset

Verification

Automated

Manual (end-to-end, isolated HOME)

How to reproduce

Uh oh!

Hweinstock left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

Hweinstock commented Aug 31, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Spec

Implementation

Fallout from making the default id unset

Verification

Automated

Manual (end-to-end, isolated HOME)

How to reproduce

Uh oh!

Hweinstock left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Hweinstock commented Aug 31, 2026•
edited
Loading

Manual (end-to-end, isolated `HOME`)

Hweinstock commented Aug 31, 2026•
edited
Loading

Manual (end-to-end, isolated `HOME`)

Hweinstock commented Aug 31, 2026•
edited
Loading

Manual (end-to-end, isolated `HOME`)