@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
- 6
- changes to make
- 0
- advisories fixed
- 6
- new
- 5
- fixes
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
- Breaking
FlueAgentis nowFlueHarness. The value returned frominit()is a harness: a configured handle for model defaults, tools, sandbox, filesystem, and sessions. Rename imports/usages fromFlueAgenttoFlueHarness, and preferconst harness = await init(...)in agent files. - Breaking
Harnesses and sessions are named, not id'd.
init({ id })is nowinit({ name }), defaulting to"default". The returned harness exposes.nameinstead of.id.harness.session(id?),harness.sessions.get/create/delete(id?), andFlueSession.idare 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
runIdinstead ofrequestId. Every HTTP invocation now gets a generatedrun_<ulid>exposed to handlers asctx.runId. Webhook mode returns{ status: 'accepted', runId }.
- Breaking
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.