Get Rid of Repeated SSH Key Password Prompts in Git

Every developer knows small interruptions can break the flow, especially when you're deep in the zone. One common hiccup is being asked for your SSH key password every time you `git pull`. If this sounds familiar, you're in the right place. Let's explore how to streamline your workflow by ensuring your SSH key remembers its password, keeping those coding sessions smooth and uninterrupted.

Understanding the Prompt

When prompted for your SSH key password with each Git operation, it's because your SSH key is encrypted with a passphrase for security. While this is good practice, entering the passphrase repeatedly can disrupt your workflow. The solution lies in the SSH agent, a background program designed to manage your SSH keys and remember their passphrases.

Step 1: Fire Up the SSH Agent

First things first: let's get the SSH agent running. Open your terminal and enter:


eval "$(ssh-agent -s)"

This command starts the agent and sets the necessary environment variables for its operation. With the agent up and running, you can add your SSH key.

Step 2: Add Your SSH Key to the Agent

With the SSH agent active, it's time to add your SSH key. If it's stored in the default location (`~/.ssh/id_rsa`), simply type:



If your key is elsewhere or named differently, point `ssh-add` to the right spot:


ssh-add ~/.ssh/your_ssh_key_name

After this, the agent will remember your passphrase, sparing you from retyping it for every Git operation.

Step 3: Ensure Persistent SSH Agent Usage

To make sure SSH always utilizes the agent for your keys, tweak your `~/.ssh/config` file. Don't worry if it doesn't exist yet; just create it and add:


Host *

AddKeysToAgent yes

UseKeychain yes

IdentityFile ~/.ssh/id_rsa

Replace the path with your key's if it differs. For macOS users, `UseKeychain yes` is a handy option, instructing the SSH agent to keep the passphrase in your keychain for even smoother access.

Bonus: Automate ssh-agent with Systemd

Linux users can automate ssh-agent startup using systemd, ensuring it's always ready to go from login. Here's how:

1. Create a systemd service file for ssh-agent in `~/.config/systemd/user/` and name it `ssh-agent.service`. Fill it with:



Description=SSH key agent




ExecStart=/usr/bin/ssh-agent -D -a $SSH_AUTH_SOCK


2. Enable and start the service to get ssh-agent running automatically:


systemctl --user enable ssh-agent

systemctl --user start ssh-agent

3. Update your shell configuration file (like `.bashrc` or `.zshrc`) to set the `SSH_AUTH_SOCK` environment variable, ensuring your system knows where to find the agent.

Wrapping Up

Integrating the SSH agent into your workflow allows you to bypass the repetitive task of entering your SSH key password for every Git pull, push, or fetch. This small adjustment to your setup can save a significant amount of time and frustration, letting you maintain your focus on what truly matters: your code. Happy coding, and here's to a smoother, more efficient development experience!