mycadre

Git worktrees that are ready to work.

mycadre creates a git worktree for a branch, copies your untracked local files (like .env) into it, runs your setup command (like npm install), and tracks it so you can list and clean up worktrees without leaving orphans behind.

Git worktrees are great for working on several branches at once — reviewing a PR while your feature branch keeps building, or running a fleet of AI coding agents in parallel, each in its own checkout. Plain git worktree add just creates the checkout: it doesn't copy your gitignored .env files, run your setup command, or track what you made for later cleanup. mycadre does — in a small, zero-dependency CLI configured by one mycadre.json file.

Install

npm install -g mycadre

git clone https://github.com/flossypurse-studios/mycadre.git
cd mycadre
npm install && npm run build
npm link   # makes `mycadre` available globally

Requires Node.js >= 18 and git on your PATH.

Quick start

# In your project's git repo:
mycadre init                 # writes mycadre.json (edit to taste)
mycadre create feature/login # new branch + worktree, env copied, setup run
mycadre list                 # see your tracked worktrees
mycadre remove feature/login # delete the worktree and its branch
mycadre clean                # prune worktrees git already dropped

Commands

Command	What it does
mycadre init	Create a mycadre.json config at the repo root.
mycadre create <branch> [--from <base>] [--no-setup] [--json]	Create a worktree for <branch> (new branch off <base>, or the current branch, unless it already exists), copy configured files into it, and run the setup command. --no-setup skips the setup command; --json prints {"branch","path"} to stdout (progress logs go to stderr) for scripting.
mycadre list [--json]	List tracked worktrees and flag any that have gone missing. --json prints machine-readable output for scripts.
mycadre remove <branch> [--keep-branch] [--force]	Remove the worktree and (unless --keep-branch) delete the branch.
mycadre clean	Prune git worktrees and drop stale tracking entries.
mycadre doctor [--json]	Check that git, your repo, mycadre.json, worktreeDir, and tracked worktrees are all in a healthy state. Exits 1 if anything's wrong.
mycadre fresh [--live <url>] [--base <branch>] [--remote <name>] [--no-pr] [--json]	Read-only check before you diff, review, push, open a PR, deploy or publish: asks the remote whether HEAD is built on its default branch, whether your local default branch is behind, and whether the branch's PR is still open at HEAD. Exit 0 fresh, 1 stale, 2 could not check. See Is my branch fresh?.
mycadre --version	Print the installed version (also -v).
mycadre --help	Show usage help (also -h).

Is my branch fresh?

Parallel branches go stale quietly. Someone merges to main while you work, and your diff now shows their change reverted. A PR gets merged while you are still pushing to its branch, and the pushes go nowhere. Production gets hot-fixed from a laptop, and the next deploy from main rolls it back. mycadre fresh checks for all three, right before the moment it matters:

mycadre fresh                                   # before a diff, review, push or PR
mycadre fresh --live https://example.com/version # before a deploy

✗ base: HEAD is 3 commits behind origin/main (4d1c2ab) — a diff against it will show their changes reverted
    4d1c2ab Fix the login redirect
    9e0b7f1 Bump the API client
    52aa0c3 Drop the old cache
✓ local: local main matches origin/main
✗ pr: PR #42 is ALREADY MERGED — pushing to 'feature/login' goes nowhere; start a new branch from main
✓ live: production (52aa0c3) is 2 commits behind origin/main

STALE — see ✗ lines above. Nothing was changed.

• base — is the remote's default branch an ancestor of HEAD? It asks the remote with git ls-remote and fetches only the commits it needs, so an old local origin/main can't make a stale branch look current.
• local — is your local default branch behind the remote?
• pr — via gh, if the branch has a PR: is it still open, and is its head in HEAD? Merged or closed PRs are flagged.
• live — with --live <url>, fetches a URL that returns the deployed commit (plain text, or JSON with a sha, commit or git_sha field) and says whether production is equal to, behind, or ahead of the remote. Ahead means deploying from the remote would revert it.

Exit codes: 0 fresh, 1 stale, 2 could not check. A check that could not run (offline, no remote, gh missing or signed out, an unreadable --live response) is exit 2 and never reads as fresh. Pass --no-pr to skip the PR check on purpose. --json prints every check for scripts and agents.

It compares against origin (or the only remote; --remote <name> to choose), even when your branch tracks a fork, and looks the PR up on that repo.

fresh never checks out, rebases, merges or pushes. The only thing it writes is the git fetch of commits it compares against, which updates remote-tracking refs and FETCH_HEAD (no tags, no submodules, no background gc).

Configuration

mycadre init writes a mycadre.json at your repo root:

{
  "worktreeDir": "../mycadre-worktrees",
  "copy": [".env", ".env.local"],
  "setup": "npm install"
}

• worktreeDir — where worktrees are created, relative to the repo root.
• copy — files/directories copied from the repo root into each new worktree (typically gitignored local config). Missing entries are skipped silently. Each entry can be:
  • a plain string (".env") — copied into the worktree, as above; or
  • an object {"path": "...", "mode": "symlink"} — a symlink is created in the worktree pointing back at the file/dir in the main repo root instead of duplicating it. Useful for large or shared things you don't want copies of, like node_modules or a big .env you always want in sync:

    "copy": [
      { "path": "node_modules", "mode": "symlink" },
      { "path": ".env", "mode": "symlink" }
    ]
    

    The symlink target is relative, so the link keeps working if you move the repo (and its worktrees) to a new location together.
• setup — a shell command run inside the new worktree after creation, or null to skip.

Commit mycadre.json so your team shares the same setup. mycadre stores its tracking data in .mycadre-state.json — add that to your .gitignore.

Why not just git worktree?

git worktree gives you the checkout. mycadre gives you a checkout you can immediately work in: local env files present, dependencies installed, and a record of what you created so cleanup is one command instead of archaeology.

Similar tools

Worktrunk manages worktrees by branch name and adds hooks, a merge workflow, and shared build caches. Claude Code (--worktree/ -w) and Cursor's Agents Window both create a worktree per parallel agent for you automatically. mycadre is smaller and more general: no agent runner, no build cache — one mycadre.json, copy some files, run one setup command, track what you made.

Troubleshooting

• Not inside a git repository (or git is not installed). — create, list, remove, and clean must be run from inside your project's git repo. Run git status to confirm you're in one, and make sure git is on your PATH.
• Target path already exists: <path> — a directory for that branch already exists in your worktreeDir. Remove it with mycadre remove <branch> (or delete the stray directory) before recreating it.
• No tracked worktree for branch '<branch>'. — remove didn't find that branch in mycadre's tracking data, so there was nothing to remove. This is a warning, not an error (mycadre exits 0). Run mycadre list to see what's tracked.
• No mycadre.json? — that's fine: mycadre falls back to sensible defaults (worktreeDir: "../mycadre-worktrees", setup: "npm install"). Run mycadre init to write a config you can customize and share with your team.

License

MIT © mycadre