Alternatives
Products that do what Runyard does
AI agent swarms that plan, code, review & ship for you
- 1

- 2

- 3

- 4LL
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
- 5

- 6

- 7

Google's platform to run AI agents at enterprise scale
Apr 2026 · cloud.google.com
- 8

- 9
- 10

- 11
- 12

- 13

Give your agent tools to create beautiful, codebase-aware UI
Apr 2026 · aidesigner.ai
- 14MA
Hey HN, I spent my xmas break building an agent framework called mcp-agent [1](https://github.com/lastmile-ai/mcp-agent) for Model Context Protocol [2]. It makes it easy to build AI apps with MCP servers, and implements every pattern from the popular Building Effective Agents blog [3] as well as OpenAI’s Swarm [4]. I’m sharing it early to get community feedback on where to take it from here, and to ask for contributions. For those who aren’t familiar with MCP, I think of it as a standardized interface to let AI communicate with software via tool calls, resources and…
2025 · github.com
- 152C
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
- 16

- 17RT
Now that AI is capable of writing large volumes of production-quality code, our role as developers is changing. Our primary job is no longer writing code. It’s planning and communicating software design and architecture. We have to do this collaboratively with agents and then review and iterate on their implementations. IDEs were not built for this workflow. So about three months ago I decided to try to build what I thought this new interface should look like. Runner is a coding agent purpose-built for this new “plan and review” workflow. It’s not for vibe coding. It’s for professional…
Sep 2025 · runnercode.com
- 18
Production-tested architecture for autonomous Claude agents
Apr 2026 · dvdshn.com
- 19AS
Feb 2026 · github.com
- 20AO
I have spent a long time working in an XP/TDD style, so when AI coding tools became useful enough for real work, I adopted them quickly. The first bottleneck I hit was not code generation, it was verification: AI could write code and tests quickly, but I was still the person reviewing implementations, clicking through flows, checking logs, inspecting database state, and deciding whether the result was actually correct. That pushed me to move validation further left. Before implementation, AI had to produce test plans. After implementation, it had to execute those plans too: drive the…
Mar 2026
- 21

- 22RA
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
- 23AO
Hello Folks! Agentic Orchestrator is a terminal tool that takes complex feature requests and builds them by orchestrating coding agents through a series of phases that emulate a full-fledged engineering flow: requirements clarification, research, design, multi-phase planning, implementation, and review. It is a single pane of glass for all your features and exposes post-publish utilities such as resolving merge conflicts and responding to review comments. The key design choice is that this is deterministic orchestration on top of undeterministic agents: things like "human review gates",…
Jun 2026 · github.com
- 24

Agents orchestrating other agents. Contribute to backnotprop/orchestrator development by creating an account on GitHub.
Jul 2026 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →