Version Packages

[github-actions]

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.4.1

Patch Changes

• #890 22dbd2c Thanks @ask-bonk! - Fix _flushQueue() permanently blocking when a queued callback throws

  A throwing callback in _flushQueue() previously caused the failing row to never be dequeued, creating an infinite retry loop that blocked all subsequent queued tasks. Additionally, _flushingQueue was never reset to false on error, permanently locking the queue for the lifetime of the Durable Object instance.

  The fix wraps each callback invocation in try-catch-finally so that failing items are always dequeued and subsequent items continue processing. The _flushingQueue flag is now reset in a top-level finally block. Missing callbacks are also dequeued instead of being skipped indefinitely.

  Note for existing stuck Durable Objects: This fix is self-healing for poison rows — they will be properly dequeued on the next _flushQueue() call. However, _flushQueue() is only triggered by a new queue() call, not on DO initialization. If you have DOs stuck in production, you can either trigger a new queue() call on affected DOs, or call dequeueAll()/dequeueAllByCallback() to clear the poison rows manually. A future improvement may add a _flushQueue() call to onStart() so stuck DOs self-heal on wake.

• #891 0723b99 Thanks @ask-bonk! - Fix getCurrentAgent() returning undefined connection when used with @cloudflare/ai-chat and Vite SSR

  Re-export agentContext as __DO_NOT_USE_WILL_BREAK__agentContext from the main agents entry point and update @cloudflare/ai-chat to import it from agents instead of the agents/internal_context subpath export. This prevents Vite SSR pre-bundling from creating two separate AsyncLocalStorage instances, which caused getCurrentAgent().connection to be undefined inside onChatMessage and tool execute functions.

  The agents/internal_context subpath export has been removed from package.json and the deprecated agentContext alias has been removed from internal_context.ts. This was never a public API.

• Updated dependencies [584cebe, 0723b99, 4292f6b]:

  • @cloudflare/ai-chat@0.0.8

@cloudflare/ai-chat@0.0.8

Patch Changes

• #882 584cebe Thanks @alexanderjacobsen! - Fix multi-step client tool calling: pass stored client tool schemas to onChatMessage during tool continuations so the LLM can call additional client tools after auto-continuation. Also add a re-trigger mechanism to the client-side tool resolution effect to handle tool calls arriving during active resolution.

• #891 0723b99 Thanks @ask-bonk! - Fix getCurrentAgent() returning undefined connection when used with @cloudflare/ai-chat and Vite SSR

  Re-export agentContext as __DO_NOT_USE_WILL_BREAK__agentContext from the main agents entry point and update @cloudflare/ai-chat to import it from agents instead of the agents/internal_context subpath export. This prevents Vite SSR pre-bundling from creating two separate AsyncLocalStorage instances, which caused getCurrentAgent().connection to be undefined inside onChatMessage and tool execute functions.

  The agents/internal_context subpath export has been removed from package.json and the deprecated agentContext alias has been removed from internal_context.ts. This was never a public API.

• #886 4292f6b Thanks @whoiskatrin! - Forward custom body fields from client requests to onChatMessage options

  Custom data sent via prepareSendMessagesRequest or the AI SDK's body option in sendMessage is now available in the onChatMessage handler through options.body. This allows passing dynamic context (e.g., model selection, temperature, custom metadata) from the client to the server without workarounds.