orion-worktree-report
See where your Git worktrees overlap.
Choose local repositories and see which registered worktrees share an uncommitted path. Every report says what it observed and what it could not check.
Watch orion-worktree-report in action
Recorded CLI output from the checksum-verified Orion Worktree Report v0.1.0 wheel. Disposable synthetic Git repositories, edited replay; private absolute paths are omitted. Coverage is an observation, not ownership or merge authority. Locally synthesized Dan narration.
Read the transcript
Orion Worktree Report observes the local repositories you select. In this disposable example, the first scan observes three registered worktrees and reports no uncommitted path overlap. Now two worktrees change the same tracked path. The scan reports the shared path and exits one, with complete coverage. It observes this overlap without deciding which worker should proceed. Add an unavailable repository and coverage becomes partial. The known overlap stays visible, while the total is unknown. This report grants no task ownership, file lock or merge permission. The source and walkthrough are linked below.
ONE SYNTHETIC EXAMPLE
1 REPOSITORY / 3 REGISTERED WORKTREES
main
clean
worker-a
shared.txt
worker-b
shared.txt
COMPLETE COVERAGE · EXIT 1
1 shared path · 1 worktree pair
All three registered worktrees were observed. The two dirty checkouts share one exact path.
Illustration of the guide’s disposable example. A shared path is an observation; it does not establish a merge conflict or who owns the work.
Start with coverage
A clean-looking answer helps only when every selected scope was observed. Missing checkouts, unsupported features, timeouts, limits and detected changes stay visible. Partial coverage never becomes “no overlap observed.”
Dirty paths include staged, unstaged and individual nonignored untracked files. Renames retain both path roles. Exact bytes determine identity, so unusual filenames stay distinct. Committed-only branch differences and ignored files are outside this report.
Select the repository yourself
orion-worktree-report --json scan --repo /absolute/path/to/repositoryNo implicit directory search or fleet discovery. The guide supplies the pinned installer, wheel checksum, two-worktree walkthrough and removal steps. Use the v0.1.0 release files in a dedicated environment with its own Python interpreter.
Tested target: CPython 3.11.9, Git 2.43.0, Linux x86_64 under WSL2, local ext4. Other platforms and versions remain unverified. No Python runtime dependencies.
Evidence for your next decision
- An observation grants no authority.
- The command assigns no task, locks no file and decides no merge. Two matching samples are not an atomic snapshot or a fence against another writer.
- Repository state stays in your hands.
- On supported stable repositories, scans initiate no writes to objects, refs, index, configuration, working files or registrations. No cleanup, prune, repair, fetch, daemon or automatic hook. Access-time bookkeeping is excluded; trusted Git and cooperative configuration are required.
- Local names need deliberate sharing.
- Reports contain absolute paths, branch names and filenames. Review and sanitize before sharing. The reporter emits no file contents, diffs, remotes or raw Git diagnostics.
A separate tool with a clear role: PM coordinates work; browser and phone interact; Handoff carries continuity; Results retains output. Worktree Report supplies an observation. Installing it creates no integration or change to those packages.