CLI: Update SDK to e746d9980b83f915e8e9d85a75dfee8f16b8df96 and add new commands/flags by kernel-internal[bot] · Pull Request #264 · kernel/cli

kernel-internal · 2026-09-18T23:36:31Z

This PR updates the Go SDK to e746d9980b83f915e8e9d85a75dfee8f16b8df96 and adds CLI commands/flags for new SDK methods.

SDK Update

Updated kernel-go-sdk to e746d9980b83f915e8e9d85a75dfee8f16b8df96 ("Handle AgentCard autopilot and declare checkout_origin on the card spec"). The only change is in vaultitem.go: CardVaultItemSpecAgentcardParam.CheckoutOrigin (request) and CheckoutOrigin on the card spec response types. api.md has no changes. Note: e746d99 is the staging commit after e7afbaf. Its API matches v0.115.0 plus checkout_origin (api.md, search.go and searchcontent.go are byte-identical to v0.115.0). Its pseudo-version v0.114.1-0.20260930182635-e746d9980b83 sorts below v0.115.0, so go get reports a "downgrade" even though the API is newer.
Previously bumped to c393858a0e762bac87313c1096a5af22896c85ce (v0.115.0). This is a release-only bump: since e7afbaf, only the changelog, README and version constant changed. api.md and all Params types are the same, so no new commands or flags are needed.
Previously bumped to e7afbafa4eb45cec605435f03168751f361b21fa. Deferred search content retrieval now ships: client.Search.Contents.Fetch returns a Response (contents, search_id, usage, warnings) instead of nothing, and the doc comments for source, max_age_hours, and browser describe the retained-content and temporary-browser behavior. api.md has no other changes.
Previously bumped to b307cc10fdfab032069c951663312e04d0203b5b (v0.114.0). This is a release-only bump: since c823c6c only the version constant and changelog changed, and api.md and all Params types are the same. No new commands or flags are needed.
Previously bumped to c823c6c04c73498e266e0955790a81d187986b4f. This adds publishable_key to Link vault provider configs: VaultProviderConfigNewParamsBodyLinkCredentials.PublishableKey, VaultProviderConfigUpdateParamsCredentials.PublishableKey, and the response field VaultProviderConfigLink.PublishableKey. api.md has no new methods.
Previously bumped to 6923472efed1a4e7f9d6f26124c3cbd381122812 ("Let Vaults fill credentials from 1Password"). api.md has no new methods, but vault items changed:
- The credential create spec is now a provider union: CredentialVaultItemSpecInputUnionParam with OfKernel (KernelCredentialVaultItemSpecInputParam, which requires provider: "kernel") and Of1password. The old CredentialVaultItemSpecInputParam was removed, so the CLI didn't compile.
- New credential_account item type (VaultItemUpsertParams.OfCredentialAccount), for connecting a 1Password account.
- New client.Vaults.Items.PerformOperation variants: 1pw_create_access_request, 1pw_access_request_status, 1pw_fill, 1pw_recover, 1pw_update_access_token.
Previously bumped to 35a02850ff6eac17ed5279dbdf54642e61d315b9. kernel auth connections get shows a Health Check Unavailable row when ManagedAuth.HealthCheckUnavailableReason is set.
Previously bumped to a1d4c5be424cb7211be912fb1a9a4cf9ec9f06fc. Only doc comments changed: telemetry.storage.enabled=false is now accepted when an OTLP destination is set (export-only telemetry for BAA orgs), and can't be changed after the browser is created. api.md and the Params fields are unchanged.
Previously bumped to 233b08772b836be24a9851d88122c39b1ed2c365. This adds telemetry.storage ({enabled}) to the telemetry config on BrowserNewParams, BrowserUpdateParams, BrowserPool{New,Update,Acquire}Params, and the managed-auth create/update/login browser config. It also adds a response-only field, BrowserTelemetryConfig.Storage. api.md has no new methods.
Previously bumped to 2e3561ade9f55969b59a50bcc7992d0121424272 (v0.113.0). This is a release-only bump: since 8dcb671 only the version constant changed, and api.md and all Params types are the same. No new commands or flags are needed.
Previously bumped to 8dcb671597fca5260a3f51847934e9c51b16d8fa, which adds 16GiB memory support for browser pools (BrowserPoolNewParams.Memory, BrowserPoolUpdateParams.Memory, and the response field BrowserPoolConfig.Memory). api.md is unchanged, so there are no new methods.
Previously bumped to 140c57d4e9906743e96c814f8785ac35d65d46c5. The only change since v0.112.0 is a doc comment on SearchProviderListParams.Slug, so this bump needs no new commands or flags.
Previously bumped to 247bcf1fc700e7582f2986ecb1904e90ff2a27a9 (v0.112.0), a release-only bump.
Previously bumped to 47c13103242727ad8633062d359aee2ad7d6cb32 (adds client.Browsers.Webmcp.CustomTools.List/Add/Remove and BrowserWebmcpListToolsParams.ExcludeCustom, and changes Tool to use nested ToolMetadata with MCP-style annotation hints)
Previously bumped to ffc38db98feff227e904bd3c84e11cc715c010a8 (adds BrowserNetworkConfigParam.ProxyRoutes for per-destination proxy routing, plus a new destination_route_unavailable proxy error code in telemetry)
Previously bumped to 8e055e16e1db7872b2bb298901c760aba435030d (adds OrgEntitlementsFeatures.Search, a response-only field; no new methods or request params)
Previously bumped to b50814fd0cd8cff8a37e56b48142eef0b3653b7c (adds BrowserPoolAcquireParams.Profile to load a profile when acquiring from a pool)
Previously bumped to a9ee57caab330fac08e26e24896274baf2e64b43 (adds BrowserTelemetryEventsParams.Type)
Previously bumped to 0584ea1, 1ef7b7c, df8b441 (v0.111.0) and 0554699 (Search API v1)

Coverage Analysis

This PR was generated by performing a full enumeration of SDK methods and CLI commands. All 172 methods in api.md were checked against the CLI, along with every top-level Params field.

These methods have no CLI command, on purpose:

The six client.ConfigRegistry.* methods are marked x-cli-skip: true.
(Resolved in e7afbaf: client.Search.Contents.Fetch now has kernel search contents.)

These fields have no flag of their own but are covered another way:

AuditLogListParams.PageToken: the auto-pager handles it.
The deprecated AuthConnectionLoginParams.BrowserTelemetry/.Proxy: the CLI sets browser.* instead.
BrowserCurlParams.ResponseEncoding: the CLI's curl sends a raw HTTP request through the browser's client.
AuditLogExportChunkParams.Limit: kernel audit-logs download pages through every chunk with the cursor, so the chunk size isn't exposed.

