Gitorii Logo Gitorii
← Back to blog
Announcement · 6 min read

Introducing Gitorii: Git Made Human-First

Why we built a new Git client from scratch, what problems it solves, and where it's headed.

Git turned 20 last year. It has won — every serious codebase on the planet runs on it, and the porcelain that ships with it has barely changed since the Linux kernel days. That is a testament to how well Linus nailed the underlying data model. It is also why every onboarding guide to a new codebase in 2026 still starts with half a page of Git incantations.

Gitorii is our attempt to close that gap without throwing Git away. It is a thin, opinionated CLI on top of the same object store, the same refs, the same protocol. Your repo is still a Git repo. Your collaborators do not need to install anything. What changes is the surface you interact with every day.

The problem in one sentence

Git's CLI was designed for the person who wrote Git. Gitorii's CLI is designed for the 90% of users who did not.

Concretely, that means three things:

  • Fewer verbs, clearer intent. You do not need to know that git commit, git add, and git stash are three different commands that all "save something." You need to save, and Gitorii exposes that as torii save.
  • Safety by construction. Destructive operations are either behind an explicit flag or backed by a local snapshot you can restore. You should never lose work because you typed a flag you did not fully understand.
  • Machine-readable output. Every command has a stable JSON mode. Agents, CI runners, and scripts can consume Gitorii without regex gymnastics against a format that was never meant to be parsed.

A quick tour

Here is the same session in Git and in Gitorii. Same result, very different ergonomics.

# Git
git checkout -b feature/auth
git add -A && git commit -m "feat: login"
git fetch origin && git rebase origin/main
git push -u origin feature/auth
# Gitorii
torii branch feature/auth -c
torii save -am "feat: login"
torii sync main --rebase
torii sync --push

No magic. The second block runs the same plumbing under the hood — but the command you typed reflects what you were trying to do, not the 2005 implementation detail.

Built for the agent era

A non-trivial share of commits today are typed by an LLM. That is a category of user Git was never designed for. Agents benefit disproportionately from three things Gitorii gives them for free:

  • Predictable command grammar. Every subcommand has the same shape: noun, verb, flags. No surprise positional arguments, no hidden defaults.
  • JSON everywhere. torii log --json, torii status --json, torii diff --json. Agents never have to scrape.
  • A safety net they can trigger themselves. Before a risky multi-file refactor, an agent can torii snapshot create and be confident it can back out.

What is in 0.1

Today Gitorii ships with the daily-driver commands (save, sync, branch, diff, log, status), snapshots, mirrors across six forges, a built-in secret scanner, SemVer-aware tagging from Conventional Commits, and SSH auto-diagnosis. It is a single statically-linked Rust binary; install with curl -fsSL https://gitorii.com/install.sh | sh or grab a release from the GitHub page.

What is next

The next three releases focus on three areas: custom workflows (repeatable, composable sequences of commands triggered by events), unified CI/CD across forges (trigger pipelines on every mirror from one command), and a hosted dashboard for teams who want visibility without scraping six different web UIs.

If that roadmap sounds interesting, the docs are the fastest place to start. And please open issues — the sharp edges are the ones we have not seen yet.