Skip to main content

Connect with Remote SSH

Remote SSH connects Kiro IDE to a Linux computer that you can already access through SSH. Your files, terminal commands, and Kiro agent work run on that host while you use the editor on your computer.

Only connect to hosts that you trust. Verify a new or changed host key before connecting. Review any local SSH configuration that can run commands on your computer.

Prerequisites

Your computer can run macOS, Windows, or Linux. The SSH host must have:

  • Linux on x64 or ARM64 with glibc 2.28 or later
  • At least 4 GiB free on the filesystem containing your home directory
  • A home directory that other users cannot write to
  • /bin/sh
  • stat, which, flock, tar, gzip, sha256sum, diff, find, id, sort, and readlink
  • HTTPS access to Kiro download, authentication, and service endpoints

Confirm that your normal SSH client can connect before using Kiro.

Connect to a host

  1. Open the Command Palette.
  2. Select Kiro: Connect to Host….
  3. Select a configured host or Enter SSH Destination….
  4. To save a host, select Add New SSH Host…. Enter user@host or a full SSH command, then choose the SSH configuration file.
  5. Verify the host fingerprint before accepting a new or changed host key.
  6. Complete SSH authentication.
  7. In the new Kiro window, open a folder on the host.
  8. Approve workspace trust and sign in to Kiro if prompted.

Kiro installs the matching remote components on the host. You do not need to install Kiro CLI or Node.js there.

Verify the connection

Open the integrated terminal and run:

bash
hostname pwd

Confirm that the hostname and path belong to the remote computer. Create and save a test file, then ask Kiro to read it. This checks that the editor, terminal, and agent use the same remote workspace.

Use SSH and Kiro sign-in safely

SSH authentication gives you access to the host. Kiro sign-in lets the agent use Kiro services from that host. These are separate sign-ins.

Remote SSH supports keys, certificates, SSH agents, passwords, and keyboard-interactive authentication. Enter secrets only in the prompt that requests them. Never paste a private key, password, certificate, or access token into chat or project files.

Kiro verifies SSH host keys. Stop if a host key changes unexpectedly. Confirm the new fingerprint with the host owner before reconnecting.

Use jump hosts and proxy commands

Remote SSH supports a ProxyJump chain with up to eight hops. It also supports a first-hop ProxyCommand.

Remote SSH does not support:

  • A ProxyCommand after ProxyJump
  • Mixed certificate ProxyJump chains
  • Match exec
  • ProxyUseFdpass

A trusted local SSH configuration may run ProxyCommand on your computer. Review that command before connecting.

Disconnect and return

Select Kiro: Close Remote Connection to disconnect the editor. Reopen the host with Kiro: Connect to Host…, or choose the remote folder from File > Open Recent.

Your project files remain on the host. The remote Kiro window has its own sign-in and chat history. It does not show chats from local Kiro windows. Saved remote chat and accepted agent work can remain available while the host and remote agent keep running. A host shutdown or unavailable remote agent can interrupt that work.

Troubleshoot Remote SSH

  • If a host is missing, select Kiro: Add New SSH Host…, then refresh the list.
  • If installation fails, check the host requirements and free disk space.
  • If a proxy blocks installation, set kiroRemote.httpProxy or kiroRemote.httpsProxy, then restart the remote environment.
  • If Kiro reports an unsupported SSH setting, use a supported configuration for that host.
  • If TLS inspection resets Kiro services, follow TLS inspection compatibility.
Page updated: November 20, 2026