@flue/cli
2.3.1 · 18 Nov 2026Apache-2.0217.3k / weekRepositoryHomepagenpmAtom feed
Upgrading @flue/cli From 0.0.4 to 0.11.1
81 releases in betweennotes for 21
- 51+
- changes to make
- 0
- advisories fixed
- 57+
- new
- 57+
- fixes
Counted from 21 of 81 release notes. Advisories are counted from the advisory database, in full.
Before you upgrade
Tick each one off as you go- Breaking0.10.2
- Breaking0.10.2
- Breaking0.10.2
- Breaking0.10.2
- Breaking0.10.2
- Breaking0.10.0
- Breaking0.10.0
- Breaking0.10.0
- Breaking0.10.0
- Breaking0.10.0
Release by release
- New
Direct agent HTTP requests and
@flue/sdkprompts can include images with up to 14 MiB of encoded data per image. Node and Cloudflare SQLite persistence stores image data in safe chunks and restores it for future turns and after restarts. - Fixed
The grep tool now uses ripgrep when available, falls back to grep, treats patterns as extended regular expressions by default, and supports literal matching.
- Fixed
SQL-backed sessions now store each history entry in its own row instead of rewriting the entire session history as one JSON value. Session saves remain transactional and preserve ordered history across Cloudflare Durable Object SQLite, Node SQLite, and PostgreSQL.
- New
- New
flue docsbrowses the documentation offline. The docs markdown already shipped inside@flue/cliis now reachable from the command line:flue docslists every page,flue docs read <path>prints one page as Markdown, andflue docs search <query>prints ranked JSON results. Content requires no network access and always matches the installed CLI version. Designed for coding agents (search → read), per Documentation. - Fixed
Runtime events no longer carry raw image bytes (#221). Image content blocks in session events (
message_*,turn_request,turn_end,agent_end,tool_call) keep theirmimeTypebut havedatareplaced with the exportedIMAGE_DATA_OMITTEDsentinel before events reach observers and persisted run history. Model context and persisted session history retain the real bytes. Events persisted before this change are unaffected. - Fixed
Updated
@earendil-works/pi-aiand@earendil-works/pi-agent-coreto 0.79.1.
- New
- Breaking
Durable Streams protocol replaces WebSocket and SSE transports. Agent instances and workflow runs are now URL-addressable durable event streams. Clients consume events via DS-compliant
GET(catch-up, long-poll, SSE) with automatic offset-based reconnection.POST /agents/:name/:idnow returns202 { streamUrl, offset }; add?wait=resultfor200 { result, streamUrl, offset }.GET /agents/:name/:idreads the event stream.GET /runs/:runIdreplaces both/runs/:runId/eventsand/runs/:runId/stream. WebSocket transport,AgentSocket,WorkflowSocket, and all socket-related types are removed from@flue/runtimeand@flue/sdk. - Breaking
Named sessions removed from agent public API. The
sessionparameter is removed from prompt submission, dispatch, SDK, and CLI. Agent instances always use the"default"session internally. An agent instance is now a single conversation with a single event stream. - Breaking
SDK rewritten with
@durable-streams/client.@flue/sdknow exportsagents.prompt(),agents.send(),agents.stream(),runs.stream(),runs.events(), andworkflows.invoke().agents.prompt()waits for the result;agents.send()returns stream coordinates immediately.FlueEventStream<T>wraps the DS client'sjsonStream()as an async iterable withcancel()andoffsetsupport. - Breaking
connectEventStreamStore()is now required onPersistenceAdapter. Custom adapters must implement this method and provide durable event-stream storage. The built-insqlite()and@flue/postgresadapters provide implementations.
- Breaking
- New
Added
deleted_classesandrenamed_classesmigration examples to the Cloudflare target documentation (#203). - Fixed
Fixed generated Node and Cloudflare app entrypoints by avoiding collisions with application-owned
appbindings. - Fixed
Updated
@earendil-works/pi-aiand@earendil-works/pi-agent-coreto 0.79.0. - Fixed
Fixed docs search dialog throwing
InvalidStateErrorwhenCmd/Ctrl+Kis pressed while already open (#214). - Fixed
Fixed SSE parser missing frame boundaries when CRLF is split across stream chunks or when using CR-only line endings (#216).
- New
- Breaking
Cloudflare durable deployments require a migration. Generated Durable Object bindings and class names changed to
FLUE_<NAME>_AGENT,FLUE_<NAME>_WORKFLOW,FLUE_REGISTRY,Flue<Name>Agent,Flue<Name>Workflow, andFlueRegistry. Existing deployments must add authored Wranglerrenamed_classesmigrations for already-deployed agent and workflow classes, update direct binding access such asenv.Assistanttoenv.FLUE_ASSISTANT_AGENT, and introduce fresh SQLite-backed agent classes throughnew_sqlite_classes; existing KV-backed classes cannot be converted in place. Installagents >=0.14.1 <0.15.0for the audited Agents SDK behavior used by this release. - Breaking
Runtime surface cleanup. Removed
tool_execution_*event types, the@flue/runtime/app,@flue/runtime/client, and@flue/runtime/sandboxcompat subpaths, publicAgentConfig/DirectAgentPayloadexports, public Cloudflare agent WebSocket adapters,store()from@flue/runtime/cloudflare, and the old Cloudflare shell migration stubs. - Breaking
Persistence adapter contracts changed. Custom adapters now implement
connectRunStore()andconnectRunRegistry()onPersistenceAdapter, useSubmissionClaimRefforclaimSubmission(), and providerenewLeases(),listExpiredSubmissions(), anddeleteSession()onAgentSubmissionStore. - Breaking
Session state changed. Ordinary session names beginning with
task:are now reserved for framework-owned delegated-task history, and existing version-4 beta session state is rejected because provider affinity now uses one opaqueaff_<ULID>key instead of derived instance/harness/session identifiers.
- Breaking
- Fixed
Fixed agents' ability to activate skills autonomously with the
activate_skilltool.
- Fixed
- Fixed
Fixed relative cwd double-scoping in custom sandbox connectors. Flue now applies a created agent's
cwdexactly once duringinit(), relative to the connector's provider-owned base directory.SandboxFactory.createSessionEnv()now receives only{ id }; connector implementations should stop consumingcwdthere. - Fixed
SDK: Export reusable option types.
@flue/sdknow exports option types for direct agent invocation, socket prompts, workflow-run event retrieval and streaming, and admin run listing, plus theRunStatustype. - Fixed
MCP tools discovered through paginated listings now preserve output-schema validation and required task-execution metadata across every page.
- Fixed
GET /admin/agentsandclient.admin.agents.list()return one unpaginated list of all built agents. The unusednextCursorresponse field was removed from the SDK and OpenAPI schema.
- Fixed
- Breaking
Move application routing imports out of
@flue/runtime/app. Importflue,admin, andFetchablefrom@flue/runtime/routing. Import provider APIs andobservefrom@flue/runtime, and Workers AI binding types from@flue/runtime/cloudflare. Rename theProviderSettingstype toProviderConfiguration. - Breaking
Check your authored source directory. Flue now selects exactly one source directory in priority order:
.flue/,src/, then the project root. If your project already has asrc/directory, move root-level agents and workflows into the selected source directory so Flue continues to discover them. - Breaking
Cloudflare: Own Cloudflare Durable Object migrations in your project Wrangler config. Flue still generates classes and bindings, but no longer appends migrations automatically. Before upgrading an existing deployment, copy its complete ordered
flue-class-*migration history from the previously generated.flue-vite.wrangler.jsoncor builtwrangler.jsoninto the project-root Wrangler config. Keep deployed tags unchanged, and append a uniquely taggednew_sqlite_classesentry whenever you add an agent or workflow class. - Breaking
Workflows: Retry interrupted Cloudflare workflows explicitly. Flue no longer starts a replacement workflow run automatically after an interruption. The interrupted run is recorded as failed; invoke the workflow again when retrying is appropriate. Restart-link fields and their legacy OpenTelemetry attributes were removed.
- Breaking
2 other lines we could not sort, mostly version bumps
- 0.4.0
With the new
'local'sandbox, the host shell is exposed directly. The agent'sbashtool can rungh issue view,npm test, etc. with whatever's on$PATHand whatever env you launched flue with. The runner / container / VM is the isolation boundary. - 0.4.0
For non-
'local'sandboxes, install the binaries inside the sandbox image, or wrap the operation as a custom tool withinit({ tools: [...] }). Tools have a structured parameter schema, are visible to the model directly, and recover the "secrets stay on the host" property — the tool readsprocess.env, the agent only sees the tool's params and result.
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.