Peer-to-peer git

Git without a forge

Peer-to-peer git: repositories are signed Nostr events (NIP-34), git data lives on any GRASP server, and issues, pull requests, review and merging work without a forge in charge.

Browser · macOS · Windows · Linux · ChromeOS

✓ tests passed

What it does

Everything a repository is lives in events its maintainers sign: who maintains it, where its data lives, which commit each branch points at, and its issues, patches, pull requests and reviews. A GRASP server stores git data only as that signed state allows. No accounts — your key is your identity — and repositories from other NIP-34 tools show up too.

01
Signed repository stateBranches and tags are what the maintainers signed, so a server that lies is caught.
02
Pull requests and mergingMerge (fast-forward or merge commit) or squash without a checkout; conflicting changes stop the merge.
03
Edit in the browserCommit a change on a branch, sign the new state and push in one step.
04
Private groupsYour key signs in to the group relay (NIP-42) and signs every git request (NIP-98).
05
Works when relays are downEvents also travel peer to peer between tabs and desktops.
06
Backups you ownA git bundle and every signed event per repository, saved to your own drive.

How it works

  1. Open git.vims.com or Git in VIMS Desktop
  2. Create a repository or explore public ones
  3. Push, open pull requests, review and merge

FAQ

Does it work with ngit and gitworkshop?

Yes. They speak the same protocol (NIP-34), so repositories move between them freely.

Where is the git data stored?

On the GRASP servers each repository names — grasp.vims.com or any other — and in your own backups.

Can agents work with repositories?

Yes. VIMS’s forge tools read, comment, open pull requests, review and merge on NIP-34, GitHub and GitLab alike, with writes waiting for approval.

Can I use VIMS Git in a browser and in VIMS Desktop?

Yes. Open it at its subdomain, or use the same surface inside the VIMS Desktop client — same key, same data.

How does VIMS Git connect to the rest of VIMS?

It shares your identity from keys.vims.com and is reachable by agents through MCP and Flow, so it works alongside every other VIMS app.

Related

Git without a forge

Everything a repository is lives in events its maintainers sign: who maintains it, where its data lives, which commit each branch points at, and its issues, patches, pull requests and reviews. A GRASP server stores git data only as that signed state allows. No accounts — your key is your identity — and repositories from other NIP-34 tools show up too.