Skip to content

CLI: Update SDK to 9de3679 (v0.94.0) and restore the telemetry control/platform flags - #231

Open
kernel-internal[bot] wants to merge 15 commits into
mainfrom
cli-coverage-update
Open

CLI: Update SDK to 9de3679 (v0.94.0) and restore the telemetry control/platform flags#231
kernel-internal[bot] wants to merge 15 commits into
mainfrom
cli-coverage-update

Conversation

@kernel-internal

@kernel-internalkernel-internalBot commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

This PR updates the Go SDK to 9de3679a3880b1fff724377144c60e26e630f7b0 and restores the CLI flags for the telemetry surface that commit brings back.

SDK Update

  • Updated kernel-go-sdk to 9de3679a3880b1fff724377144c60e26e630f7b0 (tagged v0.94.0)

Coverage Analysis

This PR was generated by performing a full enumeration of SDK methods and CLI commands.

api.md lists 145 methods, up from 140 at the previous pin. All five additions are the new SiteConfigs resource (Get, List, ListRecommendations, Lookup, Resolve), and every one carries x-cli-skip: true in openapi.yaml — so none needs a CLI command. The other 140 methods are unchanged and all resolve to existing CLI call sites.

A field-level diff of every *Params and *Param struct between 26309b6 and 9de3679 found additions in exactly two places:

  • the skipped SiteConfig*Params / LookupRequestParam / ResolveRequestParam structs, and
  • the telemetry structs restored below.

The remaining SDK changes are doc-comment rewraps plus new response-only telemetry event types (cdp_command, page_crashed, platform_api_call), which need no flags because telemetry events --types filters on free-form strings.

Restored Flags

The 9de3679 merge brings back the control/platform telemetry split that the previous pin had dropped, and BrowserTelemetryCategoriesConfigParam.Control changed type from BrowserTelemetryCategoryConfigParam to BrowserTelemetryControlConfigParam, which broke the build. This reverts the code changes in 8b5a06b:

  • --telemetry accepts ten categories again — platform is valid — for BrowserTelemetryCategoriesConfigParam.Platform
  • --telemetry-cdp-exclude is back on all eight commands (browsers create/update, browser-pools create/update/acquire, auth connections create/update/login) for BrowserTelemetryCdpControlConfigParam.ExcludedMethods

The CLI's 38-entry CDP method list was diffed against the SDK's BrowserCdpCommandMethod enum at 9de3679 and is identical.

Testing

Tested against the production API:

  • browsers create --telemetry=console,control,platform --telemetry-cdp-exclude=Input.dispatchMouseEvent,Page.captureScreenshot — the response echoes platform.enabled and both excluded methods
  • browsers get --output json (telemetry block round-trips) / update --telemetry=network --telemetry-cdp-exclude=none (clears the list) / delete
  • browsers telemetry events showed a real platform_api_call event, and --categories platform filtered to it
  • browser-pools create --telemetry=console,control,platform --telemetry-cdp-exclude=Page.navigate / get (details row renders excluding CDP methods: Page.navigate) / update --telemetry-cdp-exclude=none / delete
  • auth connections create --telemetry=console,control,platform --telemetry-cdp-exclude=Page.navigate / update --telemetry=network / delete
  • validation: --telemetry=bogus lists all ten categories, --telemetry=off with --telemetry-cdp-exclude is rejected, an unknown CDP method lists the 38 valid ones, and --telemetry-cdp-exclude without --telemetry is rejected on auth connections update
  • read-only sweep across auth context, browsers/browser-pools/auth-connections/app/proxies/profiles/extensions/credentials/projects/api-keys/credential-providers lists, org entitlements, org limits, telemetry destinations, and audit-logs search
  • go build ./..., go vet ./..., go test ./... all pass

Triggered by: kernel/kernel-go-sdk@9de3679
Reviewer: @stainless-app[bot]


Note

Medium Risk
Changes canonical auth submission binding and telemetry request shaping across browsers, pools, and auth connections; mistakes could cause rejected submits or unintended telemetry config replacement on update.

Overview
Bumps kernel-go-sdk to v0.94.0 and wires new API surfaces into the CLI.

