Alternatives
Products that do what OS layer for running multiple Codex agents in parallel does
We built an open source layer to orchestrate multiple Codex agents in parallel. Found myself and some friends running Codex agents across multiple terminals. Thats why me and a friend built emdash. Each agent gets its own isolated workspace, making it easy to see who’s working, who’s stuck, and what’s changed.
- 1EO
Hey HN! We’re Arne and Raban, the founders of Emdash (https://github.com/generalaction/emdash). Emdash is an open-source and provider-agnostic desktop app that lets you run multiple coding agents in parallel, each isolated in its own git worktree, either locally or over SSH on a remote machine. We call it an Agentic Development Environment (ADE). You can see a 1 minute demo here: https://youtu.be/X31nK-zlzKo We are building Emdash for ourselves. While working on a cap-table management application (think Stripe Atlas + Pulley), we found our development…
Feb 2026 · github.com
- 2
- 3
- 4
- 5FO
Hi HN! I've recently been finding productivity in running parallel CLI coding agents(after not believing in them initially). After having to do a ton of git stashing and branch fumbling, I decided I needed to something to more ergonomically run these agents in their own dedicated spaces. I tried a lot of the existing products but they either were too convoluted or flat out didn't work. Some of them also seem to roll their own chat UI which I don't think is the right approach, I wanted to something to lightly wrap my terminal sessions. So I built FleetCode! It uses git worktrees and let's you…
Oct 2025 · github.com
- 6
- 7
- 82C
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
- 9
- 10
- 11
- 12
- 13AO
Hi! I’m Nathan: an ML Engineer at Mozilla.ai: I built agent-of-empires (aoe): a CLI application to help you manage all of your running Claude Code/Opencode sessions and know when they are waiting for you. - Written in rust and relies on tmux for security and reliability - Monitors state of cli sessions to tell you when an agent is running vs idle vs waiting for your input - Manage sessions by naming them, grouping them, configuring profiles for various settings I'm passionate about getting self-hosted open-weight LLMs to be valid options to compete with proprietary closed models. One…
Jan 2026 · github.com
- 14
- 15
- 16
- 17
- 18
The power of Codex with local, self-hosted models and voice
Jul 2026 · opencodesuper.app
- 19
- 20
- 21HO
I'm Josh, founder of Synth. We've been working on coding agent optimization with method like GEPA and MIPRO (the latter of which, I helped to originally develop), agent evaluation via methods like RLMs, and large scale deployment for training and inference. We've also worked on patterns for memory, processing live context, and managing agent actions, combining it all in a single stack called Horizons. With the release of OpenAI's Frontier and the consumer excitement around OpenClaw, we think the timing is right to release a v0. It integrates with our sdk for evaluation and optimization but…
Feb 2026 · github.com
- 22SR
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
- 23LL
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
- 24DR
We wanted to run multiple AI coding assistants in parallel and swap models easily (Claude Code, local, Codex, etc.) without messing with the current branch. DevSwarm is a mac/windows desktop app that runs assistants on separate git branches so you can stay in the loop and compare/merge safely. Not an IDE, an Augmented Development Environment (ADE); open any branch in your IDE with a click. We’ve been dogfooding it for months, including DevSwarm. Try it in minutes: download, open a repo, start two assistants. Free beta.
Sep 2025 · devswarm.ai
Ranked by how close each launch is in meaning, then by votes. Refine with a description →