Cite as: Real Problem AI problem “Can an AI coding agent on a remote machine use my SSH keys to push to my repos?”. Opportunity score 7.8 out of 10 (severity 8, AI feasibility 8, market signal 8, competition gap 7). Category AI / Agents. Trend Agents. Source signal: Hacker News thread "ChatGPT Desktop forwards your SSH agent to remote machines", 9 November 2026, 212 points.. Canonical URL: https://www.realproblem.ai/archive/can-an-ai-coding-agent-on-a-remote-machine-use-my-ssh-keys-to-push-to-my-repos.
Can an AI coding agent on a remote machine use my SSH keys to push to my repos?
When a desktop AI app or coding agent connects to a remote box with SSH agent forwarding on, anything running there can sign in with the developer's local keys, so it could push to private GitHub repos or reach other servers without the developer seeing a prompt.
Who has it: Developers and DevOps engineers who let ChatGPT Desktop, Codex, Claude Code or similar agents work on remote dev boxes, devcontainers or cloud VMs over SSH.
- Severity8/10
- Feasible today8/10
- Market signal8/10
- Competition gap7/10
Heard in public
“The agent running on a remote machine can authenticate using your local SSH credentials. That means it can push to your private repos on GitHub, for example.”
Quoted word for word from the public post linked below. Nobody submitted it to Real Problem AI.
Hacker News thread "ChatGPT Desktop forwards your SSH agent to remote machines", 9 November 2026, 212 points.What nothing does yet
A local checker that lists every tool and config entry that turns on SSH agent forwarding, shows which remote hosts and agents can currently use your keys, flags forwarding to machines where an AI agent runs, and switches those sessions to per-use confirmation or a scoped deploy key in one step.
Tools that solve this
3 named so far, and where each one stops.
- ForwardAgent no in ~/.ssh/config
Commenters suggest turning forwarding off for every host except a short trusted list, but tools like devpod and Docker sandboxes write their own SSH config entries and can switch it back on.
- Hardware or enclave backed SSH keys (YubiKey, Secretive, Bitwarden SSH agent)
A touch, fingerprint or confirm prompt for each use stops silent signing, but most developers still keep plain key files in the default agent.
- Running agents under a separate user account or VM
Works, but each developer has to build it by hand and it is easy to forget when a new tool adds remote sessions.
Why it is archived
duplicate of NOV89 (same source and quote)
How you might build it
- 01Parser for ~/.ssh/config, includes and tool generated host entries
- 02Watcher on SSH_AUTH_SOCK and active forwarded sessions
- 03Per-use confirmation through ssh-add -c or a hardware key
- 04Scoped deploy keys per repo created through the GitHub API
- 05Alert when a new app adds ForwardAgent to a host
#NOV92 · Canonical URL: https://www.realproblem.ai/archive/can-an-ai-coding-agent-on-a-remote-machine-use-my-ssh-keys-to-push-to-my-repos