- Security: Prompt injection risk is contained to the credentials / files on the remote machine.
- SSH remotes pair nicely with agentic git identities
- Performance: Run many, many agents in parallel while maintaining good battery life and UI performance

- a hostname (e.g.
my-server.com) - a username and hostname (e.g.
user@my-server.com) - an alias from your
~/.ssh/config, e.g.my-server - anything that passes through
ssh <host>can be used as a host
ssh command, so you can set up advanced
configuration for your agent host in your local ~/.ssh/config file.
Here’s an example of a config entry:
Authentication
As we delegate to
ssh, this is really an abbreviated reference of how ssh authenticates.Local default keys
ssh will check these locations by default:
SSH Agent
If you have an SSH agent running, you can add your key:ssh will use it to authenticate.
Config
You can also configure authentication in your~/.ssh/config file.
Coder Workspaces
If you’re using Coder Workspaces, you can use an existing Workspace as a mux agent host:- Run
coder config-ssh - Use
coder.<workspace-name>as your SSH host when creating a new mux workspace