Twitter/X

Flue 2.0 is a TypeScript agent framework powered by the @pidotdev agent harness…

Brief

Flue 2.0 is a TypeScript framework for dynamic agents (built on the @pidotdev harness) that uses React-style hooks to solve agent composability. Announced by @jilles on 2026-07-31, it follows Flue 1.0 Beta (700,000+ downloads). Hooks enable multi-step workflows, conditional tool acquisition, model upgrades, and passing metadata to tools like function arguments.

Why it matters

Flue 2.0 is a TypeScript agent framework powered by the @pidotdev agent harness; announced by @jilles on 2026-07-31 and referencing Fred (@FredKSchott). Flue 1.0 Beta (released last month) has been downloaded 700,000+ times.

Key details

  • Flue 2.0 adds React-style hooks for agent composability: enforce multi-step workflows, grant new tools once conditions are met, switch up to larger models dynamically, and pass metadata/context to tools like function arguments (reducing custom API/config needs).
Source evidence

One thing is true.
Always count on Flue.

(And Fred never misses)

fks (@FredKSchott)

Introducing Flue 2 — Build dynamic agents that evolve over time.

Flue is a TypeScript framework for building the next generation of agents, powered by the @pidotdev agent harness.

The Flue 1.0 Beta was released last month & has now been downloaded 700,000+ times. And from all of that feedback, we realized something we'd missed.

Agents have a familiar problem: composability.

How do you compose together different agent capabilities in a way that feels expressive AND maintainable, especially as you scale up complexity?

Last week, I teased: “What if React for Agents?” and yes, as you will see, the inspiration here is obvious. But UI devs and agent devs have some things in common, including the same problem that the React team solved almost a decade ago with... Hooks!

There are now things that you can do in Flue 2.0 with hooks that are just fundamentally difficult in other frameworks:

A Flue agent can enforce a multi-step workflow, earn new tools once certain conditions are met, or trade up to a bigger model when the work gets too hard.

Handling metadata and context no longer requires custom framework APIs and configuration. In Flue, you can pass data to a tool the same way you pass arguments to a function.

I'm really excited for you to try Flue 2.0 out yourself. It's a big, bold take on what agents could be capable of in the future.

Read more: flueframework.com/blog/flue-…

— https://nitter.net/FredKSchott/status/2083252640994275779#m