I think &quot;Not wanting to use SSH agent forwarding&quot; is the answer. I don&#x27;t want every single machine I use to be able to authenticate as me to anyone else. If I actually want to be able to connect to a third machine, I&#x27;ll have an SSH key on the second machine. For instance, my phone has an SSH key to SSH&#x2F;mosh to my VPS, and my VPS has a different SSH key that can authenticate to GitHub. If I suspect my VPS got compromised, I can kill its key on GitHub without having to worry about whether my single, master, local key got compromised. Given that ssh-keygen is so easy and basically every server I want to talk to supports multiple authorized_keys, I haven&#x27;t seen much use for agent forwarding.<p>Also, mosh was developed at MIT, where there&#x27;s a good Kerberos setup for most SSH-able machines. So if you really want forwarding, you can forward your Kerberos ticket with the initial SSH connection. The mosh-server command on Athena is actually a wrapper script that copies your Kerberos ticket (so it&#x27;s not destroyed when the SSH session exits) and sets up a Kerberos + AFS session for the actual mosh-server to run inside:<p><a href="http:&#x2F;&#x2F;web.mit.edu&#x2F;mosh_project&#x2F;arch&#x2F;amd64_deb60&#x2F;bin&#x2F;mosh-server" rel="nofollow">http:&#x2F;&#x2F;web.mit.edu&#x2F;mosh_project&#x2F;arch&#x2F;amd64_deb60&#x2F;bin&#x2F;mosh-se...</a><p>There&#x27;s little use for key-based authentication on Athena, let alone agent forwarding, because if you <i>don&#x27;t</i> forward Kerberos tickets, you don&#x27;t have access to your network home directory.