Flowise is shutting down, and names coding agents as the reason

The sunset notice carries three dated milestones. Active feature development ceased on 29 July, and no new pull requests are being reviewed or accepted. On 10 August the GitHub repository moves to public archive status: the code stays visible indefinitely, issues and pull requests lock, and the npm packages and Docker images are marked deprecated. On 31 August the core team's presence in Discord and GitHub concludes, with community moderation handed off where applicable. The source remains Apache 2.0, and the notice tells teams to fork github.com/flowiseai/flowise and maintain their own updates.

The reason given is a paragraph, not a hint. "Over the last few months, we've noticed a significant shift in how people build," the notice says. "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."

At 20:25 EDT the repository README carried no sunset notice and still documented npm install -g flowise as the quick start, so a team that only reads GitHub has not been told. And the Hacker News submission of the notice stood at 2 points with 1 comment at roughly 9 minutes when this edition read it, six days after the announcement, so this has had close to no public discussion.

Why it matters: If anything in your pipeline installs flowise from npm or pulls the Docker image, 10 August is the date those artifacts get marked deprecated and a fork becomes the only maintained path. The wider point is the vendor's own diagnosis, which is more candid than most: a company that sold visual workflow composition is saying in writing that its abstraction lost to agents that write the code, and saying so while handing the repository to whoever wants it.