Alternatives
Products that do what EasyAgents does
I solved multi-agent AI orchestration with a for loop.
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9GF
hi guys. been working on something i think is fundamentally missing in today's workflow with ai agents. vcs. i find myself struggling with questions that agents can't answer like "why did you do it?", "when did u delete this folder? why?", etc. or trying to /rewind (after a /compact...) or basically `bisect` to find when and why something was done by the agent in the current / previous session. just like git did for code, i think we are the same core capabilities with ai agents so... i developed an open source solution for that (currently supporting claude code) would love to…
May 2026 · github.com
- 102C
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
- 11
- 12
- 13RM
RunAgent eliminates the complexity of AI agent deployment across different frameworks and languages. Today's developers face deployment nightmares with fragmented frameworks (LlamaIndex, LangChain, LangGraph, CrewAI, Letta, Agno, etc.) each requiring different deployment processes, creating unnecessary friction. The Solution: Like MCP (Model Context Protocol), RunAgent provides a standardized approach to agent deployment. Developers simply provide a config file and their agent code - RunAgent handles the rest with REST API and WebSocket (Streaming and non streaming). Our open-source platform…
2025 · github.com
- 14RA
Hi, founder of Okteto here! We’ve been experimenting with AI agents in our workflows at Okteto. Running them locally worked at first, but quickly became painful. git worktrees, multiple terminals, and messy context switches slowed us down. So we built Agent Fleets: ephemeral, fully managed environments for AI agents, built on top of Okteto’s development platform. Each agent runs in its own containerized environment on your infrastructure, with the services, tools, and policies it needs. You can spin up agents with a single click or API call. No local setup. No git worktrees. The beta…
2025 · okteto.com
- 15CA
I built this because I was tired of creating pull requests in 20 repositories just to change a single line of workflow job version. With Infra as AI, just mention the change. Agents work on all repos in parallel, read the docs, make a bunch of PRs and fill in the description. You can see the demo of the actual dashboard in the landing. Let me know your thoughts :) It means a lot to me!
Sep 2025 · infrastructureas.ai
- 16
- 17
- 181D
We just open-sourced the internal system we built at Assembled for running coding agents as a team. Coding agents worked well for individual engineers, but the surrounding workflow was a bit of a mess. We generally found that many engineers had different MCP connections and context for their agents, personal automations running that other people couldn’t access, and very little introspection for what a human’s input into the coding agent looked like. So we built an internal system that converted coding agents into shared team infrastructure. The system runs Codex, Claude Code, OpenCode, and…
Jun 2026
- 19AD
I’ve been tinkering with what a “multi-agent IDE” should look like if your day-to-day workflow is mostly in terminal (Claude Code, OpenAI Codex, etc.). The more I played with it, the more it collapsed into three fundamentals: * A good TUI: Terminal is the center stage, with other stuff (CodeEdit, Diff, Review) baked on the side. I don’t like piping Agent’s output through some electron wrapper, here you get to run CC/Codex/Droid/Amp/etc directly. * Isolation: agents shouldn’t step on each other’s toes. The simplest primitive I’ve found is Git worktrees. It is not as…
Jan 2026 · agentastic.dev
- 20
Open Source agent Sandboxes. Contribute to mihirahuja1/agentnestOSS development by creating an account on GitHub.
Jul 2026 · github.com
- 21LL
Some time ago I built a simple app to run swarms of coding agents — I call it fleet (https://news.ycombinator.com/item?id=48256389). It's based on centralized beads with a Python orchestrator and can run any coder (Claude, agy, Codex). Recently I added a UI to manage the whole agent lifecycle: adding new tasks, monitoring running ones, and a chat interface built on MCP with a centralized SQLite DB. From the UI I can spawn agents to run in any directory, define dependencies on other tasks, and specify which coder/model should do the job. Today I can run 10–15 agents…
Jun 2026
- 22
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
- 23
Agents orchestrating other agents. Contribute to backnotprop/orchestrator development by creating an account on GitHub.
Jul 2026 · github.com
- 24RG
Hey HN! I'm excited to share Reagent, an open source Javascript framework to build UI rich AI agents using graph based workflow. Github: https://github.com/reagentai/reagent There are already amazing tools for building agents but most of them seem to be focused on building the AI workflow on the backend with markdown as final output. There is generative UI in AI SDK from vercel but it seems to work only with server components afaik. So, I created a framework for building AI agents with interactive UI components; you can render any component from LLM tool, update it's…
2024 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →