Packages

@flue/runtime

2.3.1 · 18 Nov 2026Apache-2.0524.4k / weekRepositoryHomepagenpmAtom feed

Upgrading @flue/runtime From 0.6.2 to 2.3.1

28 releases in betweenevery note read

Other targets from 0.6.2Newest 0.x0.11.1
  1. 0.6.2yours
  2. 0.7.0major
  3. 1 release
  4. 0.8.0major
  5. 1 release
  6. 0.9.0major
  7. 2 releases
  8. 0.10.0major
  9. 1 release
  10. 0.10.2breaking
  11. 0.11.0major
  12. 1 release
  13. 2.0.0major
  14. 14 releases
  15. 2.3.1target
  16. 4 pre

Start here

Before you upgrade

Tick each one off as you go
  • Breaking2.0.0
  • Breaking2.0.0
  • Breaking2.0.0
  • Breaking2.0.0
  • Breaking2.0.0
  • Breaking2.0.0
  • Breaking2.0.0
  • Breaking2.0.0
  • Breaking2.0.0
  • Breaking2.0.0

Release by release

  1. 2.3.1

    18 Nov 20262 fixes
    • Fixed

      Updated @earendil-works/pi-ai and @earendil-works/pi-agent-core to 1.5.2, fixing builds that picked up pi-ai 1.5. @flue/runtime 2.3.0 imported TypeBox through @earendil-works/pi-ai, which stopped re-exporting it in 1.5.0, so a fresh install failed vite build. Flue now depends on typebox directly and requires pi ^1.5.0; remove any overrides that held pi at 1.4. If your own code imports Type or Static from @earendil-works/pi-ai, import them from typebox instead. Pi now validates tool arguments with its own JSON Schema validator, which coerces a little more (for example "3" for a number) and words its validation errors differently. OpenAI-compatible requests with no tools no longer send "tools":; set compat.requiresToolsWithToolHistory: true on models behind proxies that require it, such as older LiteLLM versions in front of Anthropic.

    • Fixed

      Workers AI binding models on the Responses API declare tools the way pi's own OpenAI provider does. Since pi 1.4, the binding passed a boolean where pi expected a tool-support mode, so a model without deferred tool loading could leave tools added mid-conversation out of its request. Models that support mid-conversation tool additions now declare every tool through additional_tools input items.

  2. 2.3.0

    12 Oct 20261 new · 6 fixes
    • New

      Updated @earendil-works/pi-ai and @earendil-works/pi-agent-core to 1.1.0. New models resolve with no configuration, including Claude Sonnet 5.5 (anthropic/claude-sonnet-5-5), Claude Haiku 5.5 (anthropic/claude-haiku-5-5), and GPT-6.1 Sol (openai/gpt-6.1-sol). Azure users must update: Pi renamed the Azure provider from azure-openai-responses to azure, so change azure-openai-responses/... model specifiers and providers config entries to azure. The AZURE_OPENAI_* environment variables are unchanged. Tool and turn durationMs values now come from Pi's monotonic timing, so a tool's duration covers only its execution, not Flue's hooks or result storage.

    • Fixed

      useAgentFinish callbacks once again see state written during the response. Since 2.2.0, finish hooks ran against the agent render from before the response's final turn, so a durable guard set by a finish callback — the documented usePersistentState pattern for appending a reminder once — was never observed: the callback re-appended on every cycle until the response failed at the runaway-loop ceiling. The agent now re-renders before each finish-hook cycle (#818).

    • Fixed

      read_skill_resource accepts a packaged skill path without its leading /. Models often echo the advertised /.flue/packaged-skills/... path without the slash, and the read failed as not found (#781).

    • Fixed

      The local sandbox SIGKILLs a command's whole process group after the grace period, even when the shell exits first. On an exec() timeout or abort, the pending SIGKILL was cancelled once the shell's pipes closed, so a process that ignored SIGTERM and held none of the shell's output kept running after exec() returned (#809).

    • Fixed

      Execution interceptors see agentName on model, tool, and shell steps, not only on the outer agent operation. The root harness's execution context carried only the instance id, so an interceptor that branches per agent took its default branch on every step (#785).

    • Fixed

      flue init --target cloudflare scaffolds the Workers AI binding that keyless cloudflare/... models need, commented out in wrangler.jsonc. The generated agent suggested switching to a keyless Cloudflare model but nothing declared env.AI; it now points at the binding to uncomment. The binding stays off by default because it reaches your Cloudflare account even in local dev (#739).

    • Fixed

      The E2B sandbox blueprint returns a non-zero exit from exec() instead of throwing. E2B's commands.run() throws CommandExitError on a non-zero exit, so a failing command rejected with no command or stderr instead of resolving with its exitCode. The blueprint is bumped to version 2; run flue update sandbox e2b to update an existing integration (#805).

  3. 2.2.2

    28 Sep 20261 fix
    • Fixed

      Fix Claude models on the cloudflare-ai-gateway provider failing with 404 not_found_error: model: claude-sonnet-4.6 was not found. Since Pi 0.84.3 the gateway catalog lists Claude models with dotted versions (claude-sonnet-4.6), but the gateway's native Anthropic endpoint forwards the model ID to Anthropic, which only accepts dashed IDs. Flue now registers these models under Anthropic's IDs (cloudflare-ai-gateway/claude-sonnet-4-6); dotted specifiers still resolve to them. The cloudflare binding provider, which uses Cloudflare's dotted catalog names, is unchanged.

  4. 2.2.1

    28 Sep 20261 fix
    • Fixed

      Fix model specifiers that stopped resolving after the Pi 0.87.1 upgrade. Pi renamed the cloudflare-ai-gateway Claude model IDs from dashed versions to dotted versions (claude-sonnet-4-6 → claude-sonnet-4.6), so existing specifiers such as cloudflare-ai-gateway/claude-sonnet-4-6 failed with Unknown model ID. When a model ID isn't in the catalog but matches exactly one catalog ID that differs only in - versus . between version digits, Flue now resolves to that model and logs a one-time warning suggesting the current ID.

  5. 2.2.0

    28 Sep 20264 new · 1 fix
    • New

      Add bounded conversation history reads so long-running chats no longer transfer the whole transcript on every page load or reconnect.

    • New

      Support document attachments (PDFs) on user messages. DeliveredAttachment is now a union of image and document attachments — { type: 'document', data, mimeType: 'application/pdf', filename? } — accepted on dispatch(), the init() handle, and direct HTTP prompts. session.prompt(), skill(), and task() gain a documents option alongside images, and @flue/react's sendMessage() gains a documents option. Documents are forwarded to the model as native document content: Anthropic document blocks, OpenAI (and Azure OpenAI) Responses input_file parts, and Google inlineData. On other model APIs the document is replaced in model context with a text placeholder saying it was omitted. Documents are stored like images — as canonical attachments projected as file parts with mediaType: 'application/pdf' — so existing conversations and persistence adapters need no migration. The SDK also exports DeliveredImageAttachment and DeliveredDocumentAttachment.

    • New

      Conversation messages now carry a server-authored timestamp (ISO 8601 capture time of the underlying durable record) in history(), observe(), and useFlueAgent. It works for every role and for existing conversations. metadata remains entirely agent-authored. Conversation settlements carry the same timestamp for when the submission settled.

    • New

      Adds support for GPT-6 Sol, GPT-6 Luna, and Claude Opus 5.5. Flue now uses Pi 0.87.1, so you can pass these models to useModel() without extra configuration. The model list at https://flueframework.com/models.json also includes them now. There are no public API changes.

    • Fixed

      Fix Cloudflare-routed Anthropic models (cloudflare/anthropic/*) failing with betas: Extra inputs are not permitted whenever the agent had tools. Anthropic beta features are now sent in the anthropic-beta request header instead of the request body.

  6. 2.1.1

    23 Sep 20261 new · 3 fixes
    • New

      Allow Flue packages and newly scaffolded applications to share a compatible Hono installation. Hono dependencies now use ^4.12.32, preventing fresh projects from installing a newer root Hono alongside the runtime's older exact version and failing typecheck.

    • Fixed

      Clarify that a skill's allowed-tools field is guidance. Flue accepts it for Agent Skills spec compatibility and does not enforce it; enforce authorization in your own tools and approval gates.

    • Fixed

      Make trace content truncation scale linearly for long message arrays. Large traced conversations no longer repeatedly serialize the remaining history while fitting gen_ai.input.messages to the attribute budget, avoiding request latency and Cloudflare Durable Object CPU-limit resets.

    • Fixed

      Record tool arguments and results of every payload shape on the standard gen_ai.tool.call.arguments / gen_ai.tool.call.result attributes, so OTel backends can display them. The shape-based diversion to the vendor flue.tool.call.* fallback keys is removed — those keys are no longer emitted, and their constants are retained for source compatibility. Payloads record exactly as before: objects/arrays as JSON strings, strings byte-for-byte within the content budget, other scalars as their JSON form.

  7. 2.1.0

    18 Sep 20263 new · 5 fixes
    • New

      Trace content budgets are now configurable. createCloudflareTracing({ contentBudgetBytes }) and createOpenTelemetryInstrumentation({ 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 its tools/list response. The metadata is available on each Flue tool as tool.annotations:

    • New

      Tools can now declare a timeoutMs execution bound: on expiry the harness aborts the tool's context.signal and settles the call with a ToolTimeoutError (the model sees Tool "<name>" timed out after <ms>ms and 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 contentBudgetBytes on createOpenTelemetryInstrumentation() / 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.

  8. 2.0.8

    16 Sep 20268 fixes
    • Fixed

      Interrupted submissions no longer retry forever when the recovery render throws: once the submission's durability deadline passes, a submission whose classification render keeps failing is settled as timed out instead of being re-rendered on every supervisor wake without ever consuming an attempt.

    • Fixed

      The Cloudflare binding's Anthropic gateway path now maps the agent's thinkingLevel to an adaptive-thinking effort (output_config.effort), so useModel thinking levels take effect on adaptive-thinking models instead of always running at Anthropic's default.

    • Fixed

      The Cloudflare binding provider now accepts a cacheRetention option ('short' or 'long') to enable Anthropic prompt caching for anthropic/… gateway models — repeated prefixes are served from cache at the cached input rate instead of paying full input price every turn. Default 'none' keeps the previous behavior.

    • Fixed

      The Cloudflare Sandbox documentation page now presents flue add sandbox cloudflare as a copyable prompt for your coding agent, with an explainer of what the blueprint-driven agent may do — installing @cloudflare/sandbox, wiring the Durable Object binding, migration, and container Dockerfile, and updating the agent to use the sandbox.

1 internal line (docs, tests, tooling) left out.

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.