Flue releases 1.0 Beta with agents, workflows, and channel connectors

• Flue 1.0 Beta reorganizes the framework around three top-level primitives, with workflows for code-driven automations, agents for autonomous stateful loops, and channels for wiring those agents into Slack, GitHub, Linear, Discord, Teams, and other surfaces, according to Flue 1.0 Beta launch post.
• The release keeps Flue's model-agnostic pitch intact: the launch post describes an "open agent harness" with zero LLM lock-in and says teams can deploy anywhere.
• Durability is the real product claim here, because the launch post says Flue can recover running agents across restarts and downtime, while FredKSchott's Durable Streams reply adds that the stack is built on Durable Streams.
• Cloudflare is still the deepest runtime path, with FredKSchott's Cloudflare runtime reply saying Flue has a Cloudflare-specific runtime using Durable Objects and SQLite under the hood.

You can read the announcement post, watch the short launch walkthrough, and skim

showing that Flue nearly shipped under a different name. The launch thread also included an

and a small but useful beta note: FredKSchott's API stability reply says the 1.0 Beta surface has stabilized after a fast-moving pre-1.0 stretch.

Flue now wants teams to think in three buckets, not one generic agent abstraction. The launch post defines them like this:

• Workflows: structured background automations where application code drives the agent.
• Agents: autonomous, stateful loops where the model drives itself to finish a task.
• Channels: connectors that plug those systems into Slack, GitHub, Linear, Discord, Teams, and similar tools.

That split makes the beta more opinionated than the earlier framework pitch, and easier to scan if you are deciding whether your task is deterministic orchestration or open-ended agentic work.

The lower layer is just as important as the new API surface. ElectricSQL's post says Flue is now based on the Durable Streams protocol, while FredKSchott's later reply says it is "100% built on @DurableStreams."

On deployment, Schott's Cloudflare runtime reply says Flue has a Cloudflare-specific runtime that uses Durable Objects and SQLite for durability and recovery. another Schott reply adds that Flue uses Agent SDK internally when deployed to Cloudflare.

Two smaller details rounded out the launch day picture. First, Schott's beta reply says the API surfaces have "stabilized quite a bit" now that Flue has hit 1.0 Beta.

Second, the replies sketched early real-world usage rather than abstract demos. one Schott reply says support is a major internal use case, while another mentions interest in tightening a Sentry integration and a quick answer on workflows suggests that workflows remain the default answer for some user questions even after agents became a first-class primitive.