@flue/runtime
2.3.1 · 18 Nov 2026Apache-2.0524.4k / weekRepositoryHomepagenpmAtom feed
Upgrading @flue/runtime From 2.0.8 to 2.1.0
1 release in betweenevery note read
Release by release
- New
Trace content budgets are now configurable.
createCloudflareTracing({ contentBudgetBytes })andcreateOpenTelemetryInstrumentation({ contentBudgetBytes })override the default 56 KiB per-span content pool — raise it (e.g.contentBudgetBytes: 200_000) to ship fuller prompts and tool results to an observability backend that isn't bound by workerd's 64 KiB span-attribute cap, or tighten it. The 128-byte sentinel floor and the shared-pool semantics are unchanged. - New
Tools returned by
createMcpConnection()now retain the metadata sent by the MCP server in itstools/listresponse. The metadata is available on each Flue tool astool.annotations: - New
Tools can now declare a
timeoutMsexecution bound: on expiry the harness aborts the tool'scontext.signaland settles the call with aToolTimeoutError(the model seesTool "<name>" timed out after <ms>msand the conversation continues) instead of letting one hung call consume the submission's durability budget. - Fixed
The OpenTelemetry ecosystem page and Cloudflare target guide now document
contentBudgetBytesoncreateOpenTelemetryInstrumentation()/createCloudflareTracing(): an override for the default 56 KiB per-span content pool. Raising it ships fuller content only on backends not bound by workerd's span cap (the OpenTelemetry adapter); on the Cloudflare target it is a tightening control only, since workerd's 64 KiB span-attribute cap is a platform limit no setting raises.
- New
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.