Alternatives
Products that do what Willder does
AI agents coordinate. People collaborate. One memory.
- 1
- 22C
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
- 3RA
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
- 4
- 5PS
I didn't want to buy a standalone computer or repurpose a laptop to run constantly so I could maintain a system to sync my LLMs, so I built this. It's a simple overview of my system, laid out in a way easy to unpack and replicate for yourself. The project is meant to be configured individually, and uniquely, since one solution might not be what's best for another. If anything, maybe it gives you some ideas on how to implement things for your own project. Best wishes, Ryan.
28d ago · pacslate.com
- 6
- 7
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
- 8IB
Excited to share a project I’ve been building for months! Would love to receive honest feedback :) My motivation: AI is clearly going to be the interface for data. But earlier attempts (text-to-SQL, etc.) fell short — they treated it like magic. The space has matured: teams now realize that AI + data needs structure, context, and rules. So I built a product to help teams deliver “chat with data” solutions fast with full control and observability (agent tracing, quality scores, etc) — am I wrong? The product allows you to connect any LLM to any data source with centralized context…
Oct 2025 · github.com
- 9
- 10SR
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
- 11
- 12TO
2025 · github.com
- 13MC
Hi HN, I’ve been building AI agents and copilots, and kept running into a frustrating problem: they don’t fail loudly, they forget things quietly. Users re-explain preferences, agents contradict earlier responses, and context resets without any clear visibility into why. I built Memograph CLI as a debugging tool to analyze conversation transcripts and show: - what the agent forgot - where continuity broke - contradictions and repeated context - estimated token waste due to re-prompting It works locally and supports plain text or JSON transcripts. Example: $ memograph Output: Cognitive Drift…
Feb 2026
- 14HG
Most AI applications are built for individuals but work happens in groups and humans want to collaborate with both agentic AI and other teammates in the same session. We created Hybrid Groups for that purpose. In Hybrid Groups, agents join group chats as virtual team members in Slack and GitHub. They participate in group conversations, proactively contribute when needed and perform actions on behalf of individual users, like managing your calendar for meeting suggestions or updating your todo list without sharing access to your private resources to the group. The project is open-source at…
2025 · youtube.com
- 15GY
I submitted this earlier but it didn’t get any traction. But it’s blowing up on Twitter, so I figured I would give it another shot here. The system is quick and easy to setup and works surprisingly well. And it’s not just a fun gimmick; it’s now a core part of my workflow.
Nov 2025 · github.com
- 16CA
May 2026 · oacp.dev
- 17MA
Hello there HN I experimented with agentic coding recently and I felt the need to track more contextual data by project. Also I felt the need to be able to go beyond the 1D chat to communicate with agents. So I created a local document memory, that is discoverable by agents themselves. The CLI is designed to be easy to pick up by agents. It allows humans to collaborate too by reading / searching / editing documents in the store. I have a Mac native GUI in the review process, I hope it will show up in the App Store soon. You can try it easily, instructions here:…
Jun 2026 · metabrain.eu
- 18WB
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
- 19
- 20IB
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
- 21BA
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
- 22
- 23
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
- 24WM
May 2026 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →