Repository navigation
BYOK SDK 0.29.0 · keys 0.29.0
0.29.0 publication record
Date: 2026-10-23 (UTC).
Status: all nine packages are published on npm latest. The complete registry readback passed.
Changes
0.29.0 is a MINOR release under the default pre-1.0 policy, with no exception. It has breaking changes in client and keys.
- Core: the new subpath
@byok-sdk/core/sealed-payloadexports the sealed payload v1 byte rules. The root entry does not change. No wire message carries sealed content in this release (#654). - Protocol, server, cloud and client: an ordinary Agent offer can select the Agent memory of its task with
agentMemory. Devices advertise the capabilityagent-memory-selection. The client exportsAGENT_MEMORY_MCP_SERVER_NAME(#614). - Client: the Agent-home projection hook gets
writeHomeFile(name, body). One call atomically replaces one file at the root of the Agent home (#738). - Client (breaking): Agent memory refuses the same names on every platform: Windows device names, a trailing
., ASCII case pairs belownotesand files with more than one hard link (#605). - Client: Agent memory runs on Windows x64 through the SDK helper, on a local NTFS volume only. The helper manifest moves to version 2 (#605).
- Client (breaking): on macOS, the Agent memory helper admits an Agent home only on a local volume (#765).
- Client: on Windows, the Claude and Codex adapters start a CLI that npm installed as a
.cmdshim, without a shell (#763). - Keys (breaking):
PiModelConfigSchemaaccepts api_modelwithoutthinkingLevelMap(#636). - Examples: K4 gets routine versions, occurrence hooks, custom harness identities, a faster settle of a cancelled claimed task and a bounded wake retry. K8 Bot routines run on K4 routines, and
CollaborationStatemoves to version 2, which is breaking for the example (#606, #760, #762, #766).
See the CHANGELOG and the release notes for the full scope and the upgrade notes. The release tracker is #743.
Upgrade note that the release notes leave out
AgentHomeProjectionApplyInput has a new required member, writeHomeFile (#744). Code that builds this input itself, for example a test double that calls a projection hook, does not compile until it supplies the member. A Host that only implements the hook needs no change. The CHANGELOG and the release notes at the source commit do not include this note. A follow-up on main adds it to both files.
Source and accepted artifacts
- Source commit:
df0c91d208b99ef7cb957279274a26015afdf44bonmain, the merge of #773. - Push CI: run 39925218716 completed with success.
- Release matrix: run 39925242444, dispatched with
release_shaequal to the source. It completed with success: 33 jobs passed and 1 job was skipped as expected. - Artifact:
release-pack-df0c91d208b99ef7cb957279274a26015afdf44b, id12489361972. Manifest SHA-256:0cbe256bc8054fc373cbaf552d6af2ba298e85b6c0e9c055ba91d8623354c9d1. - Downstream acceptance (AiphaBee) passed on macOS with the nine CI tarballs from this artifact. Their SHA-256 and SHA-512 values match the manifest.
- After publication, the npm
dist.integrityof all nine packages was compared with the tarballs in this artifact. All nine are equal.
npm execution
The account is ancienttwo, with auth-and-writes 2FA. Uploads used browser authentication. This local route has no provenance attestation. The dist-tag is latest.
A first run uploaded nothing: its browser authentication request to the registry failed with a network reset (ECONNRESET), and the run was stopped. A second run uploaded all nine packages. The registry records them from 10:12:23 to 10:14:41 UTC. That run read back all nine packages and created the tag. No upload was repeated.
Tag
The annotated tag v0.29.0 points to df0c91d2. The tag object is 1d9a4b10ddf6d489394e0f70d26e74cf7c4c7f19. Its message is v0.29.0, a blank line, then sourceGitSha df0c91d208b99ef7cb957279274a26015afdf44b. It was created after the readback passed, on 2026-10-23 at 10:16:05 UTC.
Accepted tarballs
| Package | Version | SHA-256 |
|---|---|---|
@byok-sdk/core |
0.29.0 | 99661c7ceab3debf357d9cdc5f04e591c4d4398ab2c59ea606480148f039ebcf |
@byok-sdk/protocol |
0.29.0 | 030d7c201e8d448d87f0c2425a805b7ba8faca8ca78eeee46bbe423829c22a54 |
@byok-sdk/server |
0.29.0 | 0994120394f212583cfa1167f9676cad38d40135556e5b19f387f210d1d1d5ab |
@byok-sdk/cloud |
0.29.0 | 2adbcf55bf558256a44da6e23343f042021e4097f3314f51d8bc3a054d9ddf74 |
@byok-sdk/client |
0.29.0 | 1464f6ca18c12abae490bc25cd8dfe689b1f72106c5bc29f2e3748f105f286af |
@byok-sdk/cloud-dataplane |
0.29.0 | 9043911695175df3b1ca12fd59808a6d0cd52f10a611487a34ce0d8068da73b4 |
@byok-sdk/cloud-do |
0.29.0 | 085577e6f490e1f3ef3eb69eec330aa169041b801e4b0346bf023f255fec9554 |
@byok-sdk/ui-runtime |
0.29.0 | 09792d66e47ee237d808cb4992c052772e1cde0ec181a49f48b27ad3c6a2a760 |
@byok-sdk/keys |
0.29.0 | c70074aae13636aeb32b741e0df20df90e5a4e74a874e4528e90e16f19f48b4c |
Release boundary
AiphaBee accepted this release on macOS only. Windows code relies on the required windows-latest CI (#743, D5). On Windows, Agent memory makes no claim for an OS crash or a power loss; the power-loss experiment waits for a Windows environment (#605). On macOS, the helper checks only the volume of the Agent home itself, so a network mount nested inside the home is not checked in this release (#781). Live provider runs were not part of this release: real Windows runs of Hermes (#608) and Grok, and the submit_result success rate (#610). npm publication does not deploy a Host.