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

Patch Changes

• #1902 a9d78c0 Thanks @mattzcarey! - Always apply the Worker-safe CfWorkerJsonSchemaValidator to MCP client connections by default.

  MCPClientConnection now owns the default (merged in its constructor), so every construction path uses the Worker-safe validator unless the caller supplies their own — including the RPC addMcpServer(name, namespace) path via MCPClientManager.connect(), which previously skipped it. Without the default, the MCP SDK fell back to its AJV validator when a server exposed tools with outputSchema; AJV compiles schemas with new Function, which Workers disallows, failing discovery with "Code generation from strings disallowed for this context".

  connect() now builds connections through createConnection() instead of duplicating construction, so the two paths can no longer drift. Caller-supplied client.jsonSchemaValidator overrides are respected on the live connection; because validator instances cannot survive JSON serialization, they are no longer persisted, and a previously persisted, serialization-degraded validator is ignored on restore — after hibernation the connection falls back to the Worker-safe default instead of failing discovery.

• #1903 3ba6a78 Thanks @mattzcarey! - MCP client: url-mode elicitation support with a real elicitation handler

  • Agents can now respond to server-initiated elicitation/create requests by
    calling this.mcp.configureElicitationHandlers({ form, url }), typically in
    onStart(). The advertised modes are persisted with each MCP server, so
    connections restored after Durable Object hibernation re-advertise them at
    the handshake and the handlers re-attach when onStart runs.
    MCPClientConnection also accepts elicitationHandlers callbacks for
    lower-level non-Agent usage.
  • Connections advertise elicitation modes based on what can actually be
    handled: they advertise exactly the modes with configured handlers at the
    initialize handshake; without handlers they advertise no elicitation
    capability. An explicit
    client.capabilities.elicitation (e.g. via addMcpServer) always wins,
    is persisted with the server options, and survives hibernation — it is no
    longer clobbered by a hardcoded value.
  • Overriding/instance-patching MCPClientConnection.handleElicitationRequest
    directly is deprecated in favor of the elicitationHandlers option.

• #1910 9e1b733 Thanks @mattzcarey! - MCP client: advertise no elicitation capability when no handler is configured

  Connections without an elicitation handler previously advertised form-mode
  elicitation while rejecting every elicitation request that arrived, so
  spec-compliant servers chose elicitation over their fallback flows and the
  tool call failed mid-flight. Connections now advertise the elicitation
  capability only when it can be handled: both form and url mode with a
  handlers configured via this.mcp.configureElicitationHandlers({ form, url })
  or the connection elicitationHandlers option, and no elicitation capability
  without handlers, letting servers fall back gracefully. Only modes with
  configured handlers are advertised.

  Behavior change: code relying on the deprecated pattern of instance-patching
  handleElicitationRequest on a connection stops receiving elicitation
  requests, because the capability is no longer advertised. Migrate to
  this.mcp.configureElicitationHandlers({ form, url }) / the connection
  elicitationHandlers option, or declare
  client.capabilities.elicitation explicitly — an explicit declaration is
  always honored.

• #1869 f274903 Thanks @mattzcarey! - Fix addMcpServer() reporting ready for an HTTP MCP connection that was restored while OAuth is still in progress.

  For an existing AUTHENTICATING connection, addMcpServer() now prefers the live authorization URL, otherwise returns a persisted absolute HTTP(S) authorization URL. If neither is available, it reconnects the existing connection without re-registering it: a new authorization URL is returned and persisted, a connected result is discovered before returning ready, and failed or incomplete OAuth results throw instead of falling through to ready.

@cloudflare/codemode@0.4.3

Patch Changes

• #1904 88f7f69 Thanks @mattzcarey! - Echo the durable tool-call log on the proxy tool output. ProxyToolOutput now carries an optional calls field (the execution's ToolLogEntry[]) on completed, paused and error outcomes, so UIs can render an audit trail of every connector call and step — name, args, result, approval requirement and state — without a separate executions() round trip.

@cloudflare/voice@0.3.4

Patch Changes

• #1909 63491bd Thanks @cjol! - Honor the configured sample rate for raw pcm16 audio payloads.

  Adds a sampleRate option to VoiceAgentOptions (default 16000) that is declared in the server audio_config message. VoiceClient reads it (exposed via a new sampleRate getter) and constructs AudioBuffer instances at that rate for raw pcm16 playback, so providers with a native rate other than 16 kHz (e.g. 24 kHz Gemini TTS) play at the correct speed. Falls back to 16 kHz when the server omits the field.

• #1891 d1cc317 Thanks @korinne! - Add transcriber readiness so voice agents wait for streaming STT startup before entering listening state or running call-start hooks.

@cloudflare/agent-think@0.0.1

Patch Changes

• Updated dependencies [a9d78c0, 3ba6a78, 9e1b733, f274903]:
  • agents@0.17.4
  • @cloudflare/think@0.12.1

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.