Use case · IDE & editors

Stop your editor from re-walking the tree.

VS Code and IntelliJ poll git status several times a second to keep gutter decorations and the source-control panel fresh. On a big repo, every one of those polls is a full tree walk. gity serves them from a warm cache.

The problem

Modern editors are eager. To show which lines you've changed, which files are staged, and which branch you're on, they call git status on a timer — and on file-system events, and on focus. On a small repo you never notice. On a monorepo, that steady drip of full-tree walks pegs a core and makes the whole editor feel sluggish while it waits.

How gity fixes it

Because gity speaks Git's fsmonitor v2 protocol, the editor doesn't need to know it exists. Each git status the editor issues is answered from gity's warm, watcher-backed cache — so the tenth poll in a second costs the same as the first.

# register the repo your editor has open
gity register ~/work/monorepo

# now VS Code, IntelliJ, etc. get fast status for free
gity health ~/work/monorepo    # confirm the watcher is attached

For tools that would rather be told than ask, gity also publishes change events over IPC:

# subscribe to a live stream of changed paths
gity events ~/work/monorepo

What changes for you

Snappier gutters. Decorations update from cache instead of a scan.
Lower idle CPU. The editor's status polling stops re-walking the tree.
No plugin to maintain. It works at the Git layer, so every editor benefits at once.

Frequently asked

Do I need an editor plugin?

No. gity accelerates Git itself through the fsmonitor protocol, so any editor that shells out to `git status` — VS Code, IntelliJ, Sublime Merge, the command line — benefits automatically once the repo is registered. There is nothing to install inside the editor.

Why does my editor call git status so often?

Editors poll status to keep gutter decorations, the source-control panel, and the branch indicator current. VS Code and IntelliJ both poll aggressively — several times a second on an active repo — which is fine when status is fast and painful when it isn't.

Can other tools subscribe to change events too?

Yes. Beyond the fsmonitor protocol, gity exposes a pub/sub IPC channel (`gity events`) so tooling can subscribe to filesystem-change notifications instead of polling at all.

Get gity

Try gity on your biggest repo.

One command to install, one to register, and your monorepo starts feeling like a tiny one. MIT-licensed and free to use.

Install gity → Read the docs