Chintu's for everyone Git wasn't designed for.

Why this exists

Git is one of those tools where you have to know it to learn it. The error messages assume you know what they mean. The tutorials were written by people who already know Git, for people who already know Git.

Most software handles this by getting fancier. Better terminals, prettier dashboards, more menus. None of it fixes the actual problem, which is that the thing in front of you doesn't make sense.

Chintu is the version of Git that explains what it's doing while it does it. You click Push, it pushes. It tells you what just happened. If something breaks, it tells you what it tried, what failed, and what to do next. No backup tab of Stack Overflow required.

Who it's for

First and most importantly: people Git is rude to. If origin/main still sounds like a transit station, or if git push has ever produced a wall of red text you screenshot-and-googled, you're who I built this for. Git's errors read like ransom notes. That's a Git problem, not a you problem.

But also: anyone who uses Git for things that aren't "software engineer at a company that ships code." There are a lot more of you than people realize.

• Music producers backing up VST plugin source.
• Indie devs and modders shipping patches between bug reports.
• Writers who lost a chapter once and have not been the same since.
• Researchers tracking experiment code, paper drafts, and dataset versions.
• Designers committing exports next to a README.
• Hardware folks versioning firmware alongside CAD files.
• Your cousin who tries to learn to code every January and gives up by Feb.

If you've wanted to use Git for something and bounced off, that's who this is for. Doesn't matter what the something was.

How it's different

Four things, mostly.

Buttons that mean what they say.

The button labeled Push pushes. The button labeled Pull pulls. We didn't reinvent the words.

It explains itself.

When something happens, Chintu tells you in a sentence what it did. Same when something breaks, except the sentence is slightly more apologetic.

Defaults that work.

You can override anything. You just don't have to learn the override system before you can use the app.

You learn by doing.

You'll learn what a stash is the first time you need one. Until then, congratulations — you don't need to know.

If you already know Git

Chintu's tuned for the people Git frustrates the most. That's a design priority, not a ceiling. The terminal is still there, the real git commands are still there, and most workflows in the app take fewer clicks than what you'd do in your shell anyway. The CLI's still great. It just shouldn't be the only door.

Bring your GitHub.

Sign in with the GitHub account you already have. Every repo you can see on GitHub is already there in Chintu — every branch, every commit, every collaborator. No migration, no import wizard, no "now move your code into our system."

Open Chintu, sign in, and the work you were already doing is right where you left it. If you have a GitHub, you have everything you need.

It's just me building this

Chintu is a one-person project. I write the C++ backend, the Electron app, the icons, this website. There's no team, no funding round, no co-founder. Just me, on weekends and after school.

That's fine — but it means progress is slower than it could be, and there are corners of the app I'd love a second pair of eyes on. macOS builds I can't test. Edge cases on weird repo states. UI polish I keep meaning to get to. Copy that's clearer than mine.

Try it

Free, no new account to make, runs entirely on your machine. We don't see your code. We wouldn't know what to do with it if we did.