GitIdentity – Multi-account fixer

Fix the recurring 'Repository not found' when one machine juggles multiple GitHub accounts

Problem

Developers with multiple GitHub accounts constantly hit 'Repository not found' on clone or push because an SSH key or credential matched the wrong account. Diagnosing means digging through ssh config, credential managers, and remote URLs, and it repeats with every new project.

Solution

A small CLI that inspects a repo's remotes, local SSH keys, and git credentials to determine which account is actually being used, checks it against the repo's expected account, and prints ready-to-run fix commands.

Users

Developers maintaining several GitHub identities (work/personal/client), freelancers and contractors

MVP

Scan repo remotes and local ssh config; list available SSH keys and mapped accounts; diagnose mismatches; output fix commands; per-directory identity binding

Revenue

Free CLI; Pro one-time license (~$15) with directory-level identity rules, credential health report, and team config templates

Why now

Multi-account workflows and AI coding agents touching repos make credential mismatches more frequent; the tool is fully local and shippable by one indie dev in days