Managed auth submit now supports --interaction-id for canonical --field-value / --choice-id submissions. If omitted, the CLI fetches the connection and sends the current interaction ID; explicit IDs pin or detect stale flows. get, follow, and field formatting show interaction ID and field reason (replacing the old replace-existing hint).

Telemetry gains --telemetry-cdp-exclude on browser create/update, browser-pool create/update/acquire, and auth connection create/update/login. Exclusions merge into control telemetry’s CDP command stream (none clears the list). platform is a selectable --telemetry category; summaries and pool details show excluded CDP methods when set.

README documents the new submit flag; tests cover interaction resolution, validation, and CDP exclude parsing.

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

Bump github.com/kernel/kernel-go-sdk to
v0.91.1-0.20260817203807-0a287359dcc5 (0a28735).
Coverage gap found by enumerating all 140 methods in the SDK's api.md
against the CLI command tree: the new Organization.Entitlements resource
had no CLI surface. Everything else was already covered.
New command:
- `kernel org entitlements get` for client.Organization.Entitlements.Get
(GET /org/entitlements). Renders Plan, Features, and Limits sections;
supports --output json.
Null constraint values mean unlimited in this API, and the SDK models
them as non-pointer int64, so rendering keys off respjson field validity
rather than the zero value.
Tested against the real API:
- kernel org entitlements get (table output, ENTERPRISE plan)
- kernel org entitlements get --output json
- kernel org entitlements get --output yaml (rejected as expected)
- go build ./... and go test ./... pass, including 5 new unit tests
covering populated constraints, null-as-unlimited, null plan fields,
invalid --output, and API errors.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@socket-security

socket-securityBot commented Aug 17, 2026

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

DiffPackageSupply Chain
Security
VulnerabilityQualityMaintenanceLicense
Updatedgolang/​github.com/​kernel/​kernel-go-sdk@​v0.92.0 ⏵ v0.94.073+1100100100100

View full report

