Haunt

A desktop git client that also maps your code.

Open source Desktop git client
  • Tauri
  • Nuxt
Haunt’s main window comparing a branch of an open-source library: three changed functions, what could break, and what calls the selected one.
Close-up of what could break and what calls the selected function.
  1. What the change touches, function by function.
  2. What depends on it.
  3. What could break.
The hard part

Finding the right balance between Haunt as a git client and Haunt as a tool that gives insight into a codebase.

01

The problem

Haunt started as a Tauri app that showed the full structure of a codebase. I wanted to see how far the connections between functions and files reach in SHADE, which runs through many layers to do what it does.

A diff tells you which lines changed. It doesn’t tell you what those lines touch, what depends on them or what could break. Haunt shows that, function by function, in the same place you commit.

02

Constraints

Everything runs on your own machine. Your code never leaves it.

It runs on Windows, macOS and Linux, uses the git already on your machine, and runs none of a project’s code until you trust its folder.

03

Decisions and why

Tauri instead of Electron: Electron uses far more than an app like this needs, and Tauri builds on what’s already on your machine. Nuxt because I already work in Vue and like how it works, and Nuxt UI covered the interface I needed.

Insight was the first goal. When it ran into what it could do on its own, I turned Haunt into a git client as well, because the one I used no longer fit how I work.

04

What broke

Reading a project depends on what’s installed. TypeScript and JavaScript need Node, Bun or Deno. Without them Haunt still reads the ten other languages with tree-sitter, and it says at startup what’s missing. Imports between a project’s packages only resolve once its dependencies are installed.

05

What I’d do differently

The first versions did the git work in TypeScript. I’d do it in Rust from the start: it fits better, and that’s where it lives now.

06

How it was built

Haunt is written with Claude Code, and I review every change before it goes in. The checks run on Linux, Windows and macOS for every pull request. The product decisions and the architecture are mine.

Posts about Haunt

Let’s talk

About a project, or about a role on your team. You’ll hear from me within 24 hours.

— Dimitri, RG Digital

Email me to plan a call A reply within 24 hours · NL or EN