Packages

@flue/sdk

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

Upgrading @flue/sdk From 0.4.1 to 0.5.0

1 release in betweenevery note read

Other targets from 0.4.1Newest 0.x0.11.1Latest2.3.1
  1. 0.4.1yours
  2. 0.5.0target

Before you upgrade

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

Release by release

  1. 0.5.0

    Migration needed11 May 20266 new · 5 fixes
    • Breaking

      FlueAgent is now FlueHarness. The value returned from init() is a harness: a configured handle for model defaults, tools, sandbox, filesystem, and sessions. Rename imports/usages from FlueAgent to FlueHarness, and prefer const harness = await init(...) in agent files.

    • Breaking

      Harnesses and sessions are named, not id'd. init({ id }) is now init({ name }), defaulting to "default". The returned harness exposes .name instead of .id. harness.session(id?), harness.sessions.get/create/delete(id?), and FlueSession.id are now name-based APIs (name?, .name).

    • Breaking

      Session storage keys now include the agent instance id, harness name, and session name. Existing persisted sessions under the old two-part key shape are not migrated. Cloudflare Durable Object session history from earlier builds will not be read by this release.

    • Breaking

      Webhook responses return runId instead of requestId. Every HTTP invocation now gets a generated run_<ulid> exposed to handlers as ctx.runId. Webhook mode returns { status: 'accepted', runId }.

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.