菜单
Fix SSH authentication failures in tmux sessions. Use when git push, git pull, git fetch, ssh, or scp fails with authentication, permission denied, or socket errors inside tmux. Also use when the user mentions SSH agent forwarding, SSH_AUTH_SOCK, or stale SSH sockets.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/negz/nix --skill tmux-ssh-socket命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | tmux-ssh-socket |
| description | Fix SSH authentication failures in tmux sessions. Use when git push, git pull, git fetch, ssh, or scp fails with authentication, permission denied, or socket errors inside tmux. Also use when the user mentions SSH agent forwarding, SSH_AUTH_SOCK, or stale SSH sockets. |
When you reconnect to a tmux session, the SSH_AUTH_SOCK environment variable
inside tmux still points to the old socket path from the previous connection.
The old socket is dead, so any SSH operation (git push, git pull, ssh, scp) fails
with authentication errors.
eval $(tmux showenv -s SSH_AUTH_SOCK)
This reads the current SSH_AUTH_SOCK value from the tmux server environment
(which gets updated on each new SSH connection) and exports it into the current
shell.
Run this fix when an SSH-dependent command fails inside tmux. Common symptoms:
git push or git pull fails with "Permission denied (publickey)"ssh fails with "Could not open a connection to your authentication agent"After running the fix, retry the failed command.