worktree-compose
PulseGate's liveness check found it on 9 Oct 2026; it is registered on GitHub and has been in the index since 16 Jun 2026. How this is checked
worktree-compose is a command-line tool designed to provide zero-configuration Docker Compose isolation for git worktrees. It addresses the challenges faced when multiple developers or AI agents operate on different git worktrees within the same repository, such as port conflicts, shared database corruption, cache contamination, and container name collisions. By automatically assigning unique ports, databases, caches, and containers to each worktree, it enables parallel…
Inferred · not functionally tested
Overview
5 featuresPurpose: Avoiding port conflicts and data corruption when running multiple Docker Compose stacks in parallel git worktrees.
Inferred · not functionally tested
Audience: developers using Docker and git worktrees
Inferred · not functionally tested
Functions: workflow_automation
Inferred · not functionally tested
Interfaces: API: unknown · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)
Recorded constraints: pricing: open_source · license: MIT · platforms: CLI · deployment: cli, self_hosted
Constraint provenance is unknown; confirm requirements with the publisher.
Record sources: worktree-compose.com · github.com. These links do not verify the individual claims.
In the CLI tools & terminal space, worktree-compose takes a focused approach. Inferred · not functionally tested: It focuses on avoiding port conflicts and data corruption when running multiple Docker Compose stacks in parallel git worktrees. Inferred · not functionally tested: It is built as an open-source project for developers using Docker and git worktrees. Basis unknown · not verified: The project is open source (MIT). Basis unknown · not verified: It ships for the command line, and it can be self-hosted.
worktree-compose first shipped in 2026. The project is developed in the open on GitHub with 31 stars. Inferred · not functionally tested: Among its 5 catalogued features are port isolation, container isolation, and file sync. Basis unknown · not verified: Catalogued interfaces include an MCP server.
Summary written by a language model from the project’s public pages.
Tasks: Inferred · not functionally tested
- Port isolation
- Container isolation
- File sync
- Env injection
- Zero config
Topics: Inferred · not functionally tested
Built with & integrations
- Next.js
- x-nextjs-prerender header · /_next/static/ in the HTML · __next_f in the HTML
- Vercel
- x-vercel-id header · x-vercel-cache header
Trust & compliance
Indexing history
What PulseGate has recorded for this listing
Frequently asked questions about worktree-compose
- What does worktree-compose do?
- Inferred · not functionally tested: Worktree-compose focuses on avoiding port conflicts and data corruption when running multiple Docker Compose stacks in parallel git worktrees. It is catalogued under CLI tools & terminal on PulseGate.
- Who should use worktree-compose?
- Inferred · not functionally tested: worktree-compose is an open-source project built for developers using Docker and git worktrees.
- Is worktree-compose free?
- Basis unknown · not verified: Yes — worktree-compose is open source under the MIT license and free to use.
- What platforms does worktree-compose run on?
- Basis unknown · not verified: worktree-compose runs on the command line. It can also be self-hosted.
- Is worktree-compose still active?
- PulseGate's liveness check found it on 9 Oct 2026.
- How long has worktree-compose been around?
- worktree-compose first shipped in 2026.
- Is worktree-compose open source?
- Basis unknown · not verified: Yes — worktree-compose is open source under the MIT license, developed on GitHub.
- Does worktree-compose have an API or integrations?
- Basis unknown · not verified: Yes — worktree-compose exposes an MCP server.
Similar projects
Closest matches by what these projects do