Packages

@flue/cli

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

Upgrading @flue/cli From 0.7.1 to 0.8.0

1 release in betweenevery note read

Other targets from 0.7.1Newest 0.x0.11.1Latest2.3.1
  1. 0.7.1yours
  2. 0.8.0target

Before you upgrade

Tick each one off as you go
  • Breaking0.8.0
  • Breaking0.8.0
  • Breaking0.8.0
  • Breaking0.8.0
  • Breaking0.8.0

Release by release

  1. 0.8.0

    Migration needed27 May 20265 new · 2 fixes
    • Breaking

      Applications must adopt the agent/workflow split. Move one-shot request/result modules from agents/ to workflows/; long-lived agent modules now default-export createAgent(...). Workflows create harnesses with init(agent) rather than inline init({ ... }) configuration.

    • Breaking

      Routing and run semantics changed. Public HTTP and WebSocket exposure is declared through route and websocket middleware exports. Runs, /runs, and flue logs now describe workflows only; direct or dispatched agent interactions correlate by instance, session, operation, and dispatchId instead of runId.

    • Breaking

      Roles and older agent definitions were replaced. Migrate roles and task({ role }) to named defineAgentProfile(...) subagents and task({ agent }); migrate reusable agent definitions to profiles and ToolDef imports to ToolDefinition.

    • Breaking

      Build and Cloudflare configuration changed. Node and Cloudflare builds now use a shared Vite graph; Cloudflare development follows .dev.vars / .env and CLOUDFLARE_ENV conventions. Cloudflare workflows now receive per-workflow Durable Object bindings, so review generated Wrangler configuration when upgrading.

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.