docs: Document Warp's SSH extension and feature support over SSH

src/content/docs/agent-platform/capabilities/codebase-context.mdx

@@ -38,12 +38,13 @@ When you open a directory in Warp, we check if it is part of a Git repository. I
 Code indexed with Codebase Context is never stored on our servers. Codebase Context works with both local agent sessions and [cloud agent runs](/agent-platform/cloud-agents/overview/). Without Codebase Context enabled, agents will still be able use terminal commands (i.e. `grep`, `sed`) to navigate your code.
 :::
 
-:::danger
-**Codebase Context doesn't work within SSH or WSL sessions.** \
-\
-Feature requests for support are being tracked in the following GitHub issues: \
-\- SSH: [https://github.com/warpdotdev/Warp/issues/6831](https://github.com/warpdotdev/Warp/issues/6831)\
-\- WSL: [https://github.com/warpdotdev/Warp/issues/6744](https://github.com/warpdotdev/Warp/issues/6744)
+:::caution
+**Codebase Context (semantic indexing and search) is not yet available in SSH or WSL sessions.**
+
+Feature requests:
+
+* SSH: [GitHub #6831](https://github.com/warpdotdev/Warp/issues/6831)
+* WSL: [GitHub #6744](https://github.com/warpdotdev/Warp/issues/6744)
 :::
 
 ![Codebase indexing settings in Warp. Easily track sync status and manage which folders are indexed for AI-powered context and suggestions.](../../../../assets/agent-platform/codebase-context-main.png)

src/content/docs/code/code-editor/file-tree.mdx

@@ -9,6 +9,10 @@ description: >-
 
 Warp includes a **native file tree** that makes it easy to explore and manage project files. The file tree is available whenever in any directory and it automatically reflects your project structure as files are added, removed, or changed.
 
+:::note
+The file tree also works over SSH on macOS and Linux when Warp's [SSH extension](/terminal/warpify/ssh/#installing-the-ssh-extension) is installed on the remote host.
+:::
+
 ### Opening the file tree
 
 You can open the file tree from the tools panel on the left hand side:

src/content/docs/code/overview.mdx

@@ -7,7 +7,7 @@ description: >-
 import VideoEmbed from '@components/VideoEmbed.astro';
 
 :::note
-Several coding features — including Codebase Context, code diffs, the code editor, and the file tree — are not yet available in SSH or WSL sessions.
+On macOS and Linux SSH sessions, Warp's [SSH extension](/terminal/warpify/ssh/#installing-the-ssh-extension) brings the file tree, native file reads, and native code diffs to remote hosts. See [Feature support over SSH](/code/ssh-feature-support/) for the current support matrix.
 :::
 
 ## From prompt to production
@@ -34,7 +34,7 @@ Warp’s coding agent is designed to help you generate, edit, and manage code di
 <VideoEmbed url="https://youtu.be/W8rCsznM5HA" title="Coding Features Overview" />
 
 :::note
-Warp's coding agent only works on local repositories. The agent can make changes on remote or docker repositories, but falls back to using terminal commands (i.e. `sed`, `grep` ) to make the changes.
+With the [SSH extension](/terminal/warpify/ssh/#installing-the-ssh-extension) installed on a remote macOS or Linux host, the coding agent applies edits using Warp's native diff tool over SSH. When the extension isn't installed, the agent falls back to terminal commands (i.e. `sed`, `grep`) to make changes.
 :::
 
 ### Examples of coding capabilities

src/content/docs/code/ssh-feature-support.mdx

@@ -5,34 +5,41 @@ description: >-
   are limited to local sessions.
 ---
 
-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. However, several coding-specific features are **not yet available** in remote sessions because the Agent cannot directly access the remote filesystem.
+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 is unavailable, the Agent automatically falls back to terminal commands (e.g. `cat`, `sed`, `grep`) to read and edit files. You can still accomplish most coding tasks over SSH, but the experience may be less seamless than working locally.
+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 are fully available in Warpified remote sessions:
+The following features work in Warpified remote sessions on both paths:
 
-* **Agent Mode conversations** — You can chat with the Agent, ask questions, and request code changes. The Agent will use terminal commands to interact with the remote filesystem.
+* **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:
+The following features require local filesystem access and are not yet available in Warpified remote (SSH) sessions on either path:
 
-* **Codebase Context (indexing and search)** — Warp cannot index or semantically search a remote codebase. The Agent will not have access to your full project context when generating responses. Feature request: [GitHub #6831](https://github.com/warpdotdev/Warp/issues/6831)
-* **Native file reading** — The Agent cannot read files through Warp's built-in file reading tool. It falls back to terminal commands like `cat` to read file contents.
-* **Code diffs** — The Agent cannot apply code diffs natively. It falls back to terminal commands like `sed` to make file edits.
-* **Code editor** — Warp's [native code editor](/code/code-editor/) is not yet available in remote sessions. You cannot open, view, or edit files in Warp's built-in editor over SSH.
-* **File tree (Project Explorer)** — The [file tree sidebar](/code/code-editor/file-tree/) is not yet available in remote sessions.
-* **Code review panel** — The [Code Review](/code/code-review/) panel for reviewing Git diffs is not yet available for remote repos.
+* **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. Feature request for WSL support: [GitHub #6744](https://github.com/warpdotdev/Warp/issues/6744)
+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).
 :::

src/content/docs/terminal/warpify/index.mdx

@@ -7,7 +7,7 @@ description: >-
 import DemoVideo from '@components/DemoVideo.astro';
 
 1. [Subshells](/terminal/warpify/subshells/), Warp supports enabling Warp features in subshells for bash, zsh, and fish.
-2. [SSH](/terminal/warpify/ssh/), Warp supports a tmux powered wrapper that enables Warp features in remote (SSH) sessions.
+2. [SSH](/terminal/warpify/ssh/), Warp's SSH extension brings the file tree, reliable completions, and native code diffs to remote macOS and Linux hosts. Legacy tmux-based Warpification is still available for clients that don't yet ship the extension.
 3. [SSH Legacy](/terminal/warpify/ssh-legacy/), Warp supports a legacy wrapper that enables Warp features in remote (SSH) sessions.
 
 ## Subshells