← All field notes

Why I built LocalGit Studio around the working tree

A look at the local-first decision behind my Git workspace, the workflow it supports, and the boundaries I want to keep clear.

Start with the real repository

When I started building LocalGit Studio, I kept coming back to one question: could the interface make Git easier to review without asking a developer to move a repository or change editors? I chose a local-first direction. The project works with an existing repository on the computer, while Git remains authoritative and VS Code or another editor can keep using the same files.

What the project does

The current workflow brings branches, staged and unstaged changes, diffs, recent commits, and remotes into one place. From there, a developer can stage or unstage files, commit, create or switch branches, fetch, fast-forward pull, and push. The interface is a review layer around a working tree rather than a replacement for Git.

I built the front end with React and Vite, with a local Node.js and Express API that uses the installed Git executable. The data remains on the user’s machine. Optional S3-compatible backups are manual and limited to files the user selects; they are separate from Git remotes.

Boundaries matter

Keeping work local only helps if the local service is treated carefully. LocalGit Studio binds to loopback, requires a repository or workspace path, checks request origins and workspace boundaries, and protects mutations with a CSRF token. Git subprocesses run without a shell and have output limits and timeouts. Docker and MongoDB are not runtime requirements.

What I learned

The most useful project decisions have often been boundaries: what belongs in the tool, what stays with Git, and what must remain under the developer’s control. LocalGit Studio is still in progress, so I am treating the current feature set as the work completed to date rather than a claim that the product is finished.

The project source is in the Exploring-Tech repository, and its project information page explains how it runs. The source is licensed under PolyForm Strict 1.0.0.

Open thread / public discussion

Join the conversation.

Comments will appear after a public GitHub Discussions repository is connected and configured.