Updates github.com/kernel/kernel-go-sdk from
v0.91.1-0.20260817203807-0a287359dcc5 to v0.92.0.
## Coverage Analysis
Diffing the two module sources shows the SDK API surface is byte-identical
between these versions -- the only changes are release metadata
(.release-please-manifest.json, CHANGELOG.md, README.md, internal/version.go).
A full enumeration was still performed:
- All 140 SDK methods in api.md have corresponding CLI commands.
- The 4 x-cli-skip endpoints (/site-configs/lookup, /site-configs/resolve,
/site-configs/analyses/{id}, /auth/connections/{id}/exchange) are absent
from the SDK surface, so nothing to skip.
- All params struct fields are covered by CLI flags except three, each
intentional:
- AuthConnectionLoginParams.BrowserTelemetry -- deprecated in favor of
browser.telemetry, which the CLI already uses via ManagedAuthBrowserConfigParam.
- AuditLogListParams.PageToken -- opaque cursor handled internally by
ListAutoPaging; CLI exposes --limit instead.
- BrowserCurlParams.TimeoutMs / ResponseEncoding -- `browsers curl` is
implemented against browsers.HTTPClient rather than the SDK curl endpoint;
--max-time covers the timeout and raw bytes are streamed, so response
encoding is not applicable.
No coverage gaps found; no new commands or flags added.
## Tested
- go build ./... and go vet ./... clean
- go test ./... all packages pass
- Smoke tested rebuilt binary against the live API: `kernel browsers list`
Triggered by: kernel/kernel-go-sdk@a156820
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@kernel-internalkernel-internalBot changed the title CLI: Update SDK to 0a28735 and add new commands/flagsCLI: Update Go SDK to a1568205c576686eeafc634fff0ea72b75c28c0eAug 17, 2026
kernel-internalBotand others added 2 commits August 18, 2026 21:08
Bumps kernel-go-sdk to 6e62bf5b91e5d315b90b6c9c7296e09e312fb338.
That SDK release reshapes the canonical managed-auth input field: the
boolean `replace_existing` is gone and a `reason` enum ("missing" |
"rejected") takes its place, so `auth connections get` and the
`auth connections follow` event stream now render `reason=<why>` instead
of the `replace-existing` marker. A rejected credential is still visible,
now alongside the missing-value case it could not previously express.
A full enumeration of api.md against the CLI's service interfaces and
flags found no other coverage gaps: all 136 non-x-cli-skip SDK methods
have commands, and every params field maps to an existing flag.
Tested: auth connections list, auth connections get <id> (table + json),
browsers create -t 60, browsers get <id>, browsers delete <id> against
the live API; go build ./... and go test ./cmd/... pass.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@kernel-internalkernel-internalBot changed the title CLI: Update Go SDK to a1568205c576686eeafc634fff0ea72b75c28c0eCLI: Update Go SDK to 6e62bf5b91e5d315b90b6c9c7296e09e312fb338Aug 18, 2026
kernel-internalBotand others added 2 commits August 19, 2026 18:53
Bumps kernel-go-sdk to 796d4245c87a39acbb0d408b05f0de830c500772.
That SDK release adds `interaction_id` to managed auth state and to the
submit request. The API requires it for canonical submissions
(field_values / selected_choice_id) and rejects it when paired with a
legacy submit mode, so before this change every canonical `auth
connections submit` failed with "interaction_id is required for
canonical submissions".
`auth connections submit` gains --interaction-id. Left off, the CLI reads
the connection's current interaction ID, since the ID changes on every
actionable pause and the freshly read one is the only sane default;
passing it pins the submission so the API can reject it as stale. Legacy
submit modes never send one, and --interaction-id with a legacy mode is
rejected locally with the same rule the API enforces. `auth connections
get` and `follow` now show the interaction ID next to the canonical
fields and choices it scopes.
Also resolves the stale merge of main into this branch, which had left
two competing org entitlements implementations in cmd/org.go (the branch
built `org entitlements get`; main shipped `org entitlements` in #232) so
the package no longer compiled. Main's reviewed version wins.
A full enumeration of api.md against the CLI found no other gaps: all
136 non-x-cli-skip SDK methods have commands, and the only new params
field in this release is SubmitFieldsRequest.interaction_id.
Tested against the live API: created a managed auth connection, started
a login flow, and confirmed `get` (table + JSON) and `follow` render the
interaction ID at AWAITING_INPUT; canonical submit with and without
--interaction-id now clears the API's interaction validation (it stops
at this org's submit-v2 feature gate, while the same request sent
without interaction_id still returns "interaction_id is required");
legacy `--field` submit still accepted; `--interaction-id` with `--field`
rejected locally; org entitlements, browsers create/get/delete pass.
go build ./..., go vet ./... and go test ./... pass.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@kernel-internalkernel-internalBot changed the title CLI: Update Go SDK to 6e62bf5b91e5d315b90b6c9c7296e09e312fb338CLI: Update SDK to 796d4245c87a39acbb0d408b05f0de830c500772 and add new commands/flagsAug 19, 2026
Bumps kernel-go-sdk to v0.92.1-0.20260819203102-467fea72ee93, which adds
the proxy_error browser telemetry event (BrowserProxyErrorEvent) to the
telemetry event union.
No CLI coverage gaps: a full enumeration of all 137 SDK methods in api.md
found a corresponding CLI command for each, and the new event type needs
no code change because the telemetry commands render category/type
generically and accept --types values without a fixed allowlist.
Tested: go build ./..., go vet ./..., go test ./... (all pass);
browsers create --telemetry all, browsers curl, browsers telemetry events
(table, --output json, --categories network --all, --types proxy_error),
browsers telemetry stream --categories network --types proxy_error,
browsers delete — all against the live API.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@kernel-internalkernel-internalBot changed the title CLI: Update SDK to 796d4245c87a39acbb0d408b05f0de830c500772 and add new commands/flagsCLI: Update Go SDK to 467fea72ee93a0d8e4a520169cf5e14e5d4076eeAug 19, 2026
Bumps github.com/kernel/kernel-go-sdk to
08023260493e4584c4d87638849ab4491b34ec49 (v0.93.0).
The 0.93.0 release only changed version/changelog metadata relative to
the SDK revision the CLI was already pinned to (467fea7); api.md and all
generated Go sources are byte-identical, so there are no new methods,
params, or fields to expose.
Coverage analysis: full enumeration of all 140 SDK methods in api.md
against the CLI command tree found no gaps. Every method has a command,
and every param struct field is reachable via a flag, a positional arg,
or a derived value.
Tested: go build ./..., go vet ./..., go test ./... (all pass), plus live
API smoke tests for browsers list/create/get/delete, browsers telemetry
events, auth connections list, profiles list, telemetry destinations list.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@kernel-internalkernel-internalBot changed the title CLI: Update Go SDK to 467fea72ee93a0d8e4a520169cf5e14e5d4076eeCLI: Update Go SDK to 08023260493e4584c4d87638849ab4491b34ec49Aug 20, 2026
…m split
Updates kernel-go-sdk to 9a36566d8999ca346a9eeccede0cbf88d651b93f, which mirrors
the control/platform telemetry split into the public API. BrowserTelemetryCategories
gains a `platform` category and `control` becomes its own config type carrying
`cdp.excluded_methods`, so the previous `p.Control = on()` no longer compiled.
New coverage:
- `--telemetry=platform` is now a settable category on browsers create/update,
browser-pools create/update/acquire, and auth connections create/update/login,
and is reported by the telemetry summaries and details tables.
- `--telemetry-cdp-exclude` (new flag, same eight commands) sets
BrowserTelemetryCdpControlConfigParam.ExcludedMethods. Values are the 38 CDP
methods the proxy reports, matched case-insensitively and canonicalized;
`--telemetry-cdp-exclude=none` sends an empty list to report every method again.
Combining it with `--telemetry=off` is rejected, and on auth connection
update/login it requires `--telemetry` in the same command, since a connection
stores its browser config as sent and exclusions alone would drop its category
selection.
- Excluded methods are surfaced in the create/update telemetry summary, the
browser-pool details table, and the auth connection details table.
A full enumeration of the 140 methods in api.md against the CLI command tree found
no missing commands. The x-cli-skip endpoints (site-configs, auth connection
exchange) remain excluded.
Tested against the live API: browsers create/update/delete with
--telemetry=control,platform --telemetry-cdp-exclude (set, replace, and =none
clear); browser-pools create/get/update/acquire/delete; auth connections
create/get/update/delete; browsers telemetry events --categories platform; and the
unknown-method, --telemetry=off, and missing---telemetry error paths.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@kernel-internalkernel-internalBot changed the title CLI: Update Go SDK to 08023260493e4584c4d87638849ab4491b34ec49CLI: Update SDK to 9a36566 and add new commands/flagsAug 21, 2026
Comment threadcmd/browsers_telemetry.go
… split
Updates kernel-go-sdk to c0428370612f0ae242d9c4cbbf87e6a6436ff9d9.
The previous update (f9b126f) targeted SDK commit 9a36566d8999, which is not
reachable from the SDK's main branch — that telemetry control/platform split
never landed. Against c042837 the CLI no longer compiled:
BrowserTelemetryControlConfigParam, BrowserCdpCommandMethod, the `platform`
category, and `control.cdp` do not exist. This reverts f9b126f's code changes,
so the CLI is back to the nine categories the SDK actually ships (captcha,
connection, console, control, interaction, network, page, screenshot, system)
and the `--telemetry-cdp-exclude` flag is gone.
The only API-surface change between the CLI's previous SDK and c042837 is
browser_routing.go adding "computer" and "playwright" to the direct-to-VM
routing allowlist — an internal default with no CLI-visible effect.
Coverage analysis: a full enumeration of the 140 methods in api.md against the
CLI command tree found no missing commands, and a field-by-field pass over
every Params struct found no missing flags. The x-cli-skip endpoints
(site-configs, auth connection exchange) remain excluded.
Tested against the production API:
- browsers create --telemetry=console,network / update --telemetry=page /
telemetry events / get / delete
- browser-pools create --telemetry=console / get / update --telemetry=network /
delete
- browsers create --telemetry-cdp-exclude now correctly rejects the removed flag
- read-only sweep: auth context, auth connections list, browsers list,
browser-pools list, app list, proxies list, profiles list, extensions list,
org entitlements, telemetry destinations list, credentials list, projects list
- go build ./..., go vet ./..., go test ./... all pass
Triggered by: kernel/kernel-go-sdk@c042837
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@kernel-internalkernel-internalBot changed the title CLI: Update SDK to 9a36566 and add new commands/flagsCLI: Update Go SDK to c0428370612f0ae242d9c4cbbf87e6a6436ff9d9Aug 21, 2026
kernel-internalBotand others added 2 commits August 24, 2026 18:25
…orm split
Updates kernel-go-sdk to 5e48c587a312453969141e879b8e34d60cd1ab0f.
The supplied /tmp/sdk-diff.patch was empty: the SDK staging repo is a shallow
clone that no longer contains c0428370612f, so the diff could not be computed.
It was reconstructed by diffing the module cache copy of c042837 against the
new tree.
5e48c58 sits on top of 9a36566, so the control/platform telemetry split is back
in the SDK and the CLI stopped compiling on
BrowserTelemetryCategoriesConfigParam.Control. This reverts 063d7f5's code
changes, restoring f9b126f verbatim:
- `--telemetry=platform` is a settable category again on browsers create/update,
browser-pools create/update/acquire, and auth connections create/update/login,
and is reported by the telemetry summaries and details tables.
- `--telemetry-cdp-exclude` is back on those same eight commands, setting
BrowserTelemetryCdpControlConfigParam.ExcludedMethods. Its 38 accepted values
were re-verified field-by-field against the SDK's BrowserCdpCommandMethod enum
and match exactly. `=none` clears the list; combining it with `--telemetry=off`
is rejected, and auth connection update/login require `--telemetry` alongside it.
Coverage analysis: api.md now lists 145 methods, up from 140. The five additions
are the new SiteConfigs resource (Get, List, ListRecommendations, Lookup,
Resolve); all five carry x-cli-skip: true in openapi.yaml and stay out of the
CLI, as does the auth connection exchange endpoint. A leaf-by-leaf pass over the
other 140 found no missing commands, and a field-level diff of every Params
struct between the two SDK versions found no new flags beyond the telemetry ones
above (the remaining additions are LookupRequestParam/ResolveRequestParam and
SiteConfigList*Params, all skipped). Remaining SDK changes are comment-only or
internal: the browser_routing direct-to-VM allowlist drops "computer" and
"playwright", and BrowserNewParams.GPU documents a region=us-east requirement.
Tested against the production API:
- browsers create --telemetry=control,platform,console --telemetry-cdp-exclude
(mixed case input canonicalized to Input.dispatchMouseEvent,
Page.captureScreenshot), update replacing exclusions, update --telemetry-cdp-exclude=none
to clear, then delete
- browsers telemetry events --categories platform returns the new
platform_api_call events
- browser-pools create --telemetry=control,platform --telemetry-cdp-exclude /
get (details table shows the exclusions) / update / delete
- auth connections create --telemetry=control,platform --telemetry-cdp-exclude /
update / delete
- error paths: unknown CDP method, --telemetry=off with --telemetry-cdp-exclude,
unknown category (lists platform), and cdp-exclude without --telemetry on
auth connections update
- read-only sweep: auth context, auth connections list, browsers list,
browser-pools list, app list, proxies list, profiles list, extensions list,
org entitlements, telemetry destinations list, credentials list, projects list
- go build ./..., go vet ./..., go test ./... all pass
Triggered by: kernel/kernel-go-sdk@5e48c58
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@kernel-internalkernel-internalBot changed the title CLI: Update Go SDK to c0428370612f0ae242d9c4cbbf87e6a6436ff9d9CLI: Update SDK to 5e48c58 and add new commands/flagsAug 24, 2026
Comment threadcmd/browsers_telemetry.go
kernel-internalBotand others added 2 commits August 24, 2026 20:07
… split
Updates kernel-go-sdk to 26309b6ff244c7c729ed11101ada01757df34212.
The supplied /tmp/sdk-diff.patch was empty, so the diff was recomputed by
unshallowing the SDK clone. The result explains the churn: the CLI's previous
pin, 5e48c587a312, is not on the SDK's main branch — it lives on
origin/stlc/promotion-conflict, forked from 0802326. 26309b6 is on main, so
moving to it removes the SiteConfigs resource and the control/platform
telemetry split again, and the CLI stopped compiling on
BrowserTelemetryControlConfigParam, BrowserCdpCommandMethod, the `platform`
category, and `control.cdp`.
This is the same situation 063d7f5 handled, so it reverts 484e19f's code
changes, leaving cmd/ byte-identical to the 063d7f5 state (modulo the
unrelated MCP install work merged from main since):
- `--telemetry` is back to the nine categories the SDK actually ships
(captcha, connection, console, control, interaction, network, page,
screenshot, system); `platform` is rejected again.
- `--telemetry-cdp-exclude` is gone from all eight commands (browsers
create/update, browser-pools create/update/acquire, auth connections
create/update/login).
26309b6 is c042837 plus lib/browserrouting/route_cache.go and its tests
(stale-JWT eviction), so the public API surface is identical to c042837 and
nothing new needs CLI coverage.
Coverage analysis: api.md lists 140 methods, down from 145 — the five
removals are the SiteConfigs resource, which carried x-cli-skip: true in
openapi.yaml and was never in the CLI. All 140 remaining methods were checked
one by one against CLI call sites and every one is reachable; the nine that
looked unmatched at first (Deployments/Invocations/Auth.Connections.Follow,
Browsers.Logs.Stream, Browsers.Telemetry.Stream,
Browsers.Process.StdoutStream, Invocations.DeleteBrowsers/ListBrowsers,
Browsers.Curl) all resolve to *Streaming variants or, for curl, a deliberate
raw-HTTP-through-the-browser implementation. A field-level pass over all 100
Params structs reachable from api.md flagged only three candidates, all
non-gaps: AuditLogListParams.PageToken is handled by ListAutoPaging,
AuthConnectionLoginParams.BrowserTelemetry is the deprecated alias for the
browser.telemetry the CLI already sets, and BrowserCurlParams.TimeoutMs /
ResponseEncoding are unused because `browsers curl` streams raw bytes and maps
the timeout onto --max-time.
Tested against the production API:
- browsers create --telemetry=console,network,control / get /
update --telemetry=page / telemetry events / delete
- browser-pools create --telemetry=console,control / get (details table shows
the categories) / update --telemetry=network / delete
- auth connections create --telemetry=console,control / update
--telemetry=network / get / delete
- removed surfaces now rejected: --telemetry=platform lists only the nine
valid categories, and --telemetry-cdp-exclude is an unknown flag on both
browsers create and auth connections update
- read-only sweep: auth context, browsers list, browser-pools list, auth
connections list, app list, proxies list, profiles list, extensions list,
org entitlements, org limits get, telemetry destinations list, credentials
list, projects list, api-keys list, credential-providers list, audit-logs
search
- go build ./..., go vet ./..., go test ./... all pass
Triggered by: kernel/kernel-go-sdk@26309b6
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@kernel-internalkernel-internalBot changed the title CLI: Update SDK to 5e48c58 and add new commands/flagsCLI: Update Go SDK to 26309b6ff244c7c729ed11101ada01757df34212Aug 24, 2026
…trol/platform split
Updates kernel-go-sdk to 9de3679a3880b1fff724377144c60e26e630f7b0, which the
SDK tags v0.94.0.
The supplied /tmp/sdk-diff.patch was empty again, so the diff was recomputed
from the SDK clone. 9de3679 merges the release-please branch onto 26309b6, and
that merge brings back the surface the previous pin had dropped: the SiteConfigs
resource (140 -> 145 configured endpoints) and the control/platform telemetry
split. The CLI stopped compiling on BrowserTelemetryCategoriesConfigParam.Control,
whose type changed from BrowserTelemetryCategoryConfigParam to
BrowserTelemetryControlConfigParam.
This is the same flip 484e19f handled, so it reverts 8b5a06b's code changes,
leaving cmd/ byte-identical to the 484e19f state:
- `--telemetry` accepts ten categories again (captcha, connection, console,
control, interaction, network, page, platform, screenshot, system);
`platform` is valid.
- `--telemetry-cdp-exclude` is back on all eight commands (browsers
create/update, browser-pools create/update/acquire, auth connections
create/update/login), carrying control.cdp.excluded_methods.
The CLI's 38-entry cdpCommandMethods list was diffed against the SDK's
BrowserCdpCommandMethod enum at 9de3679 and is identical.
Coverage analysis: api.md lists 145 methods, up from 140. All five additions
are the SiteConfigs resource (Get, List, ListRecommendations, Lookup, Resolve),
and every one carries x-cli-skip: true in openapi.yaml, so none needs a CLI
command. The remaining 140 methods are unchanged from the previous pin and all
resolve to CLI call sites. A field-level diff of every Params and Param struct
between 26309b6 and 9de3679 found additions in only two places: the
SiteConfig*Params / LookupRequestParam / ResolveRequestParam structs (skipped
with their endpoints) and the telemetry structs restored here
(BrowserTelemetryCategoriesConfigParam.Platform,
BrowserTelemetryControlConfigParam.Enabled/Cdp,
BrowserTelemetryCdpControlConfigParam.ExcludedMethods). The remaining SDK
changes are doc-comment rewraps plus new response-only telemetry event types
(cdp_command, page_crashed, platform_api_call), which need no flags because
`telemetry events --types` filters on free-form strings.
Tested against the production API:
- browsers create --telemetry=console,control,platform
--telemetry-cdp-exclude=Input.dispatchMouseEvent,Page.captureScreenshot —
the response echoes platform.enabled and both excluded methods
- browsers get --output json (telemetry block round-trips) /
update --telemetry=network --telemetry-cdp-exclude=none (clears the list) /
delete
- browsers telemetry events showed a real platform_api_call event, and
--categories platform filtered to it
- browser-pools create --telemetry=console,control,platform
--telemetry-cdp-exclude=Page.navigate / get (details row renders "excluding
CDP methods: Page.navigate") / update --telemetry-cdp-exclude=none / delete
- auth connections create --telemetry=console,control,platform
--telemetry-cdp-exclude=Page.navigate / update --telemetry=network /
delete
- validation: --telemetry=bogus lists all ten categories, --telemetry=off with
--telemetry-cdp-exclude is rejected, an unknown CDP method lists the 38 valid
ones, and --telemetry-cdp-exclude without --telemetry is rejected on auth
connections update
- read-only sweep: auth context, browsers list, browser-pools list, auth
connections list, app list, proxies list, profiles list, extensions list,
org entitlements, org limits get, telemetry destinations list, credentials
list, projects list, api-keys list, credential-providers list, audit-logs
search
- go build ./..., go vet ./..., go test ./... all pass
Triggered by: kernel/kernel-go-sdk@9de3679
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@kernel-internalkernel-internalBot changed the title CLI: Update Go SDK to 26309b6ff244c7c729ed11101ada01757df34212CLI: Update SDK to 9de3679 (v0.94.0) and restore the telemetry control/platform flagsAug 24, 2026

@cursorcursorBot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit c6c402b. Configure here.

pterm.Info.Printf("Telemetry capturing: %s\n", strings.Join(on, ", "))
if ex := formatCdpExcludedMethods(cfg.Browser.Control.Cdp.ExcludedMethods); ex != "" {
pterm.Info.Printf("Telemetry excluding CDP methods: %s\n", ex)
}

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

CDP exclusions hidden when disabled

Low Severity

printTelemetrySummary and formatPoolTelemetry return as soon as no categories are enabled, so they never render Control.Cdp.ExcludedMethods. A create/update that only sets --telemetry-cdp-exclude is treated as fully disabled, unlike formatManagedAuthTelemetry, which still appends the exclusion list onto a disabled base.

Additional Locations (1)
Fix in CursorFix in Web

Reviewed by Cursor Bugbot for commit c6c402b. Configure here.

Sign up for freeto 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.

0 participants