Alternatives
Products that do what Flowneer does
A Tiny TS flow builder for stateful LLM agents
- 1
- 2
- 3
Build AI agents that respond with UI instead of text
Feb 2026 · thesys.dev
- 4
- 5
- 6
- 7FA
I think graph is a wrong abstraction for building AI agents. Just look at how incredibly hard it is to make routing using LangGraph - conditional edges are a mess. I built Laminar Flow to solve a common frustration with traditional workflow engines - the rigid need to predefine all node connections. Instead of static DAGs, Flow uses a dynamic task queue system that lets workflows evolve at runtime. Flow is built on 3 core principles: * Concurrent Execution - Tasks run in parallel automatically * Dynamic Scheduling - Tasks can schedule new tasks at runtime * Smart Dependencies - Tasks can…
2024 · github.com
- 8NO
Hello HN! The day has finally come to stop adding features and start sharing what I've been building the last 5-6 months. It's a bit of CrewAI, OpenDevon, LangFuse/Cloud all in one, providing devs who prefer TypeScript an integrated framework thats provides a lot out of the box to start experimenting and building agents with. It started after peeking at the LangChain docs a few times and never liking the example code. I began experimenting with automating a simple Jira request from the engineering team to add an index to one of our Google Spanner databases (for context I'm the…
2024 · github.com
- 9
- 10TL
2023 · tinyllms.vercel.app
- 11
- 12
- 132C
Single-agent LLMs suck at long-running complex tasks. We’ve open-sourced a multi-agent orchestrator that we’ve been using to handle long-running LLM tasks. We found that single LLM agents tend to stall, loop, or generate non-compiling code, so we built a harness for agents to coordinate over shared context while work is in progress. How it works: 1. Orchestrator agent that manages task decomposition 2. Sub-agents for parallel work 3. Subscriptions to task state and progress 4. Real-time sharing of intermediate discoveries between agents We tested this on a Putnam-level math problem, but the…
Feb 2026 · github.com
- 14TO
2025 · github.com
- 15ZD
Hey HN! We just released a new library for building LLM-powered applications: @axflow/models. It is part of a larger suite of libraries we're developing for TypeScript developers working with generative AI. This library provides the simplest APIs for 1) invoking the most popular LLM and embedding models (openai, anthropic, cohere, huggingface, etc.) 2) streaming LLM responses to clients, including augmenting the streams with additional arbitrary data and 3) building client-side applications with React hooks. @axflow/models has zero dependencies and is built using only the…
2023 · docs.axflow.dev
- 16PA
Hey HN, Gabe and Alexander here from Hatchet. Today we're releasing Pickaxe, a Typescript library to build AI agents which are scalable and fault-tolerant. Here's a demo: https://github.com/user-attachments/assets/b28fc406-f501-442... Pickaxe provides a simple set of primitives for building agents which can automatically checkpoint their state and suspend or resume processing (also known as durable execution) while waiting for external events (like a human in the loop). The library is based on common patterns we've seen when helping Hatchet users run millions of…
2025 · github.com
- 17AR
So, it feels like this should exist. But I couldn't find it. So I tried to build it. Agentflow lets you run complex LLM workflows from a simple JSON file. This can be as little as a list of tasks. Tasks can include variables, so you can reuse workflows for different outputs by providing different variable values. They can also include custom functions, so you can go beyond text generation to do anything you want to write a function for. Someone might say: "Why not just use ChatGPT?" Among other reasons, I'd say that you can't template a workflow with ChatGPT, trigger it with different…
2023 · github.com
- 18UL
Recently featured in a LangChain blog https://blog.langchain.dev/empowering-development-with-flowt... , use LLMs to construct an API first runnable workflow with an IDE experience.
2024 · github.com
- 19
- 20IB
Hi, I have been building small AI Agents for quite some time now using various frameworks and one thing that always bugged me was that iterating on small things like prompts, flows, tools etc always took a code change + deployment of the app. While the prompt part can be solved with Langfuse I haven't found a good way to keep the flow management remote (and open source). Lately I have been working with Genkit (https://github.com/firebase/genkit) and love how modular it is. So I thought why not build a UI builder on top of that that can handle simple flows, prompts and…
Sep 2025
- 21IM
Every time I wanted to use LLMs in my existing pipelines the integration was very bloated, complex, and too slow. This is why I created a lightweight library that works just like scikit-learn, the flow generally follows a pipeline-like structure where you “fit” (learn) a skill from sample data or an instruction set, then “predict” (apply the skill) to new data, returning structured results. High-Level Concept Flow Your Data --> Load Skill / Learn Skill --> Create Tasks --> Run Tasks --> Structured Results --> Downstream Steps And the bast part: Every step can be saved and reused as…
2025 · github.com
- 22NC
There's been some interesting work lately with BrowserAI (runs LLMs in the browser using WebGPU) enabling local, private AI processing. Now, the team has released BrowserAgent - a no-code tool built on top of it. BrowserAgent lets you create custom AI workflows using a drag-and-drop interface, all within your browser. This means personalized web summarizers, research assistants, or content generators can all run locally with no cloud costs and full data privacy. Check it out here - https://browseragent.dev Key features include: - No-Code Workflow Builder: Design custom AI agents…
2025 · browseragent.dev
- 23CM
Hey HN, I've been building AutoAgents, an AI agent framework in Rust. Today I'm sharing a feature I haven't seen done well elsewhere: composable middleware layers for LLM inference pipelines. The problem Every agent framework lets you swap LLM providers. Almost none of them give you a structured way to enforce safety, caching, or data sanitization in the inference path itself. You end up with guardrails as application-level if-statements, caching bolted on as a separate service, and PII handling as a "we'll add it later" TODO that never ships. This gets worse with local models. Cloud APIs…
Mar 2026 · github.com
- 24EA
2025 · enginelabs.ai
Ranked by how close each launch is in meaning, then by votes. Refine with a description →