Alternatives
Products that do what A library of tree search algorithms for AI agents does
Hi HN, I built this to address what I see as the fundamental problem with ReAct-style agents: compounding errors. Even a small mistake made early enough in the loop can snowball and ruin the final output. But with search, agents can look multiple steps ahead and backtrack before committing to a particular trajectory. This has already been shown in a few papers to help agents avoid mistakes and boost overall task performance, but there's no easy way to actually build these kinds of agents. So that's why I made this framework. I believe search will eventually become table stakes for building…
- 1
- 2IB
Hey HN, I've made a groundbreaking discovery: procrastination can lead to questionable projects! While avoiding real work, I somehow created a directory of 130+ AI agents and frameworks. It's like I tried to organize a robot party and everyone showed up. What's inside: - A list of AI agents - Frameworks to build more agents So, HN, before I spiral into an existential crisis: did I accidentally create something useful, or should I go touch grass? P.S. If this somehow becomes the next big thing, I promise to pretend it was intentional all along.
2024 · aiagentsdirectory.com
- 3AA
Hi HN, Over Thanksgiving weekend I wanted to build an AI agent. As a design exercise, I wrote it as a set of React components. The component model made it easier to reason about the moving parts, composability was straightforward (e.g., reusing agents/tools), and hooks/state felt like a reasonable way to model behavior that changes over time. As I kept experimenting, I realized I was more interested in the framework (and it was a good excuse to explore React’s internals) than in the agent I originally planned, so I built this project instead. In this framework: - Agents are React…
Dec 2025 · github.com
- 4SR
Hello all, I'm a software developer. Over the last few months more and more of my work has turned into using coding agents instead of typing the whole code myself. Usually a few claude sessions at once, sometimes codex, one per feature or per revealed bug. I ran them in a split terminal for a few weeks, and quickly spotted two main problems. The first is that I couldn't easily tell which agent was stuck waiting on me and which was still working, so I'd cycle through sessions and checking on them. The second one: agents sharing a single branch step on each other. Two of them could be editing…
Jul 2026 · shikigami.dev
- 5MA
We built meta-agent: an open-source library that automatically and continuously improves agent harnesses from production traces. Point it at an existing agent, a stream of unlabeled production traces, and a small labeled holdout set. An LLM judge scores unlabeled production traces as they stream. A proposer reads failed traces and writes one targeted harness update at a time, such as changes to prompts, hooks, tools, or subagents. The update is kept only if it improves holdout accuracy. On tau-bench v3 airline, meta-agent improved holdout accuracy from 67% to 87%. We open-sourced meta-agent.…
Apr 2026 · github.com
- 6WB
Humans compete to improve their AI agents on benchmarks. But what if agents could collaborate and compete on their own? We built Hive, a crowdsourced platform where agents can evolve solutions together. One agent begins to tackle a task, iteratively improving its code. Then other agents join. They read each other’s runs, fork the best ideas, propose new ones, and push the solution forward together. We already have agents working on benchmarks like Tau2-Bench, Terminal-Bench, and ARC-AGI-2, with more tasks coming soon. We also support the new OpenAI Parameter Golf Challenge, and you can…
Mar 2026 · hive.rllm-project.com
- 7IB
Hi HN, I'm the creator of this project. For the past months, I've been working on building an AI agent that could move beyond simple generation and tackle inventive challenges autonomously. The core idea was to create a system with a "metacognitive loop"—the ability to recognize when it's stuck on a fundamental problem and then launch a sub-mission to solve that specific bottleneck before continuing. The linked article is a deeper introduction to the system's architecture and a snapshot from a recent run. I tried to design it to be evidence-grounded and self-critical to avoid the pitfalls of…
2025 · robw1se.substack.com
- 88B
Hey all, Justin here. I previously built Phind, the AI search engine for developers. One of the biggest problems we had there was figuring out what went wrong with bad searches. We had tons of searches per day, but less than 1% of users gave any explicit feedback. So we were either manually digging through searches or making general system improvements and hoping they helped. This problem gets harder with agents. Traces are longer and more complex. It takes more effort to review them, so I'm building a tool that lets you analyze LLM outputs directly to help developers of LLM apps and agents…
Jan 2026 · trails-red.vercel.app
- 9IM
Hi HN! Solo developer here. 10 days ago, I started building this after spending countless hours copying/pasting marketing sections and fighting to keep them consistent with our design system. I wondered: "What if AI could understand our design system and generate React components that actually match it?" Current progress (10 days in): - Can generate hero sections that follow your design tokens - Uses your actual component variants and styles - Works with Next.js, Tailwind, shadcn/ui It's very early days, but I'm excited to share it with other devs who: - Are tired of rebuilding…
2024 · robustlaunch.com
- 10AC
Hi HN, I’m the author of agent-contracts, a Python library that explores a contract-based approach to structuring LangGraph agents. When building larger LangGraph-based systems, I kept running into the same issues: - node responsibilities becoming implicit - state dependencies spreading across the graph - routing logic getting harder to reason about - refactoring feeling increasingly risky agent-contracts is an attempt to make these boundaries explicit. Each node declares a contract that describes: - which parts of the state it reads and writes - what external services it depends on - when…
Jan 2026 · github.com
- 11RA
Hi HN folks, I have been building AI agents for quite some time now. The shift has gone from LLM + Tools → LLM Workflows → Agent + Tools + Memory, and now we are finally seeing true agency emerge: agents as systems composed of tools, command-line access, fine-grained system capabilities, and memory. This way of building agents is powerful, and I believe it is here to stay. But the real question is: are the systems powering these agents ready for that future? I do not think so. Using Docker for a single agent is not going to scale well, because agents need to be lightweight and fast. LLMs…
Mar 2026 · github.com
- 12
An agent that remembers across sessions can keep its memory as curated markdown files, as an auto-mined structured store, or as trained experience.
22d ago · pinglin.tw
- 13
We built an open sourced coordination layer for AI agents working on the same repository. Detects work duplication and design conflicts early
9d ago · twing.dev
- 14AT
Apr 2026 · github.com
- 15AA
We’ve published a set of open-source reference implementations on how to build production-grade Agentic AI applications on AWS. What’s in the repo: • Agentic RAG, memory, and planning workflows with LangGraph & CrewAI • Strands-based flows with observability using OTEL & Arize • Evaluation with LLM-as-judge and cost/performance regressions • Built with Bedrock, S3, Step Functions, and more GitHub: https://github.com/aws-samples/sample-agentic-frameworks-on-... Would love your thoughts — feedback, issues, and stars welcome!
2025 · github.com
- 16AF
I’ve been working on a temporal database for agents that combines graphs, tables, and compute. While building it, I ended up needing an agent framework that could handle both simple tool-use tasks and more graph-based execution, so I pulled that out into a separate project, Agent Forge. Agent Forge uses a two-tier execution model: * a heuristic router decides whether a request is simple or complex * simple requests go through a lightweight agent loop with a single system prompt and tool-calling loop * more complex requests can use memory retrieval, reflection constraints, tree search, and…
Mar 2026 · github.com
- 17FA
Founder here. I built NEO, an AI agent designed specifically for AI and ML engineering workflows, after repeatedly hitting the same wall with existing tools: they work for short, linear tasks, but fall apart once workflows become long-running, stateful, and feedback-driven. In real ML work, you don’t just generate code and move on. You explore data, train models, evaluate results, adjust assumptions, rerun experiments, compare metrics, generate artifacts, and iterate; often over hours or days. Most modern coding agents already go beyond single prompts. They can plan steps, write files, run…
Jan 2026 · marketplace.visualstudio.com
- 18BC
We are a small group of undergrads interested in building human in the loop coding agents. We dream of a world where building complex agent workflows feels as simple and creative as playing with legos. When we were building stuff we needed a tool that made it easy to try out different code embedding models so that we could see which ones worked best in different scenarios and understand their strengths and weaknesses. So to speed that process up we made PurpleSearch an 'instant' search engine for your local codebases. This tool lets you quickly deploy any open source embedding model on…
2025
- 19HA
Hi HN, I am Umer. I recently built an experimental framework called HyperFlow to explore the idea of self-improving AI agents. Usually, when an agent fails a task, we developers step in to manually tweak the prompt or adjust the code logic. I wanted to see if an agent could automate its own improvement loop. Built on LangChain and LangGraph, HyperFlow uses two agents: - A TaskAgent that solves the domain problem. - A MetaAgent that acts as the improver. The MetaAgent looks at the TaskAgent's evaluation logs, rewrites the underlying Python code, tools, and prompt files, and then tests the new…
Apr 2026
- 20AB
Hi HN, Zidan here. I’ve been experimenting with AI-assisted debugging and noticed a recurring gap: most tools optimize for agent-led exploration (ex: giving claude code a browser to click around and try to reproduce an issue). But in many cases, I've already found the bug myself. What I actually want is a way to hand the agent the exact context I just saw - without retyping steps, copying logs, or hoping it can reproduce the behavior. So we built FlowLens, an open-source MCP server + Chrome extension that captures browser context and lets coding agents inspect it as structured, queryable…
Nov 2025 · github.com
- 21
Hey HN! We built https://keenable.ai, a different web search API for AI agents. Keenable searches our own 100B+ page index. We are focused on low cost and latency (p95 <250ms from us-east). We don’t believe in benchmaxxing, so we open-sourced our internal benchmarking suite, NEEDLE (available at https://keenableai.github.io/needle): a live benchmark that compares Keenable with other search APIs on fresh agent-like queries. I spent seven years at Amazon as a scientist working on web grounding for Alexa/AGI, and my co-founder Andrey previously led search at…
12d ago · keenable.ai
- 22IB
The main goal of this was to be able to not just run multiple Claude Code sessions at once, but actually manage them and keep track of what I was doing. Sometimes this is multiple attempts on the same task, sometimes I work several tasks at once. Really I was just sick of twiddling my thumbs waiting for the coding agent to finish, and I wanted it to be easy to work on/review/test another change while I waited.
2025 · github.com
- 23RA
Hi HN! Sean from MindStudio here. I wanted to share something we've been working on that I think introduces some new ideas into the "AI coding agent" space. Remy is an AI agent that builds full-stack TypeScript apps from a spec written in a new flavor of annotated markdown. The spec has two layers: prose describing what the app does, and annotations that carry the technical precision (data types, edge cases, validation rules, code snippets). The agent then "compiles" this into code: backend methods, typed schemas, frontends, test scenarios, and everything else are derived artifacts of the…
Apr 2026 · remy.msagent.ai
- 24BA
I'm one of the creators of The Edge Agent (TEA). We built this because we needed a way to deploy agents that was verifiable and robust enough for production/edge cases, moving away from loose scripts. The architecture aims to solve critical gaps in deterministic orchestration identified by *Prof. Claudionor Coelho Jr. (Stanford alum, ML/DL Faculty at Santa Clara Univ., and Senior Fellow for AI at Majestic Labs)* during our work on the Kiroku project. *Key Technical Features:* * *Neurosymbolic Native:* We integrated Prolog to logically validate LLM outputs. This combines neural…
Jan 2026 · fabceolin.github.io
Ranked by how close each launch is in meaning, then by votes. Refine with a description →