After much confusion, it seems that slickedit is messing with my ssh-agent. I use openssh via cygwin for networking. I also use Git which uses ssh, but only on the command line. Well, I wanted to use slickedit to only create check in messages on git commits (instead of using vim or notepad). I do not use slickedit Git integration and have never explicitly enabled it. I use a file socket pointed to by a user wide SSH_AUTH_SOCK environmental variable. After doing a (local only) "git commit" and writing a check-in message. I saw two behaviors in my confused thrashing: either the socket file was deleted with the ssh-agent still running or a duplicate ssh-agent was created with an empty key database. My brute force solution is to unset SSH_AUTH_SOCK in my run slickedit scripts.
