Skip to content

Commit b1dfc29

Browse files
committed
Restore Hypeman changelog update
1 parent 4feed1e commit b1dfc29

1 file changed

Lines changed: 1 addition & 0 deletions

File tree

‎changelog.mdx‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,7 @@ For API library updates, see the [Node SDK](https://github.com/onkernel/kernel-n
1313
## Product updates
1414

1515
- Released the [Kernel Terraform provider](https://registry.terraform.io/providers/kernel/kernel/latest) on the Terraform Registry. Manage browser pools and projects as code, and reference existing profiles, proxies, and extensions as data sources. Install with `source = "kernel/kernel"`.
16+
- Released [Hypeman v0.3.0](https://github.com/kernel/hypeman/releases/tag/v0.3.0) with persistent Builder resources and build caches, safer auto-standby through `POST /instances/{id}/auto-standby/hold`, and a new default API port of `4973`. Existing explicit port settings are unchanged.
1617
- Shipped CUA CLI 0.9.0 alongside [`@onkernel/cua-agent`](https://github.com/kernel/cua) and [`@onkernel/cua-ai`](https://github.com/kernel/cua) 0.10.0, adding an OpenRouter Kimi K3 computer-use provider, message queuing during active turns with cleaner interrupt handling, and Tzafon post-action screenshots. Also made cua-ai's catalog compilation declaration-only with a clearer execution boundary. Note for anyone embedding `cua-agent`: 0.10.0 upgrades the underlying `pi` stack to 0.83.0 and adopts its context-first harness API, which is a breaking change to `CuaAgentHarness`.
1718
- Added a secure managed auth login panel to the [MCP server](/reference/mcp-server), exposed as a new `open_auth_login` tool. Agents hand the user an interactive panel to complete login and re-auth, so credentials and MFA codes never enter the conversation. `manage_auth_connections` gained a read-only `wait` action to follow a flow through to completion.
1819
- Protected managed auth connections from losing their configured egress: `DELETE /proxies/{id}` now returns `400 resource_in_use` when a live connection still references the proxy. Remove or repoint those connections before deleting the proxy.

0 commit comments

Comments
 (0)