Skip to content

Fix --telemetry help text to match update merge semantics#183

Merged
Sayan- merged 2 commits into
mainfrom
sayan/fix-cli-telemetry-help
Jun 10, 2026
Merged

Fix --telemetry help text to match update merge semantics#183
Sayan- merged 2 commits into
mainfrom
sayan/fix-cli-telemetry-help

Conversation

@Sayan-

@Sayan- Sayan- commented Jun 10, 2026

Copy link
Copy Markdown
Contributor

Summary

The telemetry CLI help and README still described the old/incorrect contract. A per-category telemetry update merges into the session's current selection (only categories you name change); only --telemetry=all/off reset the whole config.

Docs-only/help-text; no behavior change.

Test plan

CI


Note

Low Risk
Documentation and CLI flag help text only; no code paths or API behavior changed.

Overview
Docs-only alignment for browser telemetry on browsers update and in the README—no runtime changes.

The --telemetry flag help on kernel browsers update now states that --telemetry=all resets to the default set, --telemetry=off disables, and comma-separated categories merge into the current selection (instead of replacing the whole config).

The README Browser Telemetry section is updated the same way: clearer examples for default/on/off and per-category capture, plus an expanded --categories list for telemetry stream (control, connection, screenshot, captcha, monitor, etc.).

Reviewed by Cursor Bugbot for commit e66b2f7. Bugbot is set up for automated code reviews on this repo. Configure here.

A per-category telemetry update merges into the session's current
selection rather than replacing it; only --telemetry=all/off reset the
whole config. The update flag help said "replaces current selection"
and "capture exactly those categories", which is wrong for the merge
path. Also refresh the README's telemetry section, which still showed
the removed name=on/off grammar, an "all categories" label for the
default set, and the old --categories list.

Co-authored-by: Cursor <cursoragent@cursor.com>
@firetiger-agent

Copy link
Copy Markdown

Firetiger deploy monitoring skipped

This PR didn't match the auto-monitor filter configured on your GitHub connection:

PRs in the kernel, infra, hypeman, and hypeship repos. kernel is a ~mono repo with many logical services underneath, ensure to focus on the implicated service for the PR

Reason: PR appears to be documentation/help text only with no behavior changes; unclear which service in the kernel mono-repo is implicated, please clarify the affected service or opt in manually if deploy monitoring is needed.

To monitor this PR anyway, reply with @firetiger monitor this.

@Sayan- Sayan- requested a review from archandatta June 10, 2026 17:22

@archandatta archandatta left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

lgtm

@Sayan- Sayan- merged commit 7b35b0e into main Jun 10, 2026
7 checks passed
@Sayan- Sayan- deleted the sayan/fix-cli-telemetry-help branch June 10, 2026 18:27
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