Alternatives
Products that do what worktree-compose does
Zero-config Docker Compose isolation for git worktrees
- 1DR
docker-compose is great for single node docker deployments, but it doesn't have a feature that would allow zero downtime deployments. It's not possible to deploy often if your app goes down every time, and using Kubernetes/Nomad/Swarm on a single node is an overkill. I created this Docker plugin to be a drop-in replacement for the restart command in usual docker-compose deployment scripts. It performs a simple rolling deployment of a single service.
2023 · github.com
- 2CC
Hi HN - We've been working on Coasts (“containerized hosts”) to make it so you can run multiple localhost instances, and multiple docker-compose runtimes, across git worktrees on the same computer. Here’s a demo: https://www.youtube.com/watch?v=yRiySdGQZZA. There are also videos in our docs that give a good conceptual overview: https://coasts.dev/docs/learn-coasts-videos. Agents can make code changes in different worktrees in isolation, but it's hard for them to test their changes without multiple localhost runtimes that are isolated and scoped to those…
Mar 2026 · github.com
- 3
- 4
- 5GW
I context-switch a lot. Someone pings me about a bug while I'm mid-feature, and I either: 1. `git stash` (and forget what's in there forever) 2. Make a "WIP: stuff" commit (clutters history) 3. Ignore them until I'm done (not great) Worktrees solve this perfectly – each task gets its own directory, fully isolated. But the commands are clunky and I kept forgetting the syntax. So I built a small CLI wrapper. Now my workflow is: ``` wnew feat/login # creates worktree + cd into it # ...do work... wcd # fuzzy-pick another worktree, cd there wgo main # jump straight to main ``` Dashboard…
Jan 2026 · github.com
- 6GS
TLDR; Graphite enables a git workflow called “stacking” - the fastest way to develop and ship code, which many large tech companies have been using for years. Graphite makes stacking available to anyone with a GitHub account. Hi HN! I’m Tomas, co-founder of graphite.dev, and today we’re launching Graphite after almost two years of development in closed beta. [1] Graphite started as an internal solution to our own problem. When we (engineers from Meta, Google and Airbnb) left our previous roles, we lost access to the internal code review tools we loved. So we built our own.…
2023
- 7CC
Hey HN, recently Apple release their own container manager tooling, but it's missing a "compose-like" tool. I'm building this CLI as a side-project and a way to help on the usage with the main tool. It's in a early version, then at the moment I'm trying to be as much as possible compatible with `docker-compose` config file, and in the current version we're supporting two commands: `up` and `down`.
2025 · github.com
- 8DC
I've been frustrated with dependency hell and clutter on my VPS from dev, so I built Devbox: a lightweight, open-source CLI tool that spins up isolated development environments using Docker. Each project runs in its own container, but your code stays in simple flat folders on the host machine—no messing with volumes or sync issues. Environments are disposable, so you can nuke and recreate them without losing your work. Key features: - Instant setup: `devbox init my-project` and you're in a fresh env with `devbox shell`. - Configurable via JSON: Define packages, services, and more in a…
Sep 2025 · devbox.ar0.eu
- 9GA
2019 · github.com
- 10
- 11
- 12NA
Hi HN, I've been building Nucleus, a lightweight Linux container runtime focused on two workloads: ephemeral AI-agent sandboxes and declarative NixOS services. It's a single Rust binary, no daemon. It is not a Docker replacement and not a strict subset of Docker either. I dropped the entire image-and-distribution half (no Dockerfile, no layers, no registry, no pull/push, no persistent storage layer) in exchange for going deeper on isolation and reproducibility. The rootfs is either a directory copied into tmpfs (agent mode) or a Nix-built closure mounted read-only (production mode). If…
Jun 2026 · github.com
- 13
- 14
- 15
- 16BB
This project addresses the inefficiencies of traditional Dockerfile-based container builds where each customization layer creates storage bloat through duplicate dependencies from repeated apt-get install commands, network inefficiency from redundant package downloads across different images, and slow iteration cycles requiring full rebuilds of all previous steps. Our solution enables building minimal base images from scratch using debootstrap that precisely include only required components in the initial build, while allowing creation of specialized variants (Java, Kafka, etc.) from these…
2025 · github.com
- 17KC
We kept hitting the same wall: you clone some arbitrary repo and just want it to run without any configuration work. So we built Keystone, an open source tool that spins up a Modal sandbox, runs Claude Code inside it, and produces a working .devcontainer/ config (Dockerfile, devcontainer.json, test runner) for any git repo. We build on the dev container standard, so the output works with VS Code and GitHub Codespaces out of the box. Main use cases: reproducible dev/CI environments, self-describing repos, and safely sandboxed coding agents. Our goal is to encourage all repos to…
Feb 2026 · github.com
- 18
- 19AC
Jun 2026 · github.com
- 20WG
I run a lot of agentic coding sessions in parallel, each in its own git worktree. Every worktree points at the same local Postgres though, so the moment one branch runs a migration it changes the schema out from under the others. I'd end up with agents tripping over each other, or me babysitting which branch "owned" the DB at any given moment. I made this to fix it. I hope you might find it helpful too.
Jun 2026 · github.com
- 21AD
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
- 22GZ
Feb 2026 · github.com
- 23LA
Inspired by lazygit, I have been working on a TUI to manage git worktrees easily, making some workflows for creating and managing worktrees a bit more straightforward. For example, creating a worktree from a PR/MR or from local changes. Executing commands on a worktree, or running a custom tmux session directly on a selected worktree. A lot of other tools are more CLI-oriented. I have tried to compile an honest comparison here: https://github.com/chmouel/lazyworktree/blob/main/COMPARAISO... Some of the code and documentation was written with an LLM if…
Jan 2026 · github.com
- 24
Ranked by how close each launch is in meaning, then by votes. Refine with a description →