@flue/react
2.3.1 · 18 Nov 2026Apache-2.0187.9k / weekRepositoryHomepagenpmAtom feed
Upgrading @flue/react From 2.1.1 to 2.3.1
5 releases in betweenevery note read
Release by release
- Fixed
Updated
@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. - 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_toolsinput items.
- Fixed
- New
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. - Fixed
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). - Fixed
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). - 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 afterexec()returned (#809). - Fixed
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). - Fixed
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). - Fixed
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).
- New
2.2.1 – 2.2.22 releases, nothing new or fixed in the notes
- New
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.
- New
3 internal lines (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.