Alternatives
Products that do what Agentflow – Run Complex LLM Workflows from Simple JSON does
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…
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
Actionable & predictive workflow b/t Salesforce and Slack
2017
- 11
- 12
- 13
- 14
- 15FA
LLM agents rely on tool calls — but tool responses are huge. Gmail, CRMs, and APIs return bloated JSON LLMs choke on large responses You only need 2–3 fields, but frameworks give you zero control Toolflow is an AI-native framework to fix this: * Filter tool responses before they hit the LLM * Context modes: `minimal`, `full`, `custom`, or `ai` * Composable TypeScript tool registry GitHub: [https://github.com/dksingh1997/toolflow](https://github.com/dksingh1997/toolflow) Would love feedback — especially from those building with LLMs in production.
2025 · github.com
- 16LF
Hey HN, I built SWE-Kit, LLM toolkit (Function callable tools) which makes building agents specialised in coding like Devin very easy. I noticed a typical pattern while building local agents: creating & perfecting LLM tools to interact with system or codebase was the repeated and time-consuming. We created a layer that simplifies building agents that can interact with code, file system, git, shell and allows you to quickly solve for a wide variety of coding agent use cases. Aren’t there open coding agents already? Well, yes, but most folks would want to solve their specific use case like a…
2024 · swekit.dev
- 17CK
Hi HN, for quite some time I've been thinking how LLMs are missing the knowledge base, where I can dump CSVs, PDFs, and most important, inline web app. running on Claude Code (bring your own agent) with agents with heartbeats and jobs https://runcabinet.com It runs locally and is installable via npm. GitHub (open source): https://github.com/hilash/cabinet This is still very early. I put the first version together quickly after seeing a post by Andrej Karpathy about LLM knowledge bases, which matched closely with what I’d been building. Some people have already…
Apr 2026 · runcabinet.com
- 18
- 19IM
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
- 20
- 21PO
Hi HN, We are excited to share patchwork - an open-source CLI for dev chore automation that you can use with your LLM of choice. Dev Teams can orchestrate custom workflows (called ‘patchflows’) using a combination of reusable steps and prompt templates to fix vulnerabilities, upgrade breaking dependencies, generate documentation, and more. We built scanning tools in the past, and saw how overwhelmed developers get with their DevSecOps pipelines. LLMs have the potential to help - but there is a need for an 'outer-loop' solution that can be customized to accommodate the processes, priorities,…
2024 · github.com
- 22AY
operator23 lets non-technical operators describe a workflow in plain English and run it across their tool stack, hubspot, apollo, monday, google drive and others. no builder, no if-then config, just a description and a review step before anything runs. We talked to marketing ops people recently to validate whether we are solving the right problems. Three things came up every single time. Setup complexity. People are not afraid of automation in theory. They are afraid of spending two hours configuring conditions and field mappings, only to have something silently misroute. The config layer is…
Mar 2026 · operator23.com
- 23
Local-first notebooks for executable LLM workflows.
Jul 2026 · icc-go.com
- 24CM
I've been vibe-coding tools to automate chunks of my consulting work, fell down a rabbit hole, and started building actual products. Suddenly I'm in a world of unknown-unknowns and known-unknowns. One of the bigger things to solve was understanding code the LLM generated that I didn't fully grasp. What does it touch? What reads and writes where? Is the auth path where I think it is? So I built codeflowmap. Point it at a repo and it maps the dependency and call graph, then surfaces the read / write / auth paths between files and functions. Connect a local model (Ollama) or any…
Jun 2026 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →