Version Packages#1572
Merged
Merged
Conversation
threepointone
pushed a commit
that referenced
this pull request
May 21, 2026
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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 was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
agents@0.13.2
Patch Changes
#1570
4f14b9cThanks @threepointone! - Addagents/chat-sdk, a Chat SDKStateAdapterbacked by Agents sub-agents.This new package entrypoint exports:
createChatSdkState(), a convenience factory for Chat SDKstate.ChatSdkStateAdapter, the concrete adapter implementation.ChatSdkStateAgent, the default sub-agent used for durable Chat SDK state.defaultThreadShard()anddefaultKeyShard(), the default sharding helpers used by the adapter.The adapter stores Chat SDK subscriptions, concurrency locks, pending queues, generic cache entries, callback metadata, thread and channel state, persisted message history, and transcript lists in Durable Object SQLite. State is sharded through
parent.subAgent()so a messenger ingress Agent can keep Chat SDK infrastructure state inside child facets instead of requiring a separate top-level Durable Object binding for every state shard.createChatSdkState()now works with the defaultChatSdkStateAgentclass when it is re-exported from the Worker entrypoint. It also defaultsparentfromgetCurrentAgent()when called inside an Agent lifecycle method or request handler, so the common setup is:Applications that need custom state behavior can still pass a custom
agentsubclass and explicitparent.This also documents the sub-agent configuration model more clearly: production Workers should export facet classes, but facet-only child classes do not belong in
new_sqlite_classesunless they are also used as top-level Durable Objects. Test wrangler configs may still include facet classes as test-only Durable Object bindings for@cloudflare/vitest-pool-workerscompatibility, while keeping them out ofnew_sqlite_classes.@cloudflare/think@0.7.2
Patch Changes
4f14b9cThanks @threepointone! - Broadcast message updates from programmaticThink.chat()turns andclearMessages()so connecteduseAgentChatclients stay in sync without reconnecting.