chore(deps): bump agents from 0.7.9 to 0.13.3

[dependabot]

Bumps agents from 0.7.9 to 0.13.3.

Release notes

Sourced from agents's releases.

agents@0.13.3

Patch Changes

• #1580 a1cd51b Thanks @​threepointone! - Improve session auto-compaction estimates by including the Session-managed frozen system prompt, support custom token counters, and expose an auto-compaction error callback.

• #1559 f942ffe Thanks @​cjol! - Stash chat turn recovery metadata before inference starts so interrupted pre-stream turns can be reconciled by chat recovery. Pre-stream interruptions now automatically retry the existing unanswered user message when it is still safe to do so.

• #1579 d0b4d0e Thanks @​threepointone! - Ensure Agent-generated workflow instance IDs always satisfy the Workflows runtime ID validator.

• #1567 3cfa498 Thanks @​cjol! - Return error statuses for in-band stream errors across programmatic chat turns.

• #1578 6fa7fd7 Thanks @​threepointone! - Use path-scoped identities for newly-created sub-agents while preserving legacy bare-name identities for existing registry entries.

• #1578 6fa7fd7 Thanks @​threepointone! - Avoid self-deadlocking facet startup when same-name sub-agents hydrate WebSocket connection state after wake.

agents@0.13.2

Patch Changes

• #1570 4f14b9c Thanks @​threepointone! - Add agents/chat-sdk, a Chat SDK StateAdapter backed by Agents sub-agents.

  This new package entrypoint exports:

  • createChatSdkState(), a convenience factory for Chat SDK state.
  • ChatSdkStateAdapter, the concrete adapter implementation.
  • ChatSdkStateAgent, the default sub-agent used for durable Chat SDK state.
  • defaultThreadShard() and defaultKeyShard(), 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 default ChatSdkStateAgent class when it is re-exported from the Worker entrypoint. It also defaults parent from getCurrentAgent() when called inside an Agent lifecycle method or request handler, so the common setup is:

  export { ChatSdkStateAgent } from "agents/chat-sdk";
  const chat = new Chat({
  adapters,
  state: createChatSdkState(),
  });

  Applications that need custom state behavior can still pass a custom agent subclass and explicit parent.

  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_classes unless 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-workers compatibility, while keeping them out of new_sqlite_classes.

agents@0.13.1

Patch Changes

• #1563 32cde40 Thanks @​threepointone! - Add managed fiber jobs with idempotent acceptance, optional completion waiting, inspection, cancellation, explicit recovery outcomes, and retained terminal status records.

agents@0.13.0

... (truncated)

Changelog

Sourced from agents's changelog.

0.13.3

Patch Changes

• #1580 a1cd51b Thanks @​threepointone! - Improve session auto-compaction estimates by including the Session-managed frozen system prompt, support custom token counters, and expose an auto-compaction error callback.

• #1559 f942ffe Thanks @​cjol! - Stash chat turn recovery metadata before inference starts so interrupted pre-stream turns can be reconciled by chat recovery. Pre-stream interruptions now automatically retry the existing unanswered user message when it is still safe to do so.

• #1579 d0b4d0e Thanks @​threepointone! - Ensure Agent-generated workflow instance IDs always satisfy the Workflows runtime ID validator.

• #1567 3cfa498 Thanks @​cjol! - Return error statuses for in-band stream errors across programmatic chat turns.

• #1578 6fa7fd7 Thanks @​threepointone! - Use path-scoped identities for newly-created sub-agents while preserving legacy bare-name identities for existing registry entries.

• #1578 6fa7fd7 Thanks @​threepointone! - Avoid self-deadlocking facet startup when same-name sub-agents hydrate WebSocket connection state after wake.

0.13.2

Patch Changes

• #1570 4f14b9c Thanks @​threepointone! - Add agents/chat-sdk, a Chat SDK StateAdapter backed by Agents sub-agents.

  This new package entrypoint exports:

  • createChatSdkState(), a convenience factory for Chat SDK state.
  • ChatSdkStateAdapter, the concrete adapter implementation.
  • ChatSdkStateAgent, the default sub-agent used for durable Chat SDK state.
  • defaultThreadShard() and defaultKeyShard(), 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 default ChatSdkStateAgent class when it is re-exported from the Worker entrypoint. It also defaults parent from getCurrentAgent() when called inside an Agent lifecycle method or request handler, so the common setup is:

  export { ChatSdkStateAgent } from "agents/chat-sdk";
  const chat = new Chat({
  adapters,
  state: createChatSdkState(),
  });

  Applications that need custom state behavior can still pass a custom agent subclass and explicit parent.

  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_classes unless 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-workers compatibility, while keeping them out of new_sqlite_classes.

0.13.1

Patch Changes

... (truncated)

Commits

• b504eed Version Packages (#1573)
• a1cd51b Fix session auto-compaction token estimates (#1580)
• 6fa7fd7 Fix facet identity self-deadlocks (#1578)
• d0b4d0e fix: generate valid default workflow IDs (#1579)
• 3cfa498 fix: fire chat responses for errors returned before parts are returned (#1567)
• f942ffe feat: Stash chat metadata for recovery before inference starts (#1559)
• 5beeeb4 Version Packages (#1572)
• 4f14b9c Add Chat SDK state adapter and messenger admin UI (#1570)
• a5bc238 Version Packages (#1562)
• 32cde40 Add Chat SDK messenger example with managed fiber durability (#1563)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)