The e7afbaf re-audit didn't find anything new. Everything it flagged is already explained in the notes: client.Browsers.Curl (the CLI's browsers curl goes through the browser's HTTP client on purpose), Telemetry.Export/.Storage on browser update and on pools, and pool ProxyRoutes (see the 140c57d and a1d4c5b notes).

New Flags / Output (e746d99)

AgentCard card specs are passed as raw --spec JSON on kernel vaults cards create/update, so checkout_origin (CardVaultItemSpecAgentcardParam.CheckoutOrigin) goes through without a new flag. The AgentCardCardSpec type in the --spec help now documents checkout_origin: an https origin with no path, used to match the cardholder's autopilot rules. If it's omitted, the checkout asks for approval, and an update that omits it removes it.
spec.checkout_origin is added to the vault item JSON output allowlist. Without this, -o json would have dropped it.
kernel vaults items get (and card create/update) show a Checkout origin row for AgentCard cards when it is set.

New Commands (e7afbaf)

kernel search contents <id> for client.Search.Contents.Fetch(). It prints the full JSON response, like the other search commands, and is not retried automatically, since browser retrieval is billed.

New Flags (e7afbaf)

--result-ids / --limit for FetchRequestParam.ResultIDs / .Limit. Exactly one is required; --limit accepts 1–100.
--timeout-ms for FetchRequestParam.TimeoutMs (1000–120000).
--content-source (auto|provider|browser), --content-format (markdown|text), --content-max-chars, --content-max-age-hours, --content-timeout-ms for FetchRequestContentParam.{Source,Format,MaxChars,MaxAgeHours,TimeoutMs}.
--content-browser-id, --content-browser-mode (curl|render) for FetchRequestContentBrowserParam.{BrowserID,Mode}.
README: the note saying deferred retrieval isn't available is replaced with docs for search contents, and the command is back in the command reference.

New Flags (c823c6c)

kernel vault-provider-configs create --publishable-key for VaultProviderConfigNewParamsBodyLinkCredentials.PublishableKey. It only works with --provider link; with agentcard the CLI rejects it before sending the request.
kernel vault-provider-configs update --publishable-key for VaultProviderConfigUpdateParamsCredentials.PublishableKey. It can be used by itself or together with --name/--credentials-file.
get, create, and update show a Publishable Key row when the key is set, and publishable_key is now in the JSON output. The key is a public Stripe pk_... value, so it's passed as a flag rather than through the secret credentials file.

Tested (c823c6c)

Against the real API: create --provider link --publishable-key pk_test_clismoke1, then get showed the Publishable Key row, update --publishable-key pk_test_clismoke2 -o json returned the new value, and delete -y cleaned up. create --provider agentcard --publishable-key failed on the client as expected.
Added unit tests in cmd/vault_provider_configs_test.go. go test ./cmd/ passes.

Changes (6923472)

kernel vaults credentials create now sends the spec as the Kernel variant. If the spec file has no provider, it defaults to "kernel", so existing spec files work unchanged. Any other provider is rejected on the client with credential spec provider must be kernel.

Coverage notes (6923472)

Not covered here, on purpose: the 1Password additions (spec provider: "1password", credential_account items, and the five 1pw_* operations). Open PR Add 1Password brokered credential vault commands #271 (hypeship/onepassword-credential-vault) already implements them, with agent guidance for the approval flow. Building a second version here would duplicate and conflict with it. The credentialSpecInput helper added here has the same name and signature as Add 1Password brokered credential vault commands #271's, so Add 1Password brokered credential vault commands #271 can replace it when it merges.

New Flags (a1d4c5b)

