Packages

@flue/sdk

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

Your version

52 stable releases, newest first, by release line. Notes are quoted as the maintainers published them.

  1. 2.x · latest line
  2. 2.3.1

    18 Nov 2026
    • 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.

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

  3. 2.3.0

    12 Oct 2026
    • 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.

    • 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).

    • 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).

  4. 2.2.2

    28 Sep 2026

    No changes in this release.

  5. 2.2.1

    28 Sep 2026

    No changes in this release.

  6. 2.2.0

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

      Unbounded reads are unchanged. @flue/react still observes the whole conversation.

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

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

  7. 2.1.1

    23 Sep 2026
    • 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.

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

  8. 2.1.0

    18 Sep 2026
    • 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.

    • The MCP guide and Agent API reference now document preserved MCP tool annotations, including how trusted applications can inspect them and why server-supplied hints are not a security boundary.

    • The Tools guide and agent API reference now document timeoutMs on tool definitions: a per-call execution bound that aborts the tool's context.signal and settles the call with a ToolTimeoutError instead of letting one hung call consume the submission's durability budget.

  9. 2.0.8

    16 Sep 2026
    • 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.

  10. 2.0.7

    15 Sep 2026
    • Installed packages once again include the bundled Flue documentation, so commands such as flue docs read guide/sandboxes work out of the box.

    • Fix delayed reconnects in observe(): after a stream has been healthy for a full stream lifetime, the reconnect backoff resets, so a subsequent disconnect reconnects promptly instead of applying a stale delay.

  11. 2.0.6

    14 Sep 2026
    • Published packages once again include the bundled Flue documentation. The 2.0.4 and 2.0.5 releases omitted the generated docs/ directories from @flue/cli, @flue/runtime, and @flue/sdk, causing commands such as flue docs read guide/sandboxes to fail.

  12. 2.0.5

    11 Sep 2026
    • Published packages once again resolve internal Flue dependencies to the release version. The 2.0.4 release accidentally shipped raw pnpm workspace: dependency specifiers, making affected packages impossible to install outside the workspace. The complete lockstep package set is republished as 2.0.5 through pnpm so every internal dependency resolves to 2.0.5 (#657).

  13. 2.0.4

    9 Sep 2026
    • "Connection error." is now classified as a retryable model error. The retryable-error matcher recognized connection reset/connection refused/connection lost but not a bare connection error — a transient "Connection error." (with its trailing period) fell through the pattern and terminated the submission as a hard failure. The matcher now also accepts connection error and the run retries it under the transient-error budget (#629).

  14. 2.0.3

    5 Aug 2026
    • The Cloudflare Agents SDK (agents) is now a dependency of @flue/vite — projects no longer declare it. The generated Worker entry is the only code that imports the SDK, so the package that generates it ships it, and every project runs the SDK version Flue was tested against instead of whatever a scaffolded range resolves to on install day; flue init --target cloudflare stops writing the dependency, and existing projects can delete theirs. A project that declares its own agents dependency still wins — the plugin only falls back to its bundled copy when the project's node_modules chain has none. This also unbreaks fresh installs, which failed on an ai peer conflict internal to agents@0.14.5, the newest version the scaffolded ^0.14.2 range had come to resolve (reported by Ben Buzbee). The scaffolded wrangler range moves to ^4.113.0.

  15. 2.0.2

    4 Aug 2026
    • Conditional tool additions are now cache-safe on models with deferred tool loading. A tool mounted by the rerender that follows a settled tool batch is anchored to that batch's final tool result, so current first-party Anthropic models (Claude 4.5 and later, excluding Haiku) keep the added definition out of the cached prompt prefix instead of invalidating it; other providers ignore the anchor and their requests are unchanged. The anchor persists with the run and is restored on rehydration, so a rehydrated context matches the live loop exactly (the internal reduced-state format counter bumps to 2). The Tools guide now states the actual cache contract: tool-set changes rewrite the native tools array and invalidate the provider prompt cache, except additions unlocked by a completed tool call on the models above (#545).

    • The cloudflare-shell blueprint is replaced by cloudflare-computer, built on @cloudflare/computer — the successor to @cloudflare/shell that hosts a durable SQLite-backed workspace in the agent's own Durable Object with a just-bash shell backend, and can escalate to a container backend where a JavaScript shell isn't enough. The adapter provides a real exec() and keeps the framework's standard tool set instead of substituting a code tool. flue add cloudflare-shell and the old docs URLs redirect to the successor.

    • Cloudflare trace spans whose terminal event never arrives (their operation orphaned by deadline force-settlement or recovery) are force-closed when the submission settles, so the run's invoke_agent root span no longer vanishes from the trace. Forced closes carry a flue.span.forced_close attribute, and span-close failures are reported instead of swallowed.

  16. 2.0.1

    1 Aug 2026
    • Reasoning effort sent through the Workers AI binding's Responses wire format is now clamped to the /run endpoint's none|low|medium|high ceiling. A gateway model whose catalog maps the xhigh/max thinking levels verbatim (for example openai/gpt-5.6-luna) previously hard-400ed after admission for a thinking level Flue itself accepts — those catalog mappings are written for the model's own API, which does accept them over the HTTP gateway path; the ceiling is the binding transport's, and the chat-completions path already applied it. The emitted effort now always comes from the catalog's own low/medium/high mappings (#544).

    • A durable submission can no longer sit unsettled forever behind a hung await. On Cloudflare the wake handler previously both executed and supervised — it awaited every attempt, so one stalled model stream or sandbox RPC wedged the only loop that evaluates durability timeouts, and a backstop alarm firing mid-drain was silently consumed without re-arming. The coordinator now separates the roles: supervisor passes run bounded and storage-only (arming their successor heartbeat before any failable work, so no pass failure breaks the wake chain), and attempt fibers run detached, settling their own submissions. Deadline enforcement is structural on both targets: each pass fires the attempt's abort controller at timeoutAt (or on an unhonored durable abort) so signal-aware awaits unwind through the normal settle paths, and once the first signal outlives a 60-second grace the pass force-settles the submission over the hung fiber, orphaning it — the Node coordinator gets the same sweep from its lease scan, whose expired-lease branch was previously unreachable while a live process renewed a hung attempt's lease forever. A new FlueEvent operation, enforce_deadline, marks the signaled grace window and the force; the per-drain attempt cap is retired as vestigial (#538).

    • The awaits that could stall an attempt now bound themselves, so a stall recovers in seconds-to-minutes instead of failing at the durability deadline. Model streams on the Workers AI binding provider get an idle deadline: a chunk gap past the cap fails the read as a retryable interruption — the exact reported shape, a 200 that never speaks again, becomes a retried turn under the transient-error budget. The default is 5 minutes (long-thinking models can be legitimately silent), configurable per provider via streamIdleTimeoutMs, with 0 disabling it, and the timer only runs while a source read is outstanding so consumer backpressure never trips it. GatewayOptions.requestTimeoutMs — previously declared but never sent — is now emitted as the cf-aig-request-timeout header, a gateway-enforced bound on time to first response. Tools are abandoned on abort: every tool run races the attempt signal, so a signal-deaf tool (a sandbox file operation with no abort plumbing) rejects at abort instead of wedging the turn past every deadline, under the same orphaned-work contract as an orphaned exec (#538).

  17. 2.0.0

    31 Jul 2026
    • Breaking

      Flue is now a Vite plugin — flue dev and flue build are removed. Adopt Flue by adding flue() from the new @flue/vite package to vite.config.ts; vite dev and vite build own the deployable application. The Node target emits dist/server.mjs (run it with node dist/server.mjs; vite preview for Node is deferred). The Cloudflare target is the official @cloudflare/vite-plugin as an explicit sibling — plugins: [flue(), cloudflare({ config: flueWorkerConfig() })] — with the target auto-detected from cloudflare()'s presence; wrangler.jsonc stays user-owned, and Flue's contributions (the generated Worker entry, served as the virtual:flue/worker module, and the per-agent Durable Object bindings) are applied in memory by the flueWorkerConfig() customizer — nothing is generated into the project tree. flue.config.ts survives as the host-independent project config: defineConfig moves to @flue/runtime/config (the @flue/cli/config export is removed), the accepted fields are target, app, db, cloudflare, agents (a glob narrowing the 'use agent' scan), providers, and tracing, and the root/output fields and named vite export are dropped. See the migration guide for the full before/after.

    • Breaking

      File-based routing is removed — app.ts is the route map. The src/agents/*, src/workflows/*, and src/channels/* directory conventions no longer create routes or registrations. An agent module joins the application through the 'use agent' directive (the module's first statement); the build scans source files for the directive and registers every capitalized exported function as an agent, deriving each agent's durable storage identity from the exported function's name — or an agentName static pinning it — never from the file (on Cloudflare, one generated Flue<PascalName>Agent Durable Object class per exported agent function; renaming an unpinned function is the storage-identity change, expressed with wrangler-native renamed_classes, and colliding identities are a build error — renaming the file changes nothing). Every HTTP route is mounted explicitly in app.ts: app.route('/agents/triage', createAgentRouter(Triage)) for agents (createAgentRouter from @flue/runtime/routing), app.route('/channels/slack', slack.route()) for channels (hand-rolled channels mount via createChannelRouter). The router factory is pure and side-effect-free — registration comes from the scan, so dispatch-only agents need no mount, and the same agent can be mounted at two URLs. The agent module's named exports route (middleware), attachments, and description are removed along with the convention that read them: protect a mount with ordinary middleware layered in app.ts before it, and the attachment byte route is part of every agent router rather than opt-in. createDefaultFlueApp() and the runtime flue() router are removed; a missing app.ts is a build error.

    • Breaking

      Workflows are removed. defineWorkflow, invoke, run stores and run event streams, the /runs/:runId and POST /workflows/:name routes (including ?wait=result), listRuns/getRun, the SDK client.workflows/client.runs namespaces, the React workflow hooks, and the dev-console run UI are all deleted, with no compatibility stubs. Conversations are the only durable unit: a workflow becomes a program that drives an agent — flue run in a shell or CI step, the start()/init() JS API from Node, the Agent SDK over HTTP, or an external durable-workflow engine (Cloudflare Workflows, Inngest, Temporal) that checkpoints the dispatch receipt in one step and reads the settled reply in another. A deterministic code-first entrypoint (the old no-model run() body) has no direct replacement. The migration guide covers the conversion.

  18. 0.11.x
  19. 0.11.1

    11 Jun 2026

    Reading the note…

  20. 0.11.0

    10 Jun 2026

    Reading the note…

  21. 0.10.x
  22. 0.10.2

    10 Jun 2026

    Reading the note…

  23. 0.10.1

    8 Jun 2026

    Reading the note…

  24. 0.10.0

    8 Jun 2026

    Reading the note…

  25. 0.9.x
  26. 0.9.2

    3 Jun 2026

    Reading the note…

  27. 0.9.1

    2 Jun 2026

    Reading the note…

  28. 0.9.0

    2 Jun 2026

    Reading the note…

  29. 0.8.x
  30. 0.8.1

    28 May 2026

    Reading the note…

  31. 0.8.0

    27 May 2026

    Reading the note…

  32. 0.7.x
  33. 0.7.1

    26 May 2026

    Reading the note…

  34. 0.7.0

    15 May 2026

    Reading the note…

  35. 0.6.x
  36. 0.6.2

    14 May 2026

    Reading the note…

  37. 0.5.x
  38. 0.5.3

    12 May 2026

    Reading the note…

  39. 0.5.2

    11 May 2026

    Reading the note…

  40. 0.5.1

    11 May 2026

    Reading the note…

  41. 0.5.0

    11 May 2026

    Reading the note…

  42. 0.4.x
  43. 0.4.1

    10 May 2026

    Reading the note…

  44. 0.4.0

    10 May 2026

    Reading the note…

  45. 0.3.x
  46. 0.3.11

    7 May 2026

    Reading the note…

  47. 0.3.10

    3 May 2026

    Reading the note…

  48. 0.3.9

    3 May 2026

    Reading the note…

  49. 0.3.8

    3 May 2026

    Reading the note…

  50. 0.3.7

    3 May 2026

    Reading the note…

  51. 0.3.6

    2 May 2026

    Reading the note…

  52. 0.3.5

    30 Apr 2026

    Reading the note…

  53. 0.3.4

    30 Apr 2026

    Reading the note…

  54. 0.3.3

    30 Apr 2026

    Reading the note…

  55. 0.3.2

    30 Apr 2026

    Reading the note…

  56. 0.3.1

    30 Apr 2026

    Reading the note…

  57. 0.3.0

    30 Apr 2026

    Reading the note…

  58. 0.2.x
  59. 0.2.0

    24 Apr 2026

    Reading the note…

  60. 0.1.x
  61. 0.1.3

    21 Apr 2026

    Reading the note…

  62. 0.1.2

    21 Apr 2026

    Reading the note…

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.