Skip to main content
Shux can run workspaces on a remote host over SSH. When configured, tool operations (file reads/edits, bash, etc.) execute on the remote machine.

​
Threat model

Shux treats the remote host as potentially hostile. By default it does not forward your local keys or credentials. The only data synced to the remote machine is:

​
Why use SSH runtime

  • Security: Prompt injection risk is contained to the credentials/files on the remote machine.
  • Performance: Run many agents in parallel without burning laptop CPU/battery.
ssh workspaces

​
Host value

The host field accepts anything you can pass to ssh <host>:
  • a hostname (for example my-server.com)
  • a username and hostname (for example user@my-server.com)
  • an alias from your ~/.ssh/config (for example my-server)
Shux delegates SSH configuration to your system ssh command, so advanced settings live in ~/.ssh/config. Example entry:

​
Authentication

Shux delegates to ssh. This is an abbreviated reference of common ways ssh authenticates.

​
Local default keys

ssh checks these locations by default:

​
SSH agent

If you have an SSH agent running, add your key:

​
~/.ssh/config

You can also set an explicit identity file:

​
Coder Workspaces

If you use Coder, see the Coder runtime page.