Just Shipped: Flue 1.0 Beta
Flue is the TypeScript framework for building the next generation of agents, designed around an open agent harness with zero LLM lock-in. It’s like Astro, for agents.
Flue 1.0 has been redesigned around three core primitives:
🔁 Workflows — structured automations designed for background work, where your code drives the agent from start to finish.
🧭 Agents (New!) — autonomous, stateful loops where the model drives itself to complete a given task.
📡 Channels (New!) — connect agents to Slack, GitHub, Linear, Discord, Teams, and more. Flue handles the boilerplate for you.
Everything shares the same durable foundation, powered internally by Pi, Vite, and Durable Streams. Deploy anywhere, use any LLM, and recover running agents across restarts and downtime.
We’ve talked to a lot of teams building agents, and keep hearing the same thing: getting to production is hard work. We built Flue to help change that.
Flue 1.0 Beta is available today. Give it a try and let me know what you think!
/grill-with-docs skill by @mattpocockuk is honestly game changer. I've never reached so far in building something from scratch with AI.
Constantly letting AI ask you questions about next steps, business requirements, completeness .. it is remarkable.
I like the GitHub copilot's agent flow of asking to keep/undo the code. Direct modification of large interdependent code is just foolish for serious development. I still can't trust the code written by AI.
I'm happy to be a little slower rather than shipping slop.
Reactive programming code snippets feels icky and definitely unconventional, but boy it works like magic. It's so hard to make end to end streams non-blocking.
I always feel tempted to just manually subscribe and process it.
Trying to build a stock watch and analysis engine with notification (telegram) for my own usage.
I'm investing some time and energy to understand the virtual actor pattern using Dapr for execution and scheduling.
Let's see how it goes.
@prynsshh@Hi_Mrinal To delegate push notifications or email events, we also heavily use this pattern, even in monolithic systems :)
Recently I made a notification demo using a poll based outbox pattern + sse for updates on UI, using Golang and React. Repo - https://t.co/ssPRjdIaUe
donno what da heck's new in nextjs, I left that boat a year ago.
Now I completely believe in SPA + non js backend.
With proper client side caching and revalidation, apps feel much faster than needed.