Skip to content

Conversation

@rgarcia
Copy link
Contributor

@rgarcia rgarcia commented Jan 30, 2026

Summary

  • Updates SDK to v0.33.0 (commit 4719594652b863858cb7492ca78adbb850a10552)
  • Breaking change fix: Removes kernel agents auth command group since the AgentAuth API was removed from the SDK
  • Fixes kernel auth connections to use correct SDK field names after API refactoring
  • Adds --proxy-id and --proxy-name flags to kernel auth connections login
  • Previously added kernel auth connections command group for the managed auth API:
    • create: Create managed auth for profile/domain combination
    • get: Get managed auth by ID
    • list: List managed auths
    • delete: Delete managed auth
    • login: Start login flow
    • submit: Submit field values to login flow
    • follow: Follow login flow events via SSE
  • Previously added credential-providers list-items command

Test plan

  • CLI builds successfully (go build ./...)
  • All tests pass (go test ./...)
  • kernel auth connections --help shows all subcommands
  • kernel auth connections create --help shows all flags

SDK Version

github.com/kernel/kernel-go-sdk@4719594652b863858cb7492ca78adbb850a10552 (v0.33.0)


Note

Medium Risk
Medium risk due to the SDK upgrade plus removal/rewiring of CLI command groups and flags, which can break existing scripts and alter API request parameters (auth connections, browsers listing, invocation behavior). No direct credential-handling logic changes beyond new plumbing to the updated SDK APIs.

Overview
SDK bump to kernel-go-sdk@v0.33.0 and CLI surface changes. Removes the entire kernel agents command group (including the automated agents auth run flow) and stops registering it in root.go to match the SDK’s removed AgentAuth API.

Adds/updates managed auth workflows via kernel auth connections. Introduces connections create/get/list/delete/login/submit/follow using the new managed-auth (AuthConnection*) SDK types, including new --proxy-id/--proxy-name on login, support for credential references by name/provider/path/auto, and SSE-based follow.

Other CLI enhancements. kernel browsers list gains a new --status filter (active|deleted|all) with --include-deleted deprecated; kernel invoke adds --async-timeout and a new invoke browsers <invocation_id> to list browsers created by an invocation; and credential-providers adds list-items <id> backed by a new ListItems SDK call.

Written by Cursor Bugbot for commit f014527. This will update automatically on new commits. Configure here.

Cursor Agent added 3 commits January 30, 2026 05:09
- Updated kernel-go-sdk from v0.28.0 to v0.29.0
- Added 1280x800@60 to available viewport configurations to match SDK update
- Updated viewport test to reflect the new viewport option

SDK release notes:
- Add support for 1280x800@60 viewport
- Add convenient param.SetJSON helper
- Update kernel-go-sdk from v0.29.0 to v0.30.0
- Add --status flag for browser list (active, deleted, all)
- Add --async-timeout flag for invoke command

SDK bump triggered by: kernel/kernel-go-sdk@6ca29d2
@rgarcia rgarcia changed the title CLI: Update SDK to v0.29.0 and add 1280x800@60 viewport support CLI: Update SDK to v0.30.0 and add new flags Feb 3, 2026
@github-actions
Copy link

github-actions bot commented Feb 3, 2026

🔧 CI Fix Available

I've pushed a fix for the CI failure. The test TestGetAvailableViewports_ReturnsExpectedOptions was expecting 7 viewports but the function now returns 8 after the new 1280x800@60 viewport was added.

👉 Click here to create a PR with the fix

}
if asyncTimeout > 0 {
params.AsyncTimeoutSeconds = kernel.Opt(asyncTimeout)
}
Copy link

Choose a reason for hiding this comment

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

Missing validation for async-timeout documented bounds

Low Severity

The --async-timeout flag help text states "(min 10, max 3600)" but the code only checks if asyncTimeout > 0 before passing the value to AsyncTimeoutSeconds. This allows values like 5 (below minimum) or 10000 (above maximum) to be sent to the API. Users relying on the documented constraints would expect invalid values to be rejected by the CLI with a helpful error.

Additional Locations (1)

Fix in Cursor Fix in Web

