Wrong commit author
Work email, now permanent in public history.
One click swaps your identity, SSH keys, and credentials — across every repo at once.
Tuesday, August 20
Works with everything you already push to
Git was built for one identity. Add a second and everything turns manual — and manual eventually fails.
Work email, now permanent in public history.
Personal account pushed into a client's audit log.
Permission denied (publickey).
Last project's token applies to the next.
Click a profile. Everything updates — exactly like your machine would.
Profiles
Active profile: Personal
One job — keeping your Git identity correct — done completely.
See all 13 featuresName, email, signing key, and credentials as one unit.
Generate, import, and route keys per profile.
Tokens in your OS keychain. Never plaintext.
Bind folders to profiles. Rules assign automatically.
Match on path, remote, host, or owner.
A watcher activates the right identity — no click.
Native-feeling, dark by default, fast as a light switch.
Tuesday, August 20
No terminal, no config edits. A background watcher keeps the right identity active — and swaps everything the moment you move between repos.
A lightweight background watcher notices the moment you enter a repository and checks which identity it belongs to — no clicks, no thinking.
One shortcut — or an automatic rule — rewrites your git config, loads the right SSH key, and updates credentials across every open repo at once.
Switched to Acme Corp — 0.6s
You can — that's the point. GitPersona doesn't replace Git; it automates the parts around it. Conditional includes, SSH host aliases, and credential helpers all work, but they're fragile, per-machine, and easy to get subtly wrong. GitPersona manages the same standard mechanisms with validation on top, so a mistake becomes impossible rather than merely unlikely.
No. GitPersona only writes standard Git configuration (user.name, user.email, signing keys) and SSH/credential settings. It never touches your working tree, history, or remotes. The optional Commit Guard installs a pre-commit hook only in repositories you choose to protect — it preserves any existing hook and can be removed at any time.
Yes — that's the core use case. Each profile carries its own GitHub credentials and SSH key. GitPersona routes each repository to the right account automatically, so personal, work, and client accounts coexist on one machine without conflicts.
No. GitPersona is local-first: profiles, keys, and tokens stay on your machine, secured by your OS keychain. There's no account, no server, and no telemetry. The upcoming Cloud Sync feature will be optional and end-to-end encrypted.
Completely. Switching identities, mapping repositories, managing keys, and applying rules all happen locally. GitPersona does not require a network connection for any core functionality.
GitPersona is published on GitHub. You can read the source, audit what happens to your config and keys, and build trust before relying on it.