> For the complete documentation index, see [llms.txt](https://docs.gotempest.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gotempest.app/integrations/tempest-remote-editors.md).

# Tempest Remote — Editors & AI Clients

Open saved Tempest SSH servers in VS Code, Cursor, JetBrains, Zed, Codex and Claude Code.

Use your saved Tempest servers in your editor or AI client. Tempest CLI manages accounts, vaults, SSH credentials, proxies and jump hosts. The Tempest desktop app does not need to remain open.

Before connecting, install and sign in to Tempest CLI, save the SSH server in Tempest, and allow TCP forwarding in its vault. Existing connections keep their assigned SSH alias; new ones receive a human-readable name.

## VS Code

**Package:** VS Code extension (`.vsix`) · [Downloads](https://github.com/tempest-term/tempest-remote-editors/releases/latest) · [Marketplace](https://marketplace.visualstudio.com/items?itemName=AltasExpressLLC.tempest-remote)

Install **Tempest Remote** and **Microsoft Remote - SSH** in your local VS Code. For a downloaded VSIX, use **Extensions: Install from VSIX…**. The Marketplace identity remains `AltasExpressLLC.tempest-remote`.

1. Open the Command Palette or click the remote indicator.
2. Choose **Tempest: Connect to Server**.
3. Select a saved server and enter the absolute remote project folder.
4. Complete the local authentication prompts. VS Code opens a remote window and installs or starts VS Code Server.

Use **Tempest: Open Settings** to choose the Tempest CLI executable if it is outside VS Code's PATH. Keep Remote - SSH's Unix-domain socket mode disabled. Errors appear in **Output → Tempest Remote** or **Remote - SSH**. To refresh an expired connection, reconnect through the Tempest command.

## Cursor

**Package:** Cursor extension (`.vsix`) · [Downloads](https://github.com/tempest-term/tempest-remote-editors/releases/latest)

Install the Cursor-specific VSIX with **Extensions: Install from VSIX…**, together with **Anysphere Remote SSH** (`anysphere.remote-ssh`).

1. Open the Command Palette and choose **Tempest: Connect to Server**.
2. Select a saved server and enter the absolute remote project folder.
3. Complete authentication in the local dialogs. Cursor opens the remote folder and starts its own remote server.

**Tempest: Open Settings** opens the CLI executable setting. Use the Cursor package rather than the VS Code package: the two use different Remote SSH providers. Their source and tests are shared.

## JetBrains

**Package:** JetBrains plugin (`.zip`) · [Downloads](https://github.com/tempest-term/tempest-remote-editors/releases/latest)

Install the ZIP with **Settings → Plugins → gear → Install Plugin from Disk** in JetBrains Gateway. Install Node.js and an up-to-date Tempest CLI locally. JetBrains licensing and remote host requirements apply.

1. Open **Tempest** in Gateway. Saved servers load automatically.
2. Select a server, click **Continue in Gateway**, and answer any Tempest authentication prompts locally.
3. In Gateway's native SSH wizard, choose the **Tempest · server-name** connection.
4. Use Gateway's own screens to select the project and IDE, install or reuse a backend, and open the JetBrains Client.

Gateway handles IDE versions, downloads, installation, startup, progress, cancellation and remote requirements. The Tempest plugin only prepares and registers the CLI-managed SSH connection. It does not run its own IDE installer, startup script or readiness polling.

**Back** returns to Gateway; **Refresh** reloads saved servers. **Advanced settings** only contains the Node.js and Tempest CLI executable paths. To disconnect or stop a backend, use Gateway's native controls.

Tempest CLI supplies its existing loopback SSH endpoint, local authentication key and public host key. Gateway connects directly with its native SSH client and strictly verifies the actual endpoint. VS Code, Cursor and Codex continue to use ProxyCommand. If a prepared connection expires, select the server from Tempest again.

## Zed

**Package:** Standalone launcher (`.zip`) · [Downloads](https://github.com/tempest-term/tempest-remote-editors/releases/latest)

Zed currently uses the standalone Tempest launcher. There is no in-editor Tempest server picker or Zed skill yet, so this is the one editor integration that currently requires a launcher command.

Install Zed with its `zed` executable, Node.js and OpenSSH. Extract the launcher ZIP and run from the extracted folder:

```sh
node scripts/remote.js connect --server ubuntu-cloudnet --editor zed --folder /home/me/project
```

Replace the server label and absolute folder path with your saved server and project. The launcher prepares the Tempest connection and opens Zed's native SSH workspace. Keep it running while editing; Ctrl+C releases its attachment. Re-run it to refresh an expired connection. Zed performs its own remote-server installation.

## Codex

**Plugin:** Tempest · [Plugin repository and downloads](https://github.com/tempest-term/tempest-remote-codex)

Install and enable **Tempest** in Codex's plugin management, using the Tempest plugin repository as the source. Start a fresh local chat after installation. The plugin includes **remote** and **terminal** skills and registers Tempest MCP. Node.js and OpenSSH are local runtime requirements for the remote helper.

For a remote project, ask:

> Use Tempest to connect to cloudnet for remote development.

The **remote** skill finds the saved server, starts its helper and keeps the SSH connection attached. Open the returned **Add SSH host to Codex** link, connect the host and select your remote project folder. The remote login shell needs an installed, authenticated `codex` on PATH.

For terminal operations in your current conversation, ask:

> Use Tempest to inspect cloudnet's running services.

The **terminal** skill uses MCP tools. It does not switch the chat's project filesystem to the remote host. Ordinary users do not manually invoke the helper. If local interactive authentication is required, follow the skill's prompt; never send passwords, OTPs or PINs in chat.

## Claude Code

**Plugin:** Tempest · [Plugin repository and downloads](https://github.com/tempest-term/tempest-remote-claude)

Install and enable **Tempest** through Claude's plugin management, using the Tempest plugin repository as the source. The plugin includes **remote** and **terminal** skills and registers Tempest MCP. Avoid enabling a duplicate standalone Tempest MCP registration.

For terminal operations, ask:

> Use Tempest to connect to cloudnet and inspect its running services.

The **terminal** skill uses the MCP tools to connect and run commands.

For a native Claude Desktop Code SSH workspace, ask:

> Prepare cloudnet for a Claude Desktop remote Code session.

The **remote** skill finds the saved server and returns an **Open SSH session in Claude** link. Open the link, confirm the host and select the remote folder in Desktop. This link requires Claude Desktop with SSH session link support. It does not move an already-running Claude Code CLI session's filesystem to the remote machine.

Node.js and OpenSSH are local helper dependencies; ordinary users do not type helper commands. If interactive authentication is needed, follow the skill's local instructions. Native Desktop bootstrap has separate requirements: successful SSH preparation alone does not verify the full workspace.

## Authentication and troubleshooting

Credentials, vault unlocks, SSH host-key confirmations and security-key operations are handled locally. Check host-key fingerprints before accepting them. Never put passwords, OTPs or PINs in chat, command arguments or settings.

The relay supports SSH command/terminal channels and TCP forwarding. SFTP subsystem requests, Unix-domain socket forwarding, remote port forwarding, X11 and SSH agent forwarding are outside the current scope. A successful SSH probe verifies the transport, not every editor's native bootstrap. If a connection expires, use the client's Tempest entry or skill to reconnect.

## Developer references

* [Tempest Remote SDK](/integrations/tempest-remote-sdk.md)
* [Remote protocol](/integrations/tempest-remote-plugin-protocol.md)
* [SSH, SCP and rsync](/integrations/tempest-remote-cli-tools.md)
* [Editor integration source](https://github.com/tempest-term/tempest-remote-editors)