cursoragent and others added 2 commits February 3, 2026 18:34
The viewport '1280x800@60' was added twice:
- Once in commit 899caee (SDK v0.29.0 update)
- Again in commit 4d9565b (feat: add 1280x800 viewport support #97)

This resulted in 8 items in getAvailableViewports() while the test
expected 7 items, causing test failures.

Also removes the duplicate assertion in the test file.

Co-authored-by: mason <mason@onkernel.com>
Adds CLI support for the SDK's InvocationService.ListBrowsers() method
which returns all active browser sessions created within a specific
invocation.

Usage: kernel invoke browsers <invocation_id> [--output json]

Co-authored-by: mason <mason@onkernel.com>
Cursor Agent and others added 2 commits February 7, 2026 18:35
…mand

- Update github.com/kernel/kernel-go-sdk from v0.30.0 to v0.32.0
- Add `kernel credential-providers list-items <id>` command to list all
  credential items from an external provider
- Fix breaking change: use Credential.Name instead of removed CredentialName
  field in AuthAgent display output

Co-authored-by: Cursor <cursoragent@cursor.com>
@rgarcia rgarcia changed the title CLI: Update SDK to v0.30.0 and add new flags CLI: Update SDK to v0.32.0 and add credential-providers list-items Feb 7, 2026
Add CLI commands for the new Auth.Connections SDK service:
- kernel auth connections create: Create managed auth for profile/domain
- kernel auth connections get: Get managed auth by ID
- kernel auth connections list: List managed auths
- kernel auth connections delete: Delete managed auth
- kernel auth connections login: Start login flow
- kernel auth connections submit: Submit field values to login flow
- kernel auth connections follow: Follow login flow events via SSE

Also bump SDK to latest version (c90e1da19efb).

Co-authored-by: Cursor <cursoragent@cursor.com>
@kernel-internal kernel-internal bot changed the title CLI: Update SDK to v0.32.0 and add credential-providers list-items CLI: Update SDK and add auth connections commands Feb 10, 2026
@cursor

This comment has been minimized.

kernel-internal bot and others added 3 commits February 11, 2026 11:07
- Update kernel-go-sdk to v0.33.0 (commit 4719594652b863858cb7492ca78adbb850a10552)
- Remove agents.go as the AgentAuth API has been removed from SDK
- Fix auth_connections.go to use correct SDK field names:
  - Use ManagedAuthCreateRequestProxyParam.ID instead of ProxyID
  - Update AuthConnectionLoginInput to use Proxy params instead of SaveCredentialAs
- Add proxy-id and proxy-name flags to auth connections login command

Co-authored-by: Cursor <cursoragent@cursor.com>
- Return error instead of nil in runInvocationBrowsers on API failure
- Add nil check on resp before accessing resp.Browsers
- Add nil check on SSE stream before defer Close in Follow
- Fix indentation in invoke SSE event handling

Co-authored-by: Cursor <cursoragent@cursor.com>
SubmitFieldsRequest: kernel.SubmitFieldsRequestParam{
Fields: in.FieldValues,
},
}
Copy link

Choose a reason for hiding this comment

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

Submit sends empty fields map for MFA-only requests

Low Severity

Fields is always set to in.FieldValues, which is a non-nil empty map[string]string (from make(map[string]string) in the cobra handler) when no --field flags are provided. This causes "fields": {} to be serialized in the request body even when only --mfa-option-id or --sso-button-selector is intended. Depending on API validation, this empty object may cause request rejection. Fields could be set conditionally only when hasFields is true.

Fix in Cursor Fix in Web

@cursor

This comment has been minimized.

- Fix auth exempt check so `auth connections` subcommands get an
  authenticated client (only `kernel auth` itself is exempt)
- Add --proxy-name to create (parity with login command)
- Add --no-save-credentials to create (defaults to saving)

Co-authored-by: Cursor <cursoragent@cursor.com>
Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

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

Bugbot Autofix is ON. A Cloud Agent has been kicked off to fix the reported issue.

CredentialAuto bool
ProxyID string
ProxyName string
SaveCredentials bool
Copy link

Choose a reason for hiding this comment

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

Unused SaveCredentials field in create input struct

Low Severity

The SaveCredentials field in AuthConnectionCreateInput is defined but never set or read anywhere. Only NoSaveCredentials is populated from the --no-save-credentials flag and checked in Create. The SaveCredentials field is dead code that adds confusion about the intended API surface.

Fix in Cursor Fix in Web

@cursor
Copy link

cursor bot commented Feb 11, 2026

Bugbot Autofix prepared fixes for 1 of the 1 bugs found in the latest run.

  • ✅ Fixed: Unused SaveCredentials field in create input struct
    • Removed the unused SaveCredentials field from AuthConnectionCreateInput since only NoSaveCredentials is ever set and checked.

Create PR

Or push these changes by commenting:

@cursor push 5094132f7e
Preview (5094132f7e)
diff --git a/cmd/auth_connections.go b/cmd/auth_connections.go
--- a/cmd/auth_connections.go
+++ b/cmd/auth_connections.go
@@ -42,8 +42,7 @@
 	CredentialAuto      bool
 	ProxyID             string
 	ProxyName           string
-	SaveCredentials     bool
-	NoSaveCredentials   bool
+	NoSaveCredentials bool
 	HealthCheckInterval int
 	Output              string
 }

@rgarcia rgarcia merged commit afd1bfe into main Feb 11, 2026
2 checks passed
@rgarcia rgarcia deleted the cli-coverage-update branch February 11, 2026 17:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants