Alternatives
Products that do what WeaveMind – AI Workflows with human-in-the-loop does
Hi! I spent 3 years evaluating LLMs for OpenAI, Anthropic, METR, and other labs. Kept running into the same problem: AI workflows break in production because there's no clean way to add human oversight, handle failures gracefully, or deploy without choosing between "all cloud" and "all self-hosted." WeaveMind is a visual workflow builder in Rust. The core idea is that humans and AI are interchangeable nodes in the same graph. When a workflow needs judgment, it pauses, notifies the team via browser extension, first responder picks it up. There's also an AI assistant that generates workflows…
- 1

- 2

- 3

- 4

- 5FA
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
- 6

- 7

- 8SM
We built a model router that plugs into coding agents (e.g. Claude Code, Codex, Cursor, etc.) and intelligently sends requests to the best model to serve them. Here's a quick demo of running it locally: https://www.youtube.com/watch?v=isKhAyivtfM. At Weave, we write most of our code with AI, and it's been getting more expensive. This came to a head when Opus 4.7 was released and, thanks to its tokenizer changes, our costs shot up. We knew we didn't need Opus for everything but we didn't want to lose out on the intelligence for the cases where you really need it. So we decided…
Jun 2026 · github.com
- 9

- 10

- 11

- 12

- 13

- 14

- 15

- 16

- 17

- 18

- 19

- 20MA
Hey HN. I'm Fabien, principal engineer, 25 years shipping production systems (Ruby, Swift, now Rust). I built Moltis because I wanted an AI assistant I could run myself, trust end to end, and make extensible in the Rust way using traits and the type system. It shares some ideas with OpenClaw (same memory approach, Pi-inspired self-extension) but is Rust-native from the ground up. The agent can create its own skills at runtime. Moltis is one Rust binary, 150k lines, ~60MB, web UI included. No Node, no Python, no runtime deps. Multi-provider LLM routing (OpenAI, local GGUF/MLX, Hugging…
Feb 2026 · moltis.org
- 21

- 22
- 23

- 24WU
Hey HN – Gregor & Magnus here again. A few months ago, we launched Browser Use (https://news.ycombinator.com/item?id=43173378), which let LLMs perform tasks in the browser using natural language prompts. It was great for one-off tasks like booking flights or finding products—but we soon realized enterprises have somewhat different needs: They typically have one workflow with dynamic variables (e.g., filling out a form and downloading a PDF) that they want to reliably run a million times without breaking. Pure LLM agents were slow, expensive, and unpredictable for these…
2025 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →