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.
Flowise is shutting down
21–30 of 49 posts
Re: Flowise is shutting down
#22I remember Flowise app being well-intended but bad. I evaluated the self-hosted version to be used as a component in an internal tool so non-technical people can tweak their prompt chains without writing code. As far as I remember:
1. it became increasingly slow as I added flows (felt like a O(n^2) ish bottleneck)
2. There were many bugs and bad UX
3. the flow variable system was underbaked and underdocumented
4. feature gaps
I decided I was probably not the target audience for their app and moved on.
Re: Flowise is shutting down
#23Disclosure 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 th…
I've been pondering this recently. There have been loads of trivial automation targets throughout the economy for years but they haven't really been fixed, despite being a small Python script (things like converting one csv file to another). Why do we suppose LLMs are suddenly going to fix them? I guess the overhead is possibly lower now, but I suspect there are other barriers to automation that most techies can't comprehend.
Re: Flowise is shutting down
#24>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. The typical rigid workflow low code approach quickly hits the limit when it comes to complexity.
Their front page says ‘design agents visually’ so their target market was less skilled devs/non devs.
So not sure why they are giving the reason if closer as cli related when low code and cli are different markets.
Re: Flowise is shutting down
#25>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. The typical rigid workflow low code approach quickly hits the limit when it comes to complexity. Their front page says ‘design agents visually’ so their target m…
I feel like there's a fundamental shift in the user interface that's causing this. People are starting to expect an "agentic interface" - that they are able to give kinda vague inputs and nudge things to work in a way they like, over the traditional experience of having increased clarity at the cost of increased setup (drag and drop, many UI first interfaces, etc).
I was editing a google doc yesterday and found it annoying that i had to find the "link" option from the context menu instead of just saying "turn links into links" and moving on.
This imo impacts everyone, regardless of how developer-ey you are. Perhaps non-devs expect a "friendlier"/more "agentic" interface now? Don't have the right vocabulary to explain.
Re: Flowise is shutting down
#26There 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 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 av…
I‘m wondering what that means for products like retool. I used it a lot in the past for internal tooling but it’s now a a segment where coding agents are likely to be a better fit, and the AI integration within retool is messy compared to just letting Claude create the web app
Re: Flowise is shutting down
#27Flowise was acquired by workday, so I'd take this with a grain of salt.
However, I agree with the reasoning. I don't see a future for visual workflow builders. They are used to define plumbings that can be defined by a 50 line python script.
A non-technical user does not need to draw this workflow. They can just ask an agent to write that code for them, to debug it, to visualize it. All workflow builders now have an AI chat where you ask the agent to build the flow for you. Why not skip the flow part?
I'm pretty biased though since that's the thesis behind what I am building.
Re: Flowise is shutting down
#28Whilst the UI provides visibility and guardrails, it also reduces flexibility. But now with LLM coding agents, it often gets in the way. Working with text/code is easier.
Re: Flowise is shutting down
#29> The typical rigid workflow low code approach quickly hits the limit when it comes to complexity.
IMO rigid workflows guarantee deterministic and auditable behaviour. It's extremely important when things go wrong.
Re: Flowise is shutting down
#30>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. The typical rigid workflow low code approach quickly hits the limit when it comes to complexity. Their front page says ‘design agents visually’ so their target m…
Claude Code isn't necessarily command-line, the desktop app supports it.