# ERROR: Command errored out with exit status 128: git clone --filter=blob:none 'git@github.com:user/private-repo.git' /tmp/pip-req-build-xxxxx. Check the logs for full command output.

- **ID:** `pip/git-clone-exit-status-128`
- **Domain:** pip
- **Category:** auth_error
- **Error Code:** `ERROR`
- **Verification:** ai_generated
- **Fix Rate:** 85%

## Root Cause

Pip cannot clone a private Git repository because the SSH key or authentication credentials are missing, invalid, or not configured for the user running pip.

## Version Compatibility

| Version | Status | Introduced | Deprecated |
|---------|--------|------------|------------|
| pip 23.0 | active | — | — |
| pip 23.1 | active | — | — |
| pip 23.2 | active | — | — |
| pip 24.0 | active | — | — |

## Workarounds

1. **Ensure SSH key is added to the SSH agent: run 'ssh-add ~/.ssh/id_rsa' and verify with 'ssh -T git@github.com'.** (80% success)
   ```
   Ensure SSH key is added to the SSH agent: run 'ssh-add ~/.ssh/id_rsa' and verify with 'ssh -T git@github.com'.
   ```
2. **Use a personal access token with HTTPS: change the requirement to 'git+https://<token>@github.com/user/private-repo.git' in requirements.txt.** (90% success)
   ```
   Use a personal access token with HTTPS: change the requirement to 'git+https://<token>@github.com/user/private-repo.git' in requirements.txt.
   ```

## Dead Ends

- **** — The underlying issue is the same SSH authentication problem; manual clone will also fail until credentials are fixed. (90% fail)
- **** — This can work if a token is provided, but if the token is missing or expired, the error persists. (40% fail)