--telemetry-storage on|off for BrowserNewParams.Telemetry.Storage.Enabled on kernel browsers create.
--telemetry-storage on|off for ManagedAuthCreateRequest/ManagedAuthUpdateRequest/AuthConnectionLoginParams .Browser.Telemetry.Storage.Enabled on kernel auth connections create, update, and login.
off requires --telemetry-export-otlp <destination> in the same command. update and login also require --telemetry, for the same reason --telemetry-cdp-exclude does: the connection stores its browser config as sent. The README is updated.
The flag is not added to browsers update (storage is fixed once the browser exists) or to browser-pools (pools don't support export, so off would always be rejected).

New Output (233b087)

Browser create/update and pool/auth-connection telemetry summaries now print Telemetry storage: off (...) when the response reports storage off. Nothing is printed when storage is on or the field is missing (older browsers, and the API today).

Coverage notes (233b087)

(Superseded by a1d4c5b, which adds the flag.) There is no --telemetry-storage request flag. storage.enabled defaults to true, and the OpenAPI spec says "Setting false is not supported yet and is rejected", so there is no usable value to expose yet. The flag should be added when false is supported.

New Flags (8dcb671)

kernel browser-pools create --memory 8GiB|16GiB for BrowserPoolNewParams.Memory.
kernel browser-pools update --memory 8GiB|16GiB for BrowserPoolUpdateParams.Memory. This only affects newly warmed browsers; use --discard-all-idle to replace idle ones.
The browser-pools create/get/update table output now has a Memory row. The flag is validated with the same parseMemoryFlag helper that browsers create --memory uses. The README is updated.

New Commands (47c1310)

kernel browsers webmcp custom-tools list <id-or-name> for client.Browsers.Webmcp.CustomTools.List(). Shows a table of ID, namespace, name, kind, URL patterns, and read-only hint; supports -o json.
kernel browsers webmcp custom-tools add <id-or-name> --namespace <ns> (--source <js> | --source-file <path|->) [--force-overwrite-namespace] for client.Browsers.Webmcp.CustomTools.Add() (AddRequestParam.Namespace, .Source, .ForceOverwriteNamespace).
kernel browsers webmcp custom-tools remove <id-or-name> <tool-id> for client.Browsers.Webmcp.CustomTools.Remove().

New Flags (47c1310)

kernel browsers webmcp list --exclude-custom for BrowserWebmcpListToolsParams.ExcludeCustom.
webmcp list now reads the new nested tool metadata. The table gains a Source column (page or custom:<namespace>), and Read Only now comes from readOnlyHint.

New Flags (ffc38db)

kernel browsers create --proxy-route PROXY=HOST[,HOST...] for BrowserNetworkConfigParam.ProxyRoutes (Hosts, Proxy.ID/Proxy.Name). The flag is repeatable. PROXY is treated as an ID if it looks like a cuid and as a name otherwise, the same way --extension and --vault work. kernel browsers get shows a Proxy Routes row when routes are set. It is not added to browser-pools create/update because the SDK says routes are not supported on pools. Used with --pool-*, it is reported as a conflicting flag.
Fix: an empty network.private_hosts: [] is no longer sent when only routes are set. Sending it would have replaced the default private ranges.

New Output (8e055e1)

kernel org entitlements now shows a Search feature row for OrgEntitlementsFeatures.Search.Enabled. JSON output already includes it through the SDK type.

New Flags (b50814f)

kernel browser-pools acquire --profile-id / --profile-name / --save-changes for BrowserPoolAcquireParams.Profile (ID, Name, SaveChanges). The loaded profile appears in the acquire output. Per the SDK, a browser acquired with a profile is destroyed and replaced on release, even with --reuse.
kernel browsers create --pool-id/--pool-name now passes --profile-id, --profile-name and --save-changes through to the acquire, and no longer warns that they conflict with the pool's configuration. --telemetry-cdp-exclude was already passed through but still triggered that warning; it no longer does.
Validation: passing both profile flags, or --save-changes without a profile, is an error.

Earlier changes on this branch

kernel browsers telemetry events --types now maps to BrowserTelemetryEventsParams.Type (the server filters instead of the CLI).
kernel search, kernel search get, kernel search providers (from main, Add Search API CLI commands #266).
auth connections login --skill-mode, the timeline Completed column, and org limits concurrent-session usage.

Fixes (140c57d)

Merging main (Add browser proxy routes to CLI create #269, Update Go SDK to v0.112.0 and support custom WebMCP tools #270) had left two copies of the WebMCP custom-tools code, so the branch didn't compile. I kept main's browsers_webmcp.go and browsers_webmcp_test.go. The custom-tools commands now come from main's browsers_webmcp_custom_tools.go.
Removed the branch's duplicate --proxy-route registration on browsers create, which caused a "flag redefined" panic. Main's implementation from Add browser proxy routes to CLI create #269 stays, so the flag format is now main's HOST[,HOST...]=PROXY, not the PROXY=HOST format described in the ffc38db section below.
Removed an unused webmcpCustomTools field from BrowsersCmd.
browsers telemetry stream/events --categories help now lists platform.

Coverage notes (140c57d)

Telemetry.Export on BrowserUpdateParams and on BrowserPool{New,Update,Acquire}Params has no CLI flag. The OpenAPI spec says export is ignored on browser update and rejected by pools. A live check agreed: browsers update --telemetry-export-otlp off left the session exporting.
BrowserPool{New,Update}Params.Network.ProxyRoutes has no CLI flag. The spec says it is not supported on browser pools.

Fixes

Removed a duplicate rootCmd.AddCommand(searchCmd) left in cmd/root.go by the earlier merge from main.

Testing

e746d99: go build ./..., go vet ./cmd and go test ./... pass. New unit test: TestVaultCardAgentcardCheckoutOriginIsPublic. The cards create/update pass-through test now includes checkout_origin. Against the real API, using a throwaway card on a connected AgentCard wallet (no checkout was run, and the card was deleted afterward): vaults cards create --provider agentcard --spec '{...,"checkout_origin":"https://shop.example.com"}' returned it in spec, vaults items get showed the Checkout origin row and -o json included it, vaults cards update without it removed it from the spec, and vaults items delete --yes cleaned up.
c393858: go build ./..., go vet ./... and go test ./... pass. No live test was run because nothing new was added. The coverage re-check found every api.md method mapped to a CLI command, except the x-cli-skip config-registry endpoints.
e7afbaf, against the real API: search contents --limit 1 --content-source provider --content-max-chars 200 (returned a per-result unavailable outcome, as expected when no retained provider content exists); --result-ids <id> --content-source browser --content-browser-mode curl --content-format text --timeout-ms 60000 (ok, browser_curl); and --result-ids <id2>,<id1> --content-source auto --content-max-age-hours 0 --content-browser-id <browser> --content-browser-mode render --content-format markdown --content-max-chars 150 --content-timeout-ms 30000 (both ok, browser_render, truncated, order preserved; the temporary browser was deleted afterward). An unknown search ID returns a 404 error. New unit tests: TestSearchContents, plus the invalid-input and wiring cases. go test ./... passes.
b307cc1: go build ./... passes. No live test was run because nothing new was added.
6923472: go build ./..., go vet ./cmd and go test ./... pass. Two request-body assertions were updated for "provider":"kernel", and a new unit test, TestCredentialSpecInputProvider, was added. Against the real API, using a temporary vault that was deleted afterward: vaults credentials create (the response has spec.provider: kernel and pending_collection with a collect URL), credentials update --version 1 (goes to version 2 with the username value), items get (table shows Provider kernel), items list, and a provider: "1password" spec, which is rejected on the client.
a1d4c5b: go build ./..., go vet ./cmd and go test ./cmd pass. New unit test: TestResolveTelemetryStorageFlag. Against the real API, using a temporary OTLP destination, auth connection and profile that were all deleted afterward:
- browsers create --telemetry-storage off --telemetry-export-otlp <dest> -t 30 prints Telemetry storage: off, and browsers get -o json shows storage.enabled=false.
- auth connections create ... --telemetry-storage off --telemetry-export-otlp <dest>: the response has storage.enabled=false.
- auth connections update --telemetry all --telemetry-storage on: the response has storage.enabled=true.
- auth connections login --telemetry all --telemetry-storage off --telemetry-export-otlp <dest> succeeds.
- Client-side errors for off without a destination, an invalid value, and update --telemetry-storage without --telemetry.
233b087: go build ./..., go vet ./cmd and go test ./... pass. New unit tests cover the storage line in printTelemetrySummary. Against the real API: browsers create --telemetry=all -t 30, then browsers get -o json (the API doesn't return storage yet, so no storage line is printed), then browsers delete.
2e3561a: go build ./..., go vet ./cmd and go test ./... pass. No live test was run because nothing new was added.
8dcb671, against the real API with a temporary pool (deleted afterward): browser-pools create --size 1 --memory 16GiB, after which get shows Memory | 16GiB. Then browser-pools update --memory 8GiB --discard-all-idle, after which get shows 8GiB. --memory 4GiB is rejected on the client. go build ./..., go vet ./cmd and go test ./cmd pass.
140c57d: go build ./..., go vet ./cmd, go test ./... pass. Live smoke tests: browsers create/update/delete, browsers webmcp list, webmcp custom-tools list, browsers telemetry events --categories platform, telemetry destinations create/delete, and browsers create --telemetry-export-otlp, which exported to the destination.
47c1310, against the real API on a temporary browser (deleted afterward): custom-tools add from --source-file and from stdin, --force-overwrite-namespace (swapped in a new tool ID), and a duplicate add (returns 409 Conflict). Also custom-tools list (table and -o json); webmcp list with and without --exclude-custom after going to example.com (the custom tool shows as custom:clitest and is hidden with the flag); webmcp invoke of the custom tool (returned {"title":"Example Domain"}); and custom-tools remove (the list is empty afterward). New unit tests cover all three subcommands, --exclude-custom, and input validation. go test ./... passes.
ffc38db: browsers create --proxy-route by proxy name and by ID both reach the API, which returns feature_not_enabled: proxy routes are not enabled for the test org, so a successful route could not be checked end to end. Invalid values (bad, =host, proxy=) are rejected on the client. A plain browsers create/get/delete still leaves network unset. New unit test: TestBrowsersCreate_WithProxyRoutes.
8e055e1: kernel org entitlements shows Search | true against the real API; -o json includes features.search. The unit tests for the entitlement rows now cover Search.
Tested against the real API, using a temporary pool and profile that were deleted afterward:
browser-pools acquire <pool> --profile-name <p> --save-changes: the output shows the Profile and Profile Save Changes: true.
browsers create --pool-name <pool> --profile-id <id> -o json: the response includes the loaded profile.
The validation errors for both profile flags together, and for --save-changes alone.

go build ./..., go vet ./cmd and go test ./cmd pass. New unit tests cover buildAcquireProfileParam and acquiring with a profile.

Triggered by: kernel/kernel-go-sdk@e746d99
Reviewer: @kernel-internal[bot]

🤖 Generated with Claude Code

Note

Medium Risk
Broad CLI/API wiring across search (billable browser retrieval), vault credentials/checkout, auth telemetry, and payment prep paths; mostly additive flags with client validation and tests.

Overview
Updates kernel-go-sdk and wires new API surface into the CLI, with README aligned to match.

Search: Adds kernel search contents to fetch page content for retained search results (--limit or --result-ids, plus content/browser options). Search docs no longer say deferred retrieval is unavailable.

Telemetry: --telemetry-storage on|off on browsers create and auth connections create / update / login (export-only when off, with validation). Summaries call out when storage is off. Historical telemetry events sends --types to the server (not a client full scan) and documents the platform category.

Browser pools: --memory 8GiB|16GiB on create/update; acquire (and pool-based browsers create) accept --profile-id / --profile-name / --save-changes.

Managed auth: Login --skill-mode, Health Check Unavailable on get, timeline Completed column; org limits get shows live concurrent session usage when the API returns it.

Vaults: Link provider configs get --publishable-key; credential create specs use an ordered fields array with required name and optional label; Adyen in prepare_checkout; AgentCard cards support checkout_origin in --spec and JSON/table output.

Org: entitlements includes the Search feature row.

^{Reviewed by Cursor Bugbot for commit 29b2105. Configure here.}

Bumps the Go SDK from v0.105.1-0.20260916183112-dab5c0714192 to v0.107.0 (commit 6c9df7b). The SDK surface is unchanged across this range: the previously pinned pseudo-version already contained every feature commit in the 0.106.0 and 0.107.0 releases (persistent browser REPL, browser update start_url, config registry, AgentCard preparation contracts, Link spend request errors). Only release metadata differs, so no new commands or flags were required. Coverage analysis: full enumeration of all 165 SDK methods in api.md against the CLI command tree found no gaps. The six client.ConfigRegistry.* methods are marked x-cli-skip in openapi.yaml and are correctly excluded. Param fields without a dedicated flag were each verified as intentional: - AuditLog{List,ExportChunk}Params.SearchUserID -> covered by --user-id - AuditLogListParams.PageToken -> handled internally by ListAutoPaging - AuthConnectionLoginParams.BrowserTelemetry -> deprecated, superseded by browser.telemetry, which --telemetry covers - BrowserCurlParams.ResponseEncoding -> `browsers curl` streams raw bytes through its own HTTP client rather than the SDK method Tested: go build ./..., go vet ./..., go test ./... (all 9 packages pass), plus live API smoke tests of `browsers list`, `browsers create`, `browsers repl` (verified top-level bindings persist across calls under a stable REPL ID), `browsers update --start-url`, and `browsers delete`. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Updates github.com/kernel/kernel-go-sdk from v0.107.0 to v0.107.1-0.20260917184535-51d7fb82550d (commit 51d7fb8). The upstream commit ("chore(stlc): seal custom-code tracking files") contains no API surface changes -- the api.md/Go source diff between v0.107.0 and 51d7fb8 is empty. Coverage analysis: full enumeration of all 165 methods in api.md against the CLI command tree (215 commands). All 159 non-skipped methods have a corresponding CLI command; the 6 config-registry methods are marked x-cli-skip: true in openapi.yaml. All params struct fields map to existing flags, positional args, or are pagination internals handled by the auto-pagers. No new commands or flags were needed. Tested: go build ./..., go vet ./..., go test ./... (all pass), kernel browsers list, kernel profiles list against the live API. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Updates github.com/kernel/kernel-go-sdk from v0.107.1-0.20260917184535-51d7fb82550d to v0.108.0. The only difference between the two module versions is the internal/version.go version constant -- api.md and every public Go source file are byte-identical, so there are no new API methods, params, or fields to expose. Coverage analysis: full enumeration of all 165 SDK methods in api.md against all 176 CLI leaf commands found no gaps. 6 methods (ConfigRegistry.{List,Lookup,Resolve} and ConfigRegistry.Analyses.{Get,List,Cancel}) are marked x-cli-skip in openapi.yaml and are intentionally absent. The remaining 159 all have CLI commands. An automated SDK-param-field vs CLI-flag comparison surfaced only naming false positives (e.g. proxy -> --proxy-id/--proxy-name, tags -> --tag, timeout_seconds -> --timeout, hold_keys -> --hold-key) and fields exposed as positional args; all were verified covered. Tested: go build ./..., go vet ./... (clean), go test ./... (all pass), and smoke-tested `kernel browsers list` and `kernel app list` against the live API. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Updates kernel-go-sdk to 6367486e6e06cdc3d9dc13c107dddca490e9b9bc. That SDK change adds two response fields to OrgLimits: concurrent_sessions_used and concurrent_sessions_available. Surface both as rows in `kernel org limits get`. A null here means usage could not be read rather than "unlimited", so these render as "unknown" instead of reusing formatProjectLimitValue. A full enumeration of the 165 methods in api.md found no missing commands; the 6 config-registry methods are x-cli-skip. Param-field audit found no missing flags: AuditLogListParams.PageToken is consumed by the SDK auto-pager, AuthConnectionLoginParams.BrowserTelemetry is deprecated in favor of browser.telemetry (already wired), and BrowserCurlParams.ResponseEncoding does not apply because `browsers curl` streams raw bytes over the browser HTTP client rather than calling Browsers.Curl. Tested: `kernel org limits get` and `-o json` against the live API (1118 used + 882 available = 2000 max); full `go test ./...` passes. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Bumps kernel-go-sdk to 3038f83eb3f7cc6a59059a0a04bdb111300ea77c, which preserves credential field order: CredentialVaultItemSpec.Fields and CredentialVaultItemSpecInputParam.Fields changed from a map keyed by name to an ordered array, and each definition now carries a stable `name`. - vaults_output.go: project spec.fields as an array (name, type, required, sensitive) instead of a keyed object, and look definitions up by name when deciding which non-sensitive values stay visible. - vaults_credentials.go: document the ordered array and the name pattern, update the create example, note that update specs stay keyed by name, reject specs still using the object form with actionable guidance, and require every create field to carry a name. Error text never echoes values. - README.md: same shape and ordering guidance. - Tests: fixtures moved to the array shape; added coverage for field order reaching the API unchanged, the keyed-form error, and the missing-name error. A full enumeration of api.md against the CLI command tree found no missing commands. All config-registry and auth exchange endpoints are x-cli-skip. Tested against the live API: vaults credentials create with out-of-alphabetical field order (order preserved in the request and in get/list output), vaults items get/list, vaults credentials update (keyed form, non-sensitive text/email values still surfaced, sensitive omitted), vaults items invoke fill by field name, and both new validation errors. Test vault, item, and browser deleted. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Updates github.com/kernel/kernel-go-sdk to v0.108.1-0.20260917213155-5cfceddfb1ea (5cfcedd). The SDK change ("Accept opaque AgentCard vaulted card IDs") revises the card_id contract on CardVaultItemSpecAgentcard: the value is an opaque ID returned by AgentCard and must be passed through unchanged, without assuming a prefix or format. The `vaults cards create|update` help text still advertised a `vc_...` shape, so it is updated to match. The CLI already forwards card_id verbatim inside the --spec JSON (there is no --card-id flag), so no behavior change was needed; a regression test now pins that prefixed, unprefixed and punctuated IDs all round-trip unchanged. A full enumeration of all 165 SDK methods in api.md against the CLI command tree found no missing commands. The six client.ConfigRegistry.* methods are marked x-cli-skip in openapi.yaml and are intentionally absent. The AgentCard and Link card spec field sets in the help text were verified complete against the SDK param structs. No new params or fields were added by this SDK bump, so no new flags were required. Tested: go build ./..., go vet ./..., go test ./... (all pass); vaults cards create --help (help renders on one line); against production API: auth status, app list, vaults list, vaults items list agentcard-vault, vaults items get agentcard-vault. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Updates github.com/kernel/kernel-go-sdk from v0.108.1-0.20260917213155-5cfceddfb1ea to the v0.109.0 release (5c91a27). Coverage analysis: api.md is byte-identical across this bump, so no API methods, params or fields were added and no new commands or flags are required. The only source changes relative to the previously pinned pseudo-version are the release version stamp and a new ConfigRegistryAnalysisService.WaitForResult convenience helper. All six /config-registry endpoints are marked x-cli-skip in openapi.yaml, so that helper is intentionally out of CLI scope. A full enumeration of all 165 api.md methods against the CLI command tree found no gaps. The six methods that do not match cmd/ by name are covered through the SDK's *Streaming variants (Deployments.FollowStreaming, Invocations.FollowStreaming, Browsers.Logs.StreamStreaming, Browsers.Telemetry.StreamStreaming, Browsers.Fs.Watch.EventsStreaming, Browsers.Process.StdoutStreamStreaming). The OrgLimits concurrency fields and the opaque AgentCard card_id help text, both landed earlier on this branch, were re-verified against the release. Tested: go build ./..., go vet ./..., go test ./... (all pass); against the production API: org limits get (both concurrency fields render), vaults list, vaults cards create --help. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Bumps kernel-go-sdk from v0.109.0 to v0.109.1-0.20260918194421-c4dc2a28cd2b, which adds an optional `label` to CredentialVaultFieldDefinition and CredentialVaultFieldInputParam. `label` is non-secret display metadata for the hosted collection form. It already reached the API because credential specs are passed through from --spec-file, but the display-safe output projection dropped it: the spec.fields allowlist in printVaultItem only permitted name/type/required/ sensitive, so every read silently discarded a label the API returned. Add it to the allowlist and document it in the command help and README. A full enumeration of api.md (165 methods) against the CLI command tree (176 commands) found no missing commands. The six config-registry endpoints are marked x-cli-skip in openapi.yaml and remain unexposed; Invocations.Follow and Deployments.Follow are covered by the streaming paths in logs/invoke/deploy logs. Tested against the live API: vaults credentials create with labelled text and password fields round-trips `label` to the API and back, and vaults items get/list both render it. Verified the pre-fix binary stripped `label` from the same responses. Sensitive values stay omitted. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

The credential field `label` support landed here against the pre-release commit c4dc2a2 (pseudo-version v0.109.1-0.20260918194421-c4dc2a28cd2b). That change is now published as the tagged v0.110.0 release, so pin the release instead of the pseudo-version; the SDK source is identical. Also guards the credentials help text with a steering assertion so the `label` documentation is not silently dropped by a later edit. A full enumeration of all 165 api.md methods against the CLI command tree found no missing commands; the 6 config-registry methods are x-cli-skip. Tested against the live API: vaults credentials create with labelled text and password fields round-trips `label` through create, items get, and items list; the test vault was deleted afterwards. go build ./... and go test ./... pass. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Bumps kernel-go-sdk from v0.110.0 to v0.110.1-0.20260918232759-6e379e6df7b9. The only change is in browsertelemetry.go: the proxy_error event's code enum gains origin_response_incomplete, restricted_route_unavailable, and unknown, and BrowserProxyErrorEventData gains raw_code (the sanitized X-Kernel-Proxy-Error header, present only when code is unknown). No CLI change is needed for that field. Unlike the credential-label case, telemetry output has no display allowlist: `browsers telemetry events` and `telemetry stream` render the Seq/Time/Category/Type table from the event envelope and emit the event body verbatim under `-o json`, so raw_code and the new codes flow through on their own. A full enumeration of api.md (165 methods) against the CLI command tree (175 commands) found no missing commands or flags. The six config-registry endpoints are marked x-cli-skip in openapi.yaml and remain unexposed, as does POST /auth/connections/{id}/exchange, which the SDK does not surface; the other 159 methods all map to a command. No request param struct changed since v0.110.0, so no new flags. Also drops a stale assertion in TestCredentialHelpSteering. The branch and main both added credential field labels; main's wording of the help text won the merge, but the branch's assertion on its own earlier phrasing ("definitions accept name, label, required, sensitive") survived and failed. The neighboring assertion on "optional non-secret human-readable label" already covers the same guidance. Tested against the live API: browsers create --telemetry network,page; browsers curl; browsers telemetry events (table and -o json); browsers delete. Full go test ./... passes. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Bumps kernel-go-sdk to v0.110.1-0.20260921155736-dd9a4a4e3d3a, which adds AgentcardPreparedProcessorAdyen and reframes prepare_checkout from "tokenization" to general "checkout" preparation. - cmd/vaults_prepare_checkout.go: add adyen to vaultCheckoutProcessors so `checkout.psp: "adyen"` passes CLI validation instead of being rejected - cmd/vaults_commands.go, README.md: document adyen, its production/sandbox environment pairing, the fresh-card Sessions restriction (public dummy card fields, not vault aliases), and that device approval / browser Authorised responses are not capture or fulfillment evidence Full enumeration of api.md methods against CLI commands found no missing commands; the six /config-registry methods and auth/connections exchange are marked x-cli-skip in openapi.yaml. No new param fields in this SDK bump. Tested: `go build ./...` and `go test ./...` pass; against the live API, `vaults items invoke <vault> <item> prepare_checkout --params '{"checkout":{...,"psp":"adyen"}}'` now passes CLI validation and reaches the API, while `"psp":"stripe"` is still rejected with the updated processor list. Did not arm a real Adyen preparation, since preparations are single-use and would irreversibly consume a live AgentCard card. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Updates github.com/kernel/kernel-go-sdk to v0.110.1-0.20260921185747-68c51002947b (68c5100). The SDK delta from dd9a4a4 touches only authconnection.go: documentation rewording on ManagedAuth.CanReauth / CanReauthReason plus one new enum value, ManagedAuthCanReauthReasonOptimisticTotpAttempt ("optimistic_totp_attempt"). No new methods, resources, or param fields. The CLI renders CanReauthReason as an opaque string in both the auth connections list and get views, so the new value surfaces with no code change. Coverage analysis: full enumeration of all 165 methods in the SDK api.md against the 176 commands in the CLI command tree found no missing commands. The 6 ConfigRegistry methods are marked x-cli-skip in openapi.yaml and are correctly absent. Tested against the production API: - kernel status - kernel auth context - kernel auth connections list --limit 3 (table and -o json) - kernel auth connections get <id> (Can Reauth / Can Reauth Reason render) - go build ./..., go vet ./..., go test ./... all pass Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Updates kernel-go-sdk to v0.110.1-0.20260921192205-ca8d4655a0dc, which adds ManagedAuthTimelineEvent.CompletedAt: the stable timestamp for when a login/reauth attempt first reached a terminal status. Full enumeration of api.md methods against cmd/ found no missing commands or param flags. The only SDK change was this response field, so `kernel auth connections timeline` now renders a Completed column alongside Timestamp. It dashes out for in-progress attempts, health checks, and historical attempts with no recorded completion time. Tested: kernel auth connections timeline (table + --output json, with and without --type/--page/--per-page) against the staging API; unit test extended to cover a populated completed_at. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Updates kernel-go-sdk to aee0b02b9b0bdb2f84172ee9b568696dcd8fa482, which adds AuthConnectionLoginParams.SkillMode: a per-login control over whether the flow reads and writes learned domain skills. Automatic reauths inherit the selected mode, so exposing it on `kernel auth connections login` is the only way to opt a connection out of skill learning from the CLI. The value is validated locally against enabled/disabled so a typo fails before a login flow is started, and omitting the flag leaves the field unset so the API keeps its default of enabled. A full enumeration of api.md methods against the CLI's commands found no other gaps: every SDK method has a command except the config-registry and auth exchange endpoints marked x-cli-skip, and the only uncovered params fields are deprecated (login browser_telemetry), handled internally (audit log page_token via ListAutoPaging), or not applicable (curl response_encoding, since the CLI streams raw bytes through the browser HTTP client). Tested: auth connections login --skill-mode disabled, --skill-mode enabled, and an invalid value against the real API, plus unit tests for set/omitted/invalid. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Updates github.com/kernel/kernel-go-sdk to 05546992051b109e2a59e1b4a7f6f4455b1470db, which adds the Search API v1 providers, and covers all four new SDK methods with CLI commands. New commands: - `kernel search <query>` -> client.Search.New - `kernel search get <id>` -> client.Search.Get - `kernel search providers` -> client.Search.Providers.List - `kernel search contents <id>` -> client.Search.Contents.Fetch `kernel search` exposes every RequestParam field: --country, --language, --max-results, --recency, --safe-search, --start-date, --end-date, --include-domains, --exclude-domains, --strict-params, --include-raw and --timeout-ms, plus --content and the --content-* options for portable retrieval and --show-content for printing extracted text. The strategy union is driven by --provider (pinned), --fallback-providers (fallback) and --fallback-on, with provider-native options supplied as a JSON object keyed by provider slug via --provider-options. Provider targets are built by round-tripping through the SDK's discriminated union so every provider's typed options are reachable without a flag per provider. A full enumeration of api.md against the CLI found no other gaps: the only other uncovered methods are the six client.ConfigRegistry.* methods, which are marked x-cli-skip in openapi.yaml. Tested: search is disabled for the test organization, so the four commands were exercised end-to-end against the real API only as far as the server's search_disabled/404 responses, which surface cleanly. Wire payloads (portable params, the content boolean/object union, and the pinned/fallback/auto strategy variants including native options) are covered by unit tests in cmd/search_test.go, along with flag wiring and client-side validation. Full `go build ./...` and `go test ./...` pass. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

cursor

Stale Bugbot comment from a previous run.

SDK release bump only; no API method or param changes. Full enumeration of api.md methods against CLI commands found no gaps. Tested: go build ./..., go test ./... Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Updates kernel-go-sdk to 1ef7b7c34dc3b987d6c515c82ea399c424f0c6e6 (adds iframe/worker browser event target types; response-only change). Full enumeration of SDK methods and params found no CLI coverage gaps. Tested: go build ./..., go test ./... (no new commands/flags to smoke test) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Updates kernel-go-sdk to 0584ea1d2238bfb06f1995ef4cab305917941efa. SDK change is documentation-only (BrowserMonitorDisconnectedEvent comment); full enumeration found no new coverage gaps. Build verified with go build ./... Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

cursor

Stale Bugbot comment from a previous run.

- Bump github.com/kernel/kernel-go-sdk to 35a02850ff6eac17ed5279dbdf54642e61d315b9 - `kernel auth connections get` now shows a "Health Check Unavailable" row when ManagedAuth.HealthCheckUnavailableReason is set (e.g. no_auth_check_url), so users know a recent health check does not verify the session. Coverage: full api.md enumeration found no new SDK methods or param fields needing CLI commands/flags (search contents is reserved/404; config-registry and auth exchange endpoints are x-cli-skip). Tested: go test ./...; auth connections list -o json and auth connections get against the live API; unit test for the new row. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Bump github.com/kernel/kernel-go-sdk to 6923472efed1a4e7f9d6f26124c3cbd381122812 ("Let Vaults fill credentials from 1Password"). The credential create spec is now a provider union, so vaults credentials create wraps the spec as the Kernel variant, defaults provider to "kernel", and rejects other providers. 1Password credentials, credential_account items, and the 1pw_* operations are left to the dedicated 1Password CLI work in #271. Tested against the real API: vaults create, credentials create (provider defaulted to kernel), credentials update, items get, items list, credentials create with provider 1password (rejected client-side), vaults delete. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

…configs - Bump kernel-go-sdk to c823c6c04c73498e266e0955790a81d187986b4f - vault-provider-configs create: --publishable-key (Link only) for VaultProviderConfigNewParamsBodyLinkCredentials.PublishableKey - vault-provider-configs update: --publishable-key for VaultProviderConfigUpdateParamsCredentials.PublishableKey - get/create/update/list JSON and table output show publishable_key Tested: vault-provider-configs create --provider link --publishable-key, get (shows Publishable Key), update --publishable-key -o json (value updated), delete; agentcard + --publishable-key rejected client-side. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

SDK version bump only; the SDK diff contains no API changes (release/changelog only). Full enumeration of api.md methods vs CLI commands found no coverage gaps (config-registry endpoints are x-cli-skip). Tested: go build ./... Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

# Conflicts: # cmd/vaults_credentials.go

rgarcia · 2026-09-30T15:46:41Z

bugbot run

cursor

Stale Bugbot comment from a previous run.

rgarcia · 2026-09-30T15:51:59Z

bugbot run

cursor

Stale Bugbot comment from a previous run.

Bump kernel-go-sdk to e7afbafa4eb45cec605435f03168751f361b21fa. client.Search.Contents.Fetch now ships and returns a response, so expose it as `kernel search contents <id>` with --result-ids/--limit, --timeout-ms and --content-{source,format,max-chars,max-age-hours,timeout-ms,browser-id,browser-mode}. Tested against the real API: - search contents --limit 1 --content-source provider --content-max-chars 200 - search contents --result-ids <id> --content-source browser --content-browser-mode curl --content-format text --timeout-ms 60000 - search contents --result-ids <id2>,<id1> --content-source auto --content-max-age-hours 0 --content-browser-id <browser> --content-browser-mode render --content-format markdown --content-timeout-ms 30000 (order preserved, browser deleted afterwards) - search contents on an unknown search ID returns a 404 error - go test ./... passes Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

socket-security · 2026-09-30T17:56:37Z

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	golang/github.com/kernel/kernel-go-sdk@v0.114.0 ⏵ v0.114.1-0.20260930182635-e746d9980b83	⁺¹

View full report

cursor

Stale Bugbot comment from a previous run.

Bump kernel-go-sdk to c393858a0e762bac87313c1096a5af22896c85ce (v0.115.0). The SDK changes since e7afbaf only touch release metadata (CHANGELOG, README, version). api.md and the param types are unchanged, so nothing new needs a CLI command or flag. Coverage: every api.md method maps to a CLI command, except the config-registry endpoints, which openapi.yaml marks x-cli-skip. Tested: go build ./..., go vet ./..., and go test ./... pass Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

- Bump github.com/kernel/kernel-go-sdk to e746d9980b83f915e8e9d85a75dfee8f16b8df96 - Document checkout_origin in the AgentCard card --spec help (CardVaultItemSpecAgentcardParam.CheckoutOrigin) - Keep spec.checkout_origin in filtered vault item JSON output - Show "Checkout origin" row in human-readable AgentCard card output - Tests: checkout_origin pass-through on cards create/update, JSON output filter Tested: vaults cards create --provider agentcard --spec '{...,"checkout_origin":"https://shop.example.com"}' (returned in spec), vaults items get (human + json show origin), vaults cards update omitting it (removed from spec), vaults items delete --yes (cleanup). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

chruffins · 2026-09-30T19:10:16Z

bugbot run

cursor

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit 29b2105. Configure here.}

kernel-internal Bot and others added 14 commits September 16, 2026 19:32

Merge main into cli-coverage-update

a63dd37

Merge main into cli-coverage-update

086f25e

Merge main into cli-coverage-update

d53e6ed

kernel-internal Bot changed the title ~~CLI: Update Go SDK to 6e379e6df7b9727b412e028352c25023439fefd8~~ CLI: Update SDK to dd9a4a4e3d3ae56a41429901b1cc7eb580febae7 and add new commands/flags Sep 21, 2026

kernel-internal Bot changed the title ~~CLI: Update SDK to dd9a4a4e3d3ae56a41429901b1cc7eb580febae7 and add new commands/flags~~ CLI: Update Go SDK to 68c51002947ba672c74f15f50420184c5b5ecbe7 Sep 21, 2026

kernel-internal Bot changed the title ~~CLI: Update Go SDK to 68c51002947ba672c74f15f50420184c5b5ecbe7~~ CLI: Update SDK to ca8d4655a0dc47369135fb4a938eeb5cf5326582 and surface managed auth completion times Sep 21, 2026

kernel-internal Bot changed the title ~~CLI: Update SDK to ca8d4655a0dc47369135fb4a938eeb5cf5326582 and surface managed auth completion times~~ CLI: Update SDK to aee0b02b9b0bdb2f84172ee9b568696dcd8fa482 and add new commands/flags Sep 21, 2026

kernel-internal Bot changed the title ~~CLI: Update SDK to aee0b02b9b0bdb2f84172ee9b568696dcd8fa482 and add new commands/flags~~ CLI: Update SDK to 05546992051b109e2a59e1b4a7f6f4455b1470db and add new commands/flags Sep 22, 2026

cursor Bot reviewed Sep 22, 2026

View reviewed changes

Comment thread cmd/search.go Outdated

chore: bump Go SDK to v0.111.0 (df8b441)

f50d037

SDK release bump only; no API method or param changes. Full enumeration of api.md methods against CLI commands found no gaps. Tested: go build ./..., go test ./... Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

kernel-internal Bot changed the title ~~CLI: Update SDK to 05546992051b109e2a59e1b4a7f6f4455b1470db and add new commands/flags~~ CLI: Update SDK to df8b4419112354f7b00a3954617d6fc50ccd1680 and add new commands/flags Sep 22, 2026

kernel-internal Bot changed the title ~~CLI: Update SDK to df8b4419112354f7b00a3954617d6fc50ccd1680 and add new commands/flags~~ CLI: Update SDK to 1ef7b7c34dc3b987d6c515c82ea399c424f0c6e6 and add new commands/flags Sep 22, 2026

kernel-internal Bot changed the title ~~CLI: Update SDK to 1ef7b7c34dc3b987d6c515c82ea399c424f0c6e6 and add new commands/flags~~ CLI: Update SDK to 0584ea1d2238bfb06f1995ef4cab305917941efa and add new commands/flags Sep 22, 2026

cursor Bot reviewed Sep 28, 2026

View reviewed changes

Comment thread cmd/browsers_telemetry.go

kernel-internal Bot changed the title ~~CLI: Update SDK to a1d4c5be424cb7211be912fb1a9a4cf9ec9f06fc and add new commands/flags~~ CLI: Update SDK to 35a02850ff6eac17ed5279dbdf54642e61d315b9 and add new commands/flags Sep 28, 2026

kernel-internal Bot changed the title ~~CLI: Update SDK to 35a02850ff6eac17ed5279dbdf54642e61d315b9 and add new commands/flags~~ CLI: Update SDK to 6923472efed1a4e7f9d6f26124c3cbd381122812 and add new commands/flags Sep 29, 2026

kernel-internal Bot changed the title ~~CLI: Update SDK to 6923472efed1a4e7f9d6f26124c3cbd381122812 and add new commands/flags~~ CLI: Update SDK to c823c6c04c73498e266e0955790a81d187986b4f and add new commands/flags Sep 30, 2026

kernel-internal Bot changed the title ~~CLI: Update SDK to c823c6c04c73498e266e0955790a81d187986b4f and add new commands/flags~~ CLI: Update SDK to b307cc10fdfab032069c951663312e04d0203b5b and add new commands/flags Sep 30, 2026

Merge remote-tracking branch 'origin/main' into cli-coverage-update

d99512c

# Conflicts: # cmd/vaults_credentials.go

rgarcia requested a review from hiroTamada September 30, 2026 15:42

cursor Bot reviewed Sep 30, 2026

View reviewed changes

Remove undocumented search contents command from README

c5099de

cursor Bot reviewed Sep 30, 2026

View reviewed changes

kernel-internal Bot changed the title ~~CLI: Update SDK to b307cc10fdfab032069c951663312e04d0203b5b and add new commands/flags~~ CLI: Update SDK to e7afbafa4eb45cec605435f03168751f361b21fa and add new commands/flags Sep 30, 2026

cursor Bot reviewed Sep 30, 2026

View reviewed changes

Comment thread cmd/search.go

kernel-internal Bot changed the title ~~CLI: Update SDK to e7afbafa4eb45cec605435f03168751f361b21fa and add new commands/flags~~ CLI: Update SDK to c393858a0e762bac87313c1096a5af22896c85ce (v0.115.0) and add new commands/flags Sep 30, 2026

kernel-internal Bot changed the title ~~CLI: Update SDK to c393858a0e762bac87313c1096a5af22896c85ce (v0.115.0) and add new commands/flags~~ CLI: Update SDK to e746d9980b83f915e8e9d85a75dfee8f16b8df96 and add new commands/flags Sep 30, 2026

cursor Bot reviewed Sep 30, 2026

View reviewed changes

chruffins approved these changes Sep 30, 2026

View reviewed changes

chruffins merged commit 3de7ce8 into main Sep 30, 2026
8 checks passed

chruffins deleted the cli-coverage-update branch September 30, 2026 19:38

chruffins mentioned this pull request Sep 30, 2026

Add deferred search content command #274

Closed

Navigation Menu

CLI: Update SDK to e746d9980b83f915e8e9d85a75dfee8f16b8df96 and add new commands/flags - #264

CLI: Update SDK to e746d9980b83f915e8e9d85a75dfee8f16b8df96 and add new commands/flags#264
chruffins merged 45 commits into
mainfrom
cli-coverage-update

kernel-internal Bot commented Sep 18, 2026 •

edited by cursor Bot

Loading

Uh oh!

cursor Bot left a comment •

edited

Loading

Uh oh!

Uh oh!

cursor Bot left a comment •

edited

Loading

Uh oh!

Uh oh!

rgarcia commented Sep 30, 2026

Uh oh!

cursor Bot left a comment •

edited

Loading

Uh oh!

rgarcia commented Sep 30, 2026

Uh oh!

cursor Bot left a comment •

edited

Loading

Uh oh!

socket-security Bot commented Sep 30, 2026 •

edited

Loading

Uh oh!

cursor Bot left a comment •

edited

Loading

Uh oh!

Uh oh!

chruffins commented Sep 30, 2026

Uh oh!

cursor Bot left a comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

kernel-internal Bot commented Sep 18, 2026 • edited by cursor Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

SDK Update

Coverage Analysis

New Flags / Output (e746d99)

New Commands (e7afbaf)

New Flags (e7afbaf)

New Flags (c823c6c)

Tested (c823c6c)

Changes (6923472)

Coverage notes (6923472)

New Flags (a1d4c5b)

New Output (233b087)

Coverage notes (233b087)

New Flags (8dcb671)

New Commands (47c1310)

New Flags (47c1310)

New Flags (ffc38db)

New Output (8e055e1)

New Flags (b50814f)

Earlier changes on this branch

Fixes (140c57d)

Coverage notes (140c57d)

Fixes

Testing

Uh oh!

cursor Bot left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

cursor Bot left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

rgarcia commented Sep 30, 2026

Uh oh!

cursor Bot left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

rgarcia commented Sep 30, 2026

Uh oh!

cursor Bot left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

socket-security Bot commented Sep 30, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

cursor Bot left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

chruffins commented Sep 30, 2026

Uh oh!

cursor Bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

kernel-internal Bot commented Sep 18, 2026 •

edited by cursor Bot

Loading

cursor Bot left a comment •

edited

Loading

cursor Bot left a comment •

edited

Loading

cursor Bot left a comment •

edited

Loading

cursor Bot left a comment •

edited

Loading

socket-security Bot commented Sep 30, 2026 •

edited

Loading

cursor Bot left a comment •

edited

Loading