Ssh-agent and ssh-add

With the following setup, you won't need any wrapper for invoking screen. Moreover, it avoids using /tmp (with the consequent security risks).

1. Ensure you have an ~/tmp directory:

   mkdir ~/tmp
   

2. Add to .screenrc the following line:

   setenv SSH_AUTH_SOCK "$HOME/tmp/ssh-agent-screen"
   

   • This ensures that inside screen, ssh looks for the socket always in the same location, rather than a changing path.
   • You must use setenv whichever shell you use, since it's a screen and not a shell command.

3. Add to .bash_profile the following line:

   [ -n "$SSH_AUTH_SOCK" ] && [ "$SSH_AUTH_SOCK"!="$HOME/tmp/ssh-agent-screen" ] && ln -sf "$SSH_AUTH_SOCK" "$HOME/tmp/ssh-agent-screen"
   

   • This will link from the fixed location (where ssh looks) to the real one, and must appear after starting ssh-agent.
   • Using [ -n "$SSH_AUTH_SOCK" ] will properly prevent errors when SSH_AUTH_SOCK is not set.
   • [ "$SSH_AUTH_SOCK"!="$HOME/tmp/ssh-agent-screen" ] will prevent screen sessions linking $HOME/tmp/ssh-agent-screen to itself, if screen sources .bash_profile.
4. Instead of starting ssh-agent in .bash_profile, you can consider connecting with ssh -A (to use agent forwarding and make the remote machine use your agent).

After this setup, you can just use standard screen command. You'll only need to recreate existing sessions or manually set SSH_AUTH_SOCK inside them to the fixed location of step 2.

Credits to this website for the idea; I avoided using /tmp. This answer is similar but uses extra aliases.

You can open Keychain Access located in /Applications/Utilities/ and navigate to your login keychain .

Once there, you can delete SSH keys. They should look like SSH: /Users/your username/.ssh/key name