CLI: Update SDK to 31c5fee384421d8c66f9c8bb5e5ef0c0ac7e194a and add vaults commands - #231
Open
kernel-internal[bot] wants to merge 32 commits into
Open
CLI: Update SDK to 31c5fee384421d8c66f9c8bb5e5ef0c0ac7e194a and add vaults commands#231kernel-internal[bot] wants to merge 32 commits into
kernel-internal[bot] wants to merge 32 commits into
Conversation
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>
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
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-internal
Bot
changed the title
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-internal
Bot
changed the title
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-internal
Bot
changed the title
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-internal
Bot
changed the title
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-internal
Bot
changed the title
…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-internal
Bot
changed the title
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
… 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-internal
Bot
changed the title
…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-internal
Bot
changed the title
… 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-internal
Bot
changed the title
…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-internal
Bot
changed the title
Updates kernel-go-sdk to v0.94.1-0.20260826181154-46978e2734f1. Full enumeration of api.md (145 SDK methods) against the CLI command tree found no missing commands or param fields. The only functional change in this SDK bump is a new `ap-southeast` value for the browser session and browser pool region enums. - Add "ap-southeast" to availableRegions(), which backs --region validation for `browsers list`, `browsers create`, `browser-pools list`, and `browser-pools create` - Update the flag help text and README for those four flags Tested against the live API: - browsers create --region ap-southeast -> browsers get (region reported as ap-southeast) -> browsers delete - browser-pools create --region ap-southeast -> browser-pools get (region ap-southeast) -> browser-pools delete - browsers list / browser-pools list --region ap-southeast return the new resources; --region eu-west correctly excludes them - browsers list --region bogus still rejected with the updated "us-east, eu-west, ap-southeast" message - go build ./... and go test ./cmd/... pass Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
kernel-internal
Bot
changed the title
Bumps github.com/kernel/kernel-go-sdk from v0.94.1-0.20260826181154-46978e2734f1 to v0.95.0. The SDK diff between the two versions touches only internal/version.go (release 0.95.0) -- no new methods, params, or fields. A full enumeration of all 152 SDK methods in api.md against every CLI leaf command confirmed no coverage gaps, and a field-level comparison of all 105 SDK *Params structs against CLI flags found no missing flags. Tested: go build ./..., go test ./cmd/... (all pass), kernel browsers list, kernel app list against the live API.
kernel-internal
Bot
changed the title
Bumps github.com/kernel/kernel-go-sdk to d348ffc2b54ec8bc313b09abb34184d8cfe5681c (v0.95.1-0.20260826235549). The only API change in this range renames SiteConfigs to ConfigRegistry and moves analysis get/list onto a ConfigRegistry.Analyses subresource. Every config-registry endpoint carries x-cli-skip: true in openapi.yaml, so no CLI coverage is needed. A full enumeration of the remaining 139 SDK methods and their param fields against the CLI found no other gaps. The merge that produced this branch left two conflicts half-resolved, both of which are fixed here: - auth_connections.go kept main's `ReplaceExisting: f.Reason == "rejected"` call sites against this branch's `Reason string` field, so the package did not compile. They now pass the reason through, matching the branch's formatter and its `reason=rejected` assertion. - browsers_telemetry.go listed "platform" in settableCategories but had no matching case in parseTelemetryCategories, so --telemetry=platform failed with an error naming platform as a valid value. Tested: go build ./... and go test ./... pass (previously the cmd package did not compile). Against the live API: `browsers create --telemetry platform` reports "Telemetry capturing: ... platform", and after an in-VM call `browsers telemetry events <id>` shows a platform/platform_api_call event. `auth connections list` verified; sessions cleaned up. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
kernel-internal
Bot
changed the title
Bumps github.com/kernel/kernel-go-sdk from v0.95.1-0.20260826235549-d348ffc2b54e to v0.96.0 (bb4371c). The upstream diff is release-only (CHANGELOG, README, internal/version.go, release-please manifest) with no API surface changes. Coverage analysis: full enumeration of all 145 SDK methods in api.md against the CLI command tree found no gaps. 5 ConfigRegistry methods are marked x-cli-skip in openapi.yaml and are excluded; the remaining 140 all have CLI commands. A recursive field-level sweep of all 100 param types (606 fields including nested structs) found no missing flags -- the only unreferenced fields are intentional: - AuditLogListParams.PageToken: handled internally by ListAutoPaging - AuthConnectionLoginParams.BrowserTelemetry/Proxy: deprecated in the SDK, superseded by browser.telemetry / browser.proxy, which are covered - BrowserCurlParams.TimeoutMs/ResponseEncoding: `browsers curl` goes through the browser HTTP proxy, where --max-time covers the timeout and binary responses are streamed natively - BrowserComputerBatchParams.Actions.SetCursor/Sleep: `computer batch` takes raw JSON via --actions, so all action types pass through Tested: go build ./..., go vet ./..., go test ./... (all pass); smoke tested against the live API with browsers list, profiles list (pagination footer), and a browsers create -> get -> delete round-trip. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
kernel-internal
Bot
changed the title
Bumps github.com/kernel/kernel-go-sdk from v0.96.0 to v0.96.1-0.20260828125604-6e498fbbc12d (6e498fb). The SDK change is response-type only: two new browser telemetry event variants (captcha_solve_started, captcha_challenge_result) plus a challenge_id field on captcha_solve_result. No new API methods and no new request params, so no new commands or flags are needed — the telemetry commands render event category/type generically and the --types filter is free-form, so the new event types flow through unchanged. A full enumeration of all 148 SDK methods in api.md against the CLI command tree found no coverage gaps. The only uncovered endpoints are the /config-registry routes, which are marked x-cli-skip: true in openapi.yaml. Param-field coverage was likewise checked across all 105 *Params structs. Tested: go test ./... passes; browsers create --telemetry=all, browsers telemetry events, browsers telemetry stream, browsers delete all verified against the live API. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
kernel-internal
Bot
changed the title
Bumps github.com/kernel/kernel-go-sdk to v0.96.1-0.20260831004050-94c784ab3169 (94c784ab). SDK change is response-side only: ManagedAuthCanReauthReason gains a totp_reauth_allowed value and requirements_satisfiable is redocumented. The CLI renders CanReauthReason as a raw string in `auth connections get`/`list`, so the new value flows through with no code change. Coverage analysis: full enumeration of all 145 methods in api.md against the CLI command tree found no gaps. Every method has a command (the six config-registry and auth exchange endpoints are x-cli-skip), and every field across the 104 params structs maps to a flag or positional arg. Tested: go build ./..., go vet ./..., go test ./... all pass; `kernel auth connections list` and `kernel auth connections get <id>` against the live API render Can Reauth / Can Reauth Reason correctly. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
kernel-internal
Bot
changed the title
Bumps github.com/kernel/kernel-go-sdk from
v0.96.1-0.20260831004050-94c784ab3169 to v0.97.0 (e9ee30b).
The SDK delta is a release-only bump (CHANGELOG, README, version.go,
release-please manifest); no API surface changed.
Coverage analysis: enumerated all 145 methods in the SDK api.md and the
full CLI command tree (153 commands). The only uncovered SDK methods are
the ConfigRegistry endpoints (/config-registry, /lookup, /resolve,
/analyses, /analyses/{id}), all marked x-cli-skip: true in openapi.yaml.
Param-field cross-check surfaced no missing flags.
Tested: go build ./..., go test ./... (all pass), and smoke-tested
`kernel browsers list` and `kernel profiles list` against the live API.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
kernel-internal
Bot
changed the title
Updates github.com/kernel/kernel-go-sdk to
v0.97.1-0.20260902190118-ed434f757fca (ed434f7).
SDK changes covered:
- New resource client.Browsers.Webmcp -> `kernel browsers webmcp`
- `list-tools <id_or_name>` for client.Browsers.Webmcp.ListTools
- `invoke-tool <id_or_name>` for client.Browsers.Webmcp.InvokeTool
with --tool-ref, --input (JSON, '-' reads stdin), --timeout-sec
for InvokeRequestParam.{ToolRef,Input,TimeoutSec}
- All /browsers/{id_or_name} sub-resource routes now accept a browser
session name. Migrated the renamed path param field
(Params.ID -> Params.IDOrName) for replays stop/download, process
kill/status/stdin/stdout-stream/resize, and fs watch stop/events,
and synced the local service interface signatures to idOrName.
Coverage analysis: full enumeration of api.md against the CLI command
tree found no other gaps. ConfigRegistry endpoints are x-cli-skip.
Tested against the live API:
- browsers webmcp list-tools / invoke-tool: correct paths and flag
handling; the API returns 404 because /browsers/*/webmcp/* is not
deployed yet (verified identically via direct curl).
- browsers replays list/start/stop/download, browsers process
spawn/status/kill, browsers fs watch start/stop, browsers computer
get-mouse-position -- all pass, addressed by session name.
- go build ./... and go test ./... pass.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
kernel-internal
Bot
changed the title
| truncateURL(t.Source.PageURL, 40), | ||
| frame, | ||
| truncateURL(t.Description, 60), | ||
| }) |
There was a problem hiding this comment.
Byte-sliced table truncation
Low Severity
The new WebMCP tools table shortens Description (and URLs) with truncateURL, which slices by bytes via s[:maxLen]. A max length that lands inside a multi-byte UTF-8 character produces a garbled trailing sequence in the terminal table. This violates the project's rune-aware truncation rule for CLI table display strings.
Triggered by learned rule: Use rune-aware truncation for CLI table display strings
Reviewed by Cursor Bugbot for commit fc5ba82. Configure here.
The SDK diff from the CLI's previous pin (ed434f7) to d02140d is a release-only bump: .release-please-manifest.json, CHANGELOG.md, README.md and internal/version.go. No API surface changed. Full enumeration of api.md (147 methods) against the CLI command tree found no coverage gaps. The 5 /config-registry methods are marked x-cli-skip in openapi.yaml; the remaining 142 all have CLI commands, and every *Params field (including the nested *RequestParam structs and the ProxyNewParams config union variants) maps to an existing flag. Tested: go build ./..., go test ./... (all pass), and live API smoke tests of `browsers list`, `profiles list`, `app list`. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
kernel-internal
Bot
changed the title
… health Updates github.com/kernel/kernel-go-sdk to v0.98.1-0.20260903142348-7a377c78440a (7a377c7). The only SDK change since v0.98.0 is on the OtlpDestination response, which gained consecutive_failures, last_error, last_error_at and last_export_at. No new endpoints or request params, so a full enumeration of api.md against the command tree turned up no missing commands or flags. 'kernel telemetry destinations get/create/update' now print Delivery, Consecutive Failures, Last Export At, Last Error and Last Error At, and 'list' gained a Delivery column. Delivery keys off consecutive_failures alone, since last_error/last_error_at are retained after a later success and would otherwise read as a live failure. Tested against the live API: telemetry destinations create/get/list/delete, get -o json (health fields pass through), and a browser session created with --telemetry-export-otlp. The API reported consecutive_failures 0 with no health timestamps throughout, so the healthy and never-delivered paths are covered live and the failing and retained-error paths by unit tests. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
kernel-internal
Bot
changed the title
Update kernel-go-sdk to 31c5fee384421d8c66f9c8bb5e5ef0c0ac7e194a, which adds
the Vaults resource (11 endpoints) and links vaults to browser sessions.
New commands (kernel vaults):
- create, get, list, delete for client.Vaults.{Upsert,Get,List,Delete}
- items {create,get,list,update,delete,events,perform-operation} for
client.Vaults.Items.*
Vault item specs are discriminated unions spanning four provider variants, so
they are taken as JSON via --spec / --spec-file (matching the --chrome-policy
convention) rather than a flag per provider-conditional field.
New flags:
- browsers create --vault for BrowserNewParams.Vaults (repeatable, ID or name)
- browsers get now shows Vaults and Usage Status for the new response fields
vaults list uses the page-based pagination UX (--page/--per-page + footer).
Tested against the real API: vaults create/get/list/delete (incl. pagination
footer), items create for wallet(link), wallet(agentcard) and card(agentcard)
via both --spec and --spec-file -, items get (incl. --wait/--expand), list,
update (verified persisted), events (incl. --after/--wait), perform-operation,
delete; browsers create --vault by both name and ID, verified the Vaults row in
browsers get and Usage Status on a deleted session. All test resources cleaned
up. go build, go vet and go test ./... pass.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
kernel-internal
Bot
changed the title
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
There are 2 total unresolved issues (including 1 from previous review).
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Want higher recall? High effort reviews run extra passes and find more bugs. A team admin can switch effort levels in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 75eae00. Configure here.
|
|
||
| if in.Output == "json" { | ||
| return util.PrintPrettyJSONSlice(items) | ||
| } |
There was a problem hiding this comment.
Vaults list JSON omits pagination
Medium Severity
kernel vaults list --output json prints a bare array even though the command is page-based. After the client drops the extra lookahead item, scripted callers have no has_more or next-page cursor and cannot page past the first slice.
Triggered by learned rule: Paginated CLI JSON output must include pagination cursor
Reviewed by Cursor Bugbot for commit 75eae00. Configure here.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR updates the Go SDK to 31c5fee384421d8c66f9c8bb5e5ef0c0ac7e194a and adds CLI commands/flags for new SDK methods.
SDK Update
Coverage Analysis
This PR was generated by performing a full enumeration of SDK methods and CLI commands.
All 152 methods in
api.mdwere compared against the 155 existing CLI commands. The only gaps were the newVaultsresource and the newBrowserNewParams.Vaultsfield. Theclient.ConfigRegistry.*methods remain uncovered by design — those endpoints are markedx-cli-skip: trueinopenapi.yaml.New Commands
kernel vaults createforclient.Vaults.Upsert()kernel vaults getforclient.Vaults.Get()kernel vaults listforclient.Vaults.List()kernel vaults deleteforclient.Vaults.Delete()kernel vaults items createforclient.Vaults.Items.Upsert()kernel vaults items getforclient.Vaults.Items.Get()kernel vaults items listforclient.Vaults.Items.List()kernel vaults items updateforclient.Vaults.Items.Update()kernel vaults items deleteforclient.Vaults.Items.Delete()kernel vaults items eventsforclient.Vaults.Items.Events()kernel vaults items perform-operationforclient.Vaults.Items.PerformOperation()New Flags
--vaultonkernel browsers createforBrowserNewParams.Vaults(repeatable, accepts vault ID or name)--nameonkernel vaults createforVaultUpsertParams.Name--page/--per-pageonkernel vaults listforVaultListParams.{Limit,Offset}--wait,--expandonkernel vaults items getforVaultItemGetParams.{Wait,Expand}--after,--waitonkernel vaults items eventsforVaultItemEventsParams.{After,Wait}--typeonkernel vaults items perform-operationforVaultItemPerformOperationParams.Type--type,--spec,--spec-fileonkernel vaults items createforVaultItemUpsertParams.{OfWallet,OfCard}.Spec--spec,--spec-fileonkernel vaults items updateforVaultItemUpdateParams.SpecOn
--specCardVaultItemSpecUnionParamandWalletVaultItemSpecUnionParamare discriminated unions spanning four provider variants (wallet/card × link/agentcard) with ~25 provider-conditional fields between them. Rather than a flag per field with validity depending onprovider, the specs are taken as JSON via--spec/--spec-file(-reads stdin), following the existing--chrome-policy/--chrome-policy-fileconvention. The SDK's registered union discriminators unmarshal these directly, so all four variants are reachable.kernel vaults listuses the page-based pagination UX (--page/--per-pageplus the+1has-more trick and footer), matchingkernel profiles list.Two new response fields are also surfaced in
kernel browsers get:Vaults(linked vaults) andUsage Status(shown only for deleted sessions).Testing
Smoke tested against the real API; all test resources were cleaned up afterwards.
vaults create/get/list(pagination footer) /deletevaults items createfor all three reachable variants — wallet+link, wallet+agentcard (via--spec-file -on stdin), and card+agentcardvaults items getincluding--waitand--expand payment_methodsvaults items list,events(including--afterand--wait)vaults items update— verified the change persisted (amount 1250 → 4200)vaults items perform-operation,vaults items deletebrowsers create --vaultby both name and ID; verified theVaultsrow inbrowsers get, andUsage Status: readyon a deleted session--type, malformed--specJSON, missing spec, and--spec/--spec-filemutual exclusiongo build ./...,go vet ./...andgo test ./...all pass.Triggered by: kernel/kernel-go-sdk@31c5fee
Reviewer: @kernel-internal[bot]
🤖 Generated with Claude Code