Terminal > Code
Feature support over SSH
# Feature support over SSH When you [Warpify an SSH session](/terminal/warpify/ssh/), Warp's core terminal features — the input editor, completions, blocks, history search, and more — work the same as they do locally. With Warp's [SSH extension](/terminal/warpify/ssh/#installing-the-ssh-extension) installed on the remote host, additional coding features such as the file tree, native file reading, and native code diffs also work over SSH on macOS and Linux. This page documents which features are available based on which path you're on: * **SSH extension** - Installed on first connect when you choose **Install Warp's SSH extension**. Available on macOS and Linux remote hosts. * **Legacy tmux-based Warpification** - An older alternative that's being deprecated. It remains available today for clients that don't yet ship the SSH extension (for example, Windows clients). See [Legacy: tmux-based Warpification](/terminal/warpify/ssh/#legacy-tmux-based-warpification). :::note When a native tool isn't available on the current path, the Agent falls back to terminal commands (e.g. `cat`, `sed`, `grep`). You can still accomplish most coding tasks, but the experience is less seamless than working locally or through the SSH extension. ::: ## Features that work over SSH The following features work in Warpified remote sessions on both paths: * **Agent Mode conversations** — Chat with the Agent, ask questions, and request code changes on the remote host. * **Running shell commands** — The Agent can execute commands on the remote machine on your behalf. * **Grep and file glob** — The Agent can search for files and patterns using terminal-based grep and glob tools. * **MCP tools** — Model Context Protocol integrations remain available. * **Terminal features** — The input editor, command completions, autosuggestions, command history, blocks, and all other core terminal features work as expected. The following features require the **SSH extension**: * **File tree (Project Explorer)** — The [file tree sidebar](/code/code-editor/file-tree/) reflects the remote project structure and updates as you navigate or change files. * **Native file reading** — The Agent reads remote files through Warp's built-in file reading tool instead of shelling out to `cat`. * **Native code diffs** — The Agent applies edits as inline [code diffs](/agent-platform/local-agents/code-diffs/) you can review and approve, instead of using `sed` or other shell commands. * **Reliable, parallel completions** — Generators run in parallel over a single multiplexed connection, so completions stop hitting the remote host's `MaxSessions` ceiling and stop occasionally injecting errors into your blocks. ## Features not yet available over SSH The following features require local filesystem access and are not yet available in Warpified remote (SSH) sessions on either path: * **Code editor (file open/edit UI)** — Warp's [native code editor](/code/code-editor/) is not yet available in remote sessions. You cannot open, view, or edit remote files in Warp's built-in editor. * **Computer use** — The Agent cannot take screenshots or interact with the remote machine's desktop. :::note WSL sessions have the same limitations as SSH and are not currently covered by the SSH extension. Feature request for WSL support: [GitHub #6744](https://github.com/warpdotdev/Warp/issues/6744). :::A reference for which Warp coding features are available over SSH and which are limited to local sessions.
When you Warpify an SSH session, Warp’s core terminal features — the input editor, completions, blocks, history search, and more — work the same as they do locally. With Warp’s SSH extension installed on the remote host, additional coding features such as the file tree, native file reading, and native code diffs also work over SSH on macOS and Linux.
This page documents which features are available based on which path you’re on:
- SSH extension - Installed on first connect when you choose Install Warp’s SSH extension. Available on macOS and Linux remote hosts.
- Legacy tmux-based Warpification - An older alternative that’s being deprecated. It remains available today for clients that don’t yet ship the SSH extension (for example, Windows clients). See Legacy: tmux-based Warpification.
Features that work over SSH
Section titled “Features that work over SSH”The following features work in Warpified remote sessions on both paths:
- Agent Mode conversations — Chat with the Agent, ask questions, and request code changes on the remote host.
- Running shell commands — The Agent can execute commands on the remote machine on your behalf.
- Grep and file glob — The Agent can search for files and patterns using terminal-based grep and glob tools.
- MCP tools — Model Context Protocol integrations remain available.
- Terminal features — The input editor, command completions, autosuggestions, command history, blocks, and all other core terminal features work as expected.
The following features require the SSH extension:
- File tree (Project Explorer) — The file tree sidebar reflects the remote project structure and updates as you navigate or change files.
- Native file reading — The Agent reads remote files through Warp’s built-in file reading tool instead of shelling out to
cat. - Native code diffs — The Agent applies edits as inline code diffs you can review and approve, instead of using
sedor other shell commands. - Reliable, parallel completions — Generators run in parallel over a single multiplexed connection, so completions stop hitting the remote host’s
MaxSessionsceiling and stop occasionally injecting errors into your blocks.
Features not yet available over SSH
Section titled “Features not yet available over SSH”The following features require local filesystem access and are not yet available in Warpified remote (SSH) sessions on either path:
- Code editor (file open/edit UI) — Warp’s native code editor is not yet available in remote sessions. You cannot open, view, or edit remote files in Warp’s built-in editor.
- Computer use — The Agent cannot take screenshots or interact with the remote machine’s desktop.