Alternatives
Products that do what Lich, start a dev stack per coding agent in parallel does
Hey HN, Lich is a worktree aware local dev stack orchestrator. Simply put, it allows you to run multiple copies of your development stack from different worktrees with different code in parallel without going insane. I built Lich because I’ve found myself increasingly using multiple parallel coding agents for development work. I wanted my coding agents to each have independent copies of my development stack to be able to test and validate their own work well. I found that trying to do this totally broke the way I have normally setup tooling for local development. Ports conflict, the UI from…
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13D2
Mike, cofounder of DevSwarm here. I’ve been using Claude Code heavily for the last few months (multiple Max plans). Running sessions in parallel across git branches or worktrees is fast, but it breaks down quickly in practice because of sprawl. Terminals everywhere, editor windows everywhere, and you lose track of basics like which agent is on which branch and what is ready for review. DevSwarm is what we built to solve that. The core abstraction is simple: workspace equals branch. Each workspace runs its agent session(s) and keeps the state visible. In 2.0 we added a full VS Code IDE…
Feb 2026
- 14SR
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
- 15OL
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.
Sep 2025 · github.com
- 16TO
I built DevClaw, an OpenClaw plugin that turns each Telegram group into an isolated, autonomous dev team: planner/orchestrator, DEVs, and QA all running on their own. I use it for all my development now. Issues on GitLab/GitHub are the single source of truth, and three things compound to save around 70% on tokens: model tiering (Haiku for typos, Opus for architecture), session reuse across tasks, and token-free scheduling that burns zero LLM calls for orchestration. Please try it and give some feedback. Also keen to hear from anyone running autonomous coding agents, especially what…
Feb 2026 · github.com
- 17CA
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
- 18BE
I realised I was working on more parallel tasks with coding agents, but git branches became a huge bottleneck. Tried Git Butler but it just complicated things further. Found git worktrees as a solution but the git API was a bit too complicated for day to day. So thought I'll vibe-code this simple CLI utility to manage the process. It technically works with any setup – claude/codex/gemini + cursor/vim/whatever. Just manages git worktrees inside your repo and sets up your dev environment how you like it. Nothing fancy, just something I built to scratch my own itch. Figured…
2025 · github.com
- 19IB
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
- 20CT
I built CodeBeam to solve two core developer frustrations: constant context-switching between browser and IDE, and the tedious process of dealing with errors across different languages and frameworks. What makes CodeBeam different is its universal adaptability. It watches your clipboard with customizable directives for automatic file operations, while simultaneously monitoring your logs for errors using pattern-based detection that works with any language or framework. When it spots an error, it automatically generates AI-ready prompts with rich context, making debugging significantly…
2025 · github.com
- 21CR
Hey HN, Over the past 10 months I've been using Claude Code heavily, and one limitation kept coming up: you can really only run one coding agent at a time. While one agent is refactoring something, the rest of the repo is basically blocked unless you start manually juggling branches and working directories. The core issue is that AI coding agents operate directly in your filesystem. If two agents run in the same working directory they quickly start stepping on each other’s changes. Git worktrees turned out to be a surprisingly good primitive for solving this. So I built ChatML, a Desktop app…
Mar 2026 · github.com
- 22PO
Hi HN, We are excited to share patchwork - an open-source CLI for dev chore automation that you can use with your LLM of choice. Dev Teams can orchestrate custom workflows (called ‘patchflows’) using a combination of reusable steps and prompt templates to fix vulnerabilities, upgrade breaking dependencies, generate documentation, and more. We built scanning tools in the past, and saw how overwhelmed developers get with their DevSecOps pipelines. LLMs have the potential to help - but there is a need for an 'outer-loop' solution that can be customized to accommodate the processes, priorities,…
2024 · github.com
- 23FB
TLDR: made the first background coding agent that has an isolated workspace and runs locally Howdy - I’m Kevin, co-founder of Firebender, and we built the first background coding agent in android studio / Jetbrains! Why not just use Cursor background agents or OpenAI Codex? Both of these require setting up a cloud container and cloning your existing developer environment, and maintaining it. Then when you want to iterate on changes as AI inevitably makes a mistake, you either throw away the work, or have to pull down the branch and clean it up. This feels really clunky. With Firebender,…
2025 · youtube.com
- 24LA
Hello HN, I am building a devtool to understand existing codebases. The idea originates from my time at big tech as well as various attempts to get involved in open source projects. When I was in college I wanted to improve my coding skills by contributing to opensource projects. I would pickup a bug or feature request but I always found myself stuck at the very first step. I did not understood where and how to begin contributing. I once submitted a patch in firefox which was labeled "Good first issue" but that was still very handheld. The assigner told me exactly which files I need to…
2024 · lucidcode.ai
Ranked by how close each launch is in meaning, then by votes. Refine with a description →