Rendered at 05:17:31 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
ashu1461 3 hours ago [-]
There is something about agent workflow builders not gaining as much traction as they could have. Open AI also launched something in house and they are also shutting it down
OpenAI is deprecating Agent Builder. Existing users can continue using it during the transition window, and the product is scheduled to shut down on November 30, 2026. ChatKit remains available. See the deprecations page for the current timeline.
juancn 3 hours ago [-]
I think it's the cost (both tokens and initial setup and debugging the workflow).
It's really easy to spend a gazillion tokens by mistake and the resulting workflows are still probabilistic and open for abuse or failure.
Maybe it's too soon, we need more time to figure out what works and what doesn't.
We're still looking for the right balance for when a probabilistic solution (i.e AI) works and when we need a deterministic one (classic software).
ashu1461 2 hours ago [-]
Correct and I think for non technical folks just creating pure ai agents is much easier than creating these workflows which can be harder to test as well.
itake 2 hours ago [-]
The problem that workflow engines solve (configurable code) is just better solve with agents just maintaining the code.
2 years ago (during the agentic workflow boom) prompting was annoying and tedious. Context was small, harnesses were weak. You needed to string along multiple complex prompts to get anything done.
Now, you can give an agent 50+ tasks and it will churn through them.
taoh 1 hours ago [-]
"Over the last few months, we've noticed a significant shift in how people build. As AI models become more capable at reasoning, we've noticed that developers are increasingly relying on new coding agents such as Claude Code/OpenClaw to handle complex tasks." is true when your primary users are developers. But no-code workflow is still valuable at scenarios where determinism is required.
I'm building an agentic compliance platform where every procedure needs to follow company policies and operated on the rigid plan, but the procedure itself is different for every customer. Coding agents could in principle generate the necessary workflow for each company, but they need to integrate with millions of other applications in the company, easy to review and modify.
We built our own workflow builder because every other existing solution is too complicated and doesn't meet compliance requirements. The workflow builder itself was coded by Claude, and it's working wonderfully.
So flowise's shutdown is because their business is targeting a specific sector which doesn't need it anymore, not because workflow builder itself is not useful.
Trying to make an harness and not falling behind with how fast those frontier model evolve is hard. We've built our own harness to make games, but it became obsolete as soon as a new model dropped. Gave up and now just letting user use whatever harness they want on their side.
cebert 3 hours ago [-]
I’ve never heard of this product before today, but their website made it look like a nice visual tool. It’s too bad they didn’t make it.
whycombinetor 3 hours ago [-]
"Visual graph editor for AI workflows" seems like an extremely saturated market (Langflow, n8n). Consolidation seems natural as the agent engineering industry matures.
maxdo 2 hours ago [-]
as a person who spent years building flow.ai before flowise.ai, i'd say drag n drop ui was dead on arrival it works for a set of very hand picked cusomers , the rest were in a weird spot between people who can code( and think accordingly ) and don't.
ProAm 1 hours ago [-]
One AI company down, 999 to go.
behnamoh 2 hours ago [-]
It lacked so many features that n8n and Langflow offered, so I'm not sad about it, but it was the first visual agentic workflow builder that I tried and I wish they could make it somehow.
Hey, look on the bright side. You were able to ride the ai hype and made some money. We all knew these tools wouldn't last.
llmgraph 5 hours ago [-]
Disclosure up front: I build LLMGraph (llmgraph.ai), a hosted product in the same category, so I have a horse in this race.
The interesting part of the announcement is the stated reason: "developers are increasingly relying on new coding agents" and "rigid workflow low code approach quickly hits the limit when it comes to complexity." I think that's half right. Coding agents are clearly eating the developer end of this market. But a lot of Flowise usage was never developers; it was teams who wanted to design an LLM pipeline visually, hand it to a non-engineer to tweak prompts, and deploy it without owning infrastructure. That need didn't go away this week, and telling those users to fork and maintain a large TypeScript codebase themselves is not a real answer for them.
For anyone running Flowise in production, the practical decision is fork-and-maintain versus migrating somewhere maintained. Forking is a bigger commitment than it sounds: you own dependency updates, security patches, and model API churn indefinitely, and the contributor community that used to absorb that work is dispersing. Worth being honest with yourself about whether your team will actually do that maintenance before the first CVE forces the question.
https://developers.openai.com/api/docs/guides/agent-builder
OpenAI is deprecating Agent Builder. Existing users can continue using it during the transition window, and the product is scheduled to shut down on November 30, 2026. ChatKit remains available. See the deprecations page for the current timeline.
It's really easy to spend a gazillion tokens by mistake and the resulting workflows are still probabilistic and open for abuse or failure.
Maybe it's too soon, we need more time to figure out what works and what doesn't.
We're still looking for the right balance for when a probabilistic solution (i.e AI) works and when we need a deterministic one (classic software).
2 years ago (during the agentic workflow boom) prompting was annoying and tedious. Context was small, harnesses were weak. You needed to string along multiple complex prompts to get anything done.
Now, you can give an agent 50+ tasks and it will churn through them.
I'm building an agentic compliance platform where every procedure needs to follow company policies and operated on the rigid plan, but the procedure itself is different for every customer. Coding agents could in principle generate the necessary workflow for each company, but they need to integrate with millions of other applications in the company, easy to review and modify.
We built our own workflow builder because every other existing solution is too complicated and doesn't meet compliance requirements. The workflow builder itself was coded by Claude, and it's working wonderfully.
So flowise's shutdown is because their business is targeting a specific sector which doesn't need it anymore, not because workflow builder itself is not useful.
The fact is, there's not as much need for drag-n-drop low code tools anymore. At least I don't have much need.
At the time, they posted "Flowise isn’t going anywhere, we’re doubling down. In fact, we’re only just getting started!" [2]
I wonder if "keep the platform running for >= 1 year post-acquisition" was part of the terms! Ah well, another one for Our Incredible Journey [3]...
[1] https://newsroom.workday.com/2025-08-14-Workday-Acquires-Flo...
[2] https://www.linkedin.com/posts/flowiseai_were-thrilled-to-sh...
[3] https://ourincrediblejourney.tumblr.com/
The interesting part of the announcement is the stated reason: "developers are increasingly relying on new coding agents" and "rigid workflow low code approach quickly hits the limit when it comes to complexity." I think that's half right. Coding agents are clearly eating the developer end of this market. But a lot of Flowise usage was never developers; it was teams who wanted to design an LLM pipeline visually, hand it to a non-engineer to tweak prompts, and deploy it without owning infrastructure. That need didn't go away this week, and telling those users to fork and maintain a large TypeScript codebase themselves is not a real answer for them.
For anyone running Flowise in production, the practical decision is fork-and-maintain versus migrating somewhere maintained. Forking is a bigger commitment than it sounds: you own dependency updates, security patches, and model API churn indefinitely, and the contributor community that used to absorb that work is dispersing. Worth being honest with yourself about whether your team will actually do that maintenance before the first CVE forces the question.