@flue/react
2.3.1 · 18 Nov 2026Apache-2.0187.9k / weekRepositoryHomepagenpmAtom feed
16 stable releases, newest first, by release line. Notes are quoted as the maintainers published them.
2.3.1
18 Nov 2026Updated
@earendil-works/pi-aiand@earendil-works/pi-agent-coreto 1.5.2, fixing builds that picked up pi-ai 1.5.@flue/runtime2.3.0 imported TypeBox through@earendil-works/pi-ai, which stopped re-exporting it in 1.5.0, so a fresh install failedvite build. Flue now depends ontypeboxdirectly and requires pi^1.5.0; remove any overrides that held pi at 1.4. If your own code importsTypeorStaticfrom@earendil-works/pi-ai, import them fromtypeboxinstead. 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":; setcompat.requiresToolsWithToolHistory: trueon 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_toolsinput items.
2.3.0
12 Oct 2026Updated
@earendil-works/pi-aiand@earendil-works/pi-agent-coreto 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 fromazure-openai-responsestoazure, so changeazure-openai-responses/...model specifiers andprovidersconfig entries toazure. TheAZURE_OPENAI_*environment variables are unchanged. Tool and turndurationMsvalues now come from Pi's monotonic timing, so a tool's duration covers only its execution, not Flue's hooks or result storage.useAgentFinishcallbacks 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 documentedusePersistentStatepattern 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_resourceaccepts 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).
New Features
Updated
@earendil-works/pi-aiand@earendil-works/pi-agent-coreto 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 fromazure-openai-responsestoazure, so changeazure-openai-responses/...model specifiers andprovidersconfig entries toazure. TheAZURE_OPENAI_*environment variables are unchanged. Tool and turndurationMsvalues now come from Pi's monotonic timing, so a tool's duration covers only its execution, not Flue's hooks or result storage.
Fixes & Other Changes
useAgentFinishcallbacks 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 documentedusePersistentStatepattern 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_resourceaccepts 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).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 afterexec()returned (#809).Execution interceptors see
agentNameon model, tool, and shell steps, not only on the outeragentoperation. 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).flue init --target cloudflarescaffolds the Workers AI binding that keylesscloudflare/...models need, commented out inwrangler.jsonc. The generated agent suggested switching to a keyless Cloudflare model but nothing declaredenv.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).The E2B sandbox blueprint returns a non-zero exit from
exec()instead of throwing. E2B'scommands.run()throwsCommandExitErroron a non-zero exit, so a failing command rejected with no command or stderr instead of resolving with itsexitCode. The blueprint is bumped to version 2; runflue update sandbox e2bto update an existing integration (#805).
2.2.1 – 2.2.22 releases that only update dependencies@flue/sdk 2.2.2Show each
- 2.2.228 Sep 2026@flue/sdk 2.2.2
- 2.2.128 Sep 2026@flue/sdk 2.2.1
2.2.0
28 Sep 2026Support document attachments (PDFs) on user messages.
DeliveredAttachmentis now a union of image and document attachments —{ type: 'document', data, mimeType: 'application/pdf', filename? }— accepted ondispatch(), theinit()handle, and direct HTTP prompts.session.prompt(),skill(), andtask()gain adocumentsoption alongsideimages, and@flue/react'ssendMessage()gains adocumentsoption. Documents are forwarded to the model as native document content: Anthropicdocumentblocks, OpenAI (and Azure OpenAI) Responsesinput_fileparts, and GoogleinlineData. 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 asfileparts withmediaType: 'application/pdf'— so existing conversations and persistence adapters need no migration. The SDK also exportsDeliveredImageAttachmentandDeliveredDocumentAttachment.
Minor Changes
Support document attachments (PDFs) on user messages.
DeliveredAttachmentis now a union of image and document attachments —{ type: 'document', data, mimeType: 'application/pdf', filename? }— accepted ondispatch(), theinit()handle, and direct HTTP prompts.session.prompt(),skill(), andtask()gain adocumentsoption alongsideimages, and@flue/react'ssendMessage()gains adocumentsoption. Documents are forwarded to the model as native document content: Anthropicdocumentblocks, OpenAI (and Azure OpenAI) Responsesinput_fileparts, and GoogleinlineData. 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 asfileparts withmediaType: 'application/pdf'— so existing conversations and persistence adapters need no migration. The SDK also exportsDeliveredImageAttachmentandDeliveredDocumentAttachment.
2.1.1
23 Sep 2026Clarify
useFlueAgent'sstatuscontract to match the reducer's actual aggregate behavior.statusreflects the observed conversation's activity — including submissions admitted out-of-band (webhooks, dispatches, other clients) — combined with the hook's in-memory local admission recollection. The README now documents the full precedence order (failed-local-settlementerror→ streaming text →submitted→ active/recollected submissionstreaming→ retained-failed-senderror→idle) and notes that a locally-admitted submission that has not yet settled keepsstreamingacross empty or absent observations until it settles. The reload fix covers submissions already represented by conversation messages; a submission admitted but not yet materialized into a message at reload time is documented as a residual window.Keep
useFlueAgent'sstatusatstreamingafter a reload for an unsettled submission. The reducer now derives active (unsettled) submission ids from the observed conversation — messagesubmissionIds minus settled ids — instead of relying only on the in-memory admission receipt, which does not survive a reload. Previously a fresh hook would reportidlefor an admitted-but-silent prompt or a running tool call until the next assistant text part streamed.
Patch Changes
Clarify
useFlueAgent'sstatuscontract to match the reducer's actual aggregate behavior.statusreflects the observed conversation's activity — including submissions admitted out-of-band (webhooks, dispatches, other clients) — combined with the hook's in-memory local admission recollection. The README now documents the full precedence order (failed-local-settlementerror→ streaming text →submitted→ active/recollected submissionstreaming→ retained-failed-senderror→idle) and notes that a locally-admitted submission that has not yet settled keepsstreamingacross empty or absent observations until it settles. The reload fix covers submissions already represented by conversation messages; a submission admitted but not yet materialized into a message at reload time is documented as a residual window.Keep
useFlueAgent'sstatusatstreamingafter a reload for an unsettled submission. The reducer now derives active (unsettled) submission ids from the observed conversation — messagesubmissionIds minus settled ids — instead of relying only on the in-memory admission receipt, which does not survive a reload. Previously a fresh hook would reportidlefor an admitted-but-silent prompt or a running tool call until the next assistant text part streamed.
2.1.0
18 Sep 2026sendMessagenow passes through every send controlclient.send()accepts (idempotencyKey,initialData,uid,signal, …) and resolves with the admission receipt (AgentSendResult) instead ofvoid.Retry a send safely by keeping the key and reusing it when the request's outcome is uncertain:
const agent = useFlueAgent({ url }); const key = `prompt-${crypto.randomUUID()}`; // persist before sending try { const receipt = await agent.sendMessage('hello', { idempotencyKey: key }); // receipt.submissionId correlates with settlements; receipt.deduplicated // is true when this retry converged on an already-admitted send. } catch { // A network failure does not prove the server rejected the prompt — // retry later with the same key to converge on the original submission. }
Minor Changes
sendMessagenow passes through every send controlclient.send()accepts (idempotencyKey,initialData,uid,signal, …) and resolves with the admission receipt (AgentSendResult) instead ofvoid.Retry a send safely by keeping the key and reusing it when the request's outcome is uncertain:
const agent = useFlueAgent({ url }); const key = `prompt-${crypto.randomUUID()}`; // persist before sending try { const receipt = await agent.sendMessage('hello', { idempotencyKey: key }); // receipt.submissionId correlates with settlements; receipt.deduplicated // is true when this retry converged on an already-admitted send. } catch { // A network failure does not prove the server rejected the prompt — // retry later with the same key to converge on the original submission. }
2.0.8
16 Sep 2026Only updates a dependency:@flue/sdk 2.0.8
2.0.7
15 Sep 2026Fix
useFlueAgentcallbacks changing identity on every store update — they now stay stable until the underlying session changes, preventing unnecessary re-renders and stale-effect churn.
Patch Changes
Fix
useFlueAgentcallbacks changing identity on every store update — they now stay stable until the underlying session changes, preventing unnecessary re-renders and stale-effect churn.
2.0.6
14 Sep 2026Published 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 asflue docs read guide/sandboxesto fail.
2.0.5
11 Sep 2026Published 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).
2.0.4
9 Sep 2026"Connection error."is now classified as a retryable model error. The retryable-error matcher recognizedconnection reset/connection refused/connection lostbut not a bareconnection 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 acceptsconnection errorand the run retries it under the transient-error budget (#629).
2.0.3
5 Aug 2026Reading the note…
2.0.2
4 Aug 2026Reading the note…
2.0.1
1 Aug 2026Reading the note…
2.0.0
31 Jul 2026Reading 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.