Holt A product of Contrare Research

See what your agents changed. Keep the work that matters.

Holt brings your coding agents' separate workspaces into one local view. Find duplicate work, catch overlapping edits, see what depends on what, and check which changes need preserving before cleanup.

Try Holt on GitHub See a real example
free core no account your code stays local
Real product renderer / controlled Git fixture Actual Holt terminal interface classifying ten Git worktrees as at risk, holding, or disposable, with unique-work evidence and a recoverable rescue command for the selected worktree.
Why I built it

Claude Code duplicated work. Then originals disappeared.

I was working on a large project, and keeping track of the agents became its own job. I built Holt because I wanted to understand what was happening and protect the work already there.

These separate copies of a repository are called Git worktrees. They let agents work in parallel, but each can hold changes the others have never seen.

Watch Holt open a real relationship graph, find a collision and repeated work, and show changes with no durable copy. Then see how the same tools fit into Claude Code and local Codex workflows.

Explore the actual demo graph ↗
Actual graph and terminal captures from Holt v0.4.5 on controlled Git examples, with animated emphasis. Agent interfaces and recovery flow are illustrations. Nothing was deleted or moved in these captures. Explore the graph · Read the terminal view · Evidence and output.
Try it on your own worktrees

One read-only check. No setup call.

Open a terminal inside the repository you want to inspect, then run this. It downloads the official release into npm's cache and runs Holt without a global install.

run inside your repository
npm exec --yes --loglevel=error --allow-remote=root \
  --package=https://github.com/Raed2180416/holt/releases/latest/download/holt.tgz \
  -- holt risk --strict-read-only --no-symbols --include-primary

Requires Node ^22.22.2 || ^24.15.0 || >=26.0.0 and Git 2.45 or newer. The check changes no repository files, hooks, or locks. Protection and quarantine remain separate, explicit actions.

Prefer a regular install? 
npm install -g https://github.com/Raed2180416/holt/releases/latest/download/holt.tgz --allow-remote=root

Then run holt risk --strict-read-only --no-symbols --include-primary from your repository. The per-command --allow-remote=root flag supports npm 12's explicit URL-package permission.

Open the full terminal view or graph

After a regular install, holt doctor shows which analysis backends are available. Run holt tui --include-primary to explore the workstreams, collisions, and unique-work evidence. Press q to leave.

holt graph --html holt-graph.html --include-primary exports an interactive local graph. Choose a new output filename, then open it in your browser. holt context <id> gives the sibling context for a workstream listed by holt status.

The problem

More agents shouldn't mean losing the thread.

Two agents can rebuild the same thing, change the same function, or leave a fix in a workspace you thought was finished. Holt helps you see those relationships before deciding what to combine, preserve, or clean up.

The useful context is often outside the current workspace: an API another agent is still building, a sibling edit that will collide, or a fix that has never reached a commit. Holt makes that state available before the next coding, landing, or cleanup decision.

  1. 01

    See the whole picture

    Bring the workspaces, branches, stashes, and local changes into one view. Give each agent context about what the others are doing.

  2. 02

    Untangle the work

    Find overlapping edits and duplicate code. Review dependencies and a suggested order for bringing changes together.

  3. 03

    Keep a way back

    Check for work that exists nowhere else. Review protection, capture, and recoverable quarantine before taking an action.

Agentsparallel edits
context
Holtevidence / action / recovery
primitives
Gitworktrees / refs / locks
What Holt does

From scattered agent work to a decision you can inspect.

Use Holt alongside your editor and Git workflow. It is most useful when several agents or branches have their own local workspaces. Each part answers a different question.

01 / DECISION

What changed, and where?

status, risk, the terminal interface, and an offline relationship graph bring the workspaces into one view. See local changes and work with no durable copy elsewhere.

02 / OVERLAP

Are agents stepping on each other?

collisions and hotspots reveal shared files and symbols. You can review the overlap before separate tasks turn into a difficult merge.

03 / DUPLICATES

Did we build this twice?

duplicates surfaces repeated implementations across workspaces. Inspect the evidence and decide what to reuse. Similarity is a review signal, not permission to discard code.

04 / COORDINATION

What should come together first?

impact, order, partition, and plan help you review dependencies, divide work, and choose a landing order. Suggested relationships still need your review and tests.

05 / PRESERVATION

Is this the only copy?

gate checks a worktree before removal. protect and auto apply local protection; rescue captures work to a verifiable local ref. Ignored or unmeasured content can keep a decision blocked.

06 / RECOVERY

Can I get it back?

clean previews recoverable quarantine. Its explicit apply step moves measured disposable worktrees into locked local storage. quarantines, restore, and local receipts show the way back.

07 / AGENT CONTEXT

Can my agents see this too?

A project-scoped MCP server gives agents 18 decision-oriented tools, including live ownership, context, collisions, landing order, and discard preview/recovery. In the CLI, context and brief supply the sibling context. Optional host hooks cover specific operations. Check your host's coverage before relying on blocking.

08 / HISTORY

What happened to that work?

Inspect branches and stashes alongside workspaces. journal and forensics help trace local actions; audit checks the installed package's declared capabilities and bytes.

09 / LOCAL AND FREE

Free core

Local analysis, no account, no code upload, no usage telemetry. The single-repository core is free under FSL-1.1-MIT for any purpose other than a defined Competing Use. Internal commercial use is permitted within that boundary.

Run a first check

A few useful boundaries

The read-only check is the place to start. The full host matrix and security notes cover the rest.

  • The first check changes no repository files, hooks, or locks.
  • A worktree scan is not an off-machine backup.
  • Local checks do not protect cloud agent workspaces by default.
  • Unknown or incomplete results need review before any action.
A note from the developer

I'm building this solo. I'd like to know if it helps you.

I'm Raed, the developer behind Holt at Contrare Research. The duplicated work and lost originals in my own project are why this matters to me. I've put a lot into it, and I'm trying to get it into the hands of people who might find it useful.

If you try it, please tell me what you think. Useful, confusing, missing something, or just not needed in your workflow: honest opinions and criticism are welcome.

Run a first check Explore the demo research.contrare@outlook.com Share feedback on GitHub GitHub feedback requires a GitHub account. You can also email me.