[Xeago]

This somewhat painfully breaks when reattaching as the socket from the shells environment could be defunct. Whereas the shell session outside has a different, totally fine agent in its environment. This was somewhat painful to explain to some engineers and I suck at explaining so I’ll gladly receive a good explanation for it (or a nice workaround?) :D

[gylterud]

Are you talking about running ssh-agent on the server side? To further connect to some other machine?

For that I use a file to save the name of the socket and PID, and restore this in my .profile.