Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions src/content/docs/agents/cli-agents/claude-code.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -70,6 +70,8 @@ Claude Code supports Warp's full set of agent integration features:
* **Tab Configs** - Save and restore Claude Code session configurations.
* **[Remote Control](/agents/cli-agents/remote-control/)** - Publish your Claude Code session so you can monitor and steer it from another device.

Claude Code sessions do **not** appear in the Conversation Panel or Agent Management Panel. Those surfaces list Warp Agent conversations and cloud runs. For where third-party CLI agents show up, see [Third-party CLI agents overview](/agents/cli-agents/overview/#where-third-party-cli-agents-appear).

## Related pages

* [How to set up Claude Code](/guides/external-tools/how-to-set-up-claude-code/) — step-by-step setup guide
Expand Down
11 changes: 11 additions & 0 deletions src/content/docs/agents/cli-agents/overview.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -45,6 +45,17 @@ When you launch a supported agent inside Warp, the **agent toolbelt** appears au
<figcaption>The agent toolbelt for CLI agents.</figcaption>
</figure>

## Where third-party CLI agents appear

Third-party CLI agents run inside a terminal pane. Warp detects the session and shows status on that pane and in [vertical tabs](/terminal/windows/vertical-tabs/), not as Warp Agent conversation threads.

* **Conversation Panel** - Lists Warp Agent conversations and cloud agent runs. Claude Code, Codex, OpenCode, and other third-party CLI agents do **not** appear there.
* **Agent Management Panel** - Manages Warp-managed agents and cloud runs. Third-party CLI agents do **not** appear there.
* **Vertical tabs and the agent toolbelt** - Show live third-party CLI agent status while the process is running in a pane.
* **Remote Control** - Publishes a running third-party session so you can monitor or steer it from another device. See [Remote Control](/agents/cli-agents/remote-control/).

If you expected a Claude Code session in the Conversation Panel, that is expected behavior today. Keep the session in its tab, use vertical-tab status, or publish it with Remote Control.

## Feature support

Not every feature is available for every agent. The table below shows current support.
Expand Down
1 change: 1 addition & 0 deletions src/content/docs/agents/cli/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -53,3 +53,4 @@ If you already use the Warp app, most of your setup carries over. Rules and skil
* [Input and shell commands](/agents/cli/input-and-shell-commands/) - Compose prompts and run shell commands from the same input.
* [Configuration](/agents/cli/configuration/) - Customize the CLI with the settings file.
* [Reference](/agents/cli/reference/) - Flags, slash commands, and keyboard shortcuts.
* [Uninstall the Warp Agent CLI](/support-and-community/troubleshooting-and-support/logging-out-and-uninstalling/#uninstalling-the-warp-agent-cli) - Remove the CLI without removing the Warp app.
5 changes: 5 additions & 0 deletions src/content/docs/agents/cli/quickstart.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -115,8 +115,13 @@ Run the printed command later to pick up where you left off.

To browse and reopen past conversations from inside the CLI, see [Agent conversations](/agents/cli/agent-conversations/#conversation-history).

## Uninstall the Warp Agent CLI

The CLI is separate from the Warp desktop app. To remove an install-script or Homebrew install, and optional local agent data, see [Uninstalling the Warp Agent CLI](/support-and-community/troubleshooting-and-support/logging-out-and-uninstalling/#uninstalling-the-warp-agent-cli).

## Next steps

* [Agent conversations](/agents/cli/agent-conversations/) - Work with the transcript, code diffs, plans, and tasks.
* [Customizing the CLI](/agents/cli/configuration/) - Rules, skills, MCP servers, themes, and settings.
* [Reference](/agents/cli/reference/) - All flags, slash commands, and keyboard shortcuts.
* [Logging out & uninstalling](/support-and-community/troubleshooting-and-support/logging-out-and-uninstalling/#uninstalling-the-warp-agent-cli) - Remove the CLI binary and related local files.
Original file line number Diff line number Diff line change
Expand Up @@ -46,6 +46,14 @@ The notebook will not be saved until either title or body text is added.
<figcaption>Editing a Notebook.</figcaption>
</figure>

### Open an existing notebook

* Open the [Warp Drive](/knowledge-and-collaboration/warp-drive/) panel and select the notebook.
* Search for the notebook title in the [Command Palette](/terminal/command-palette/).
* Open a shared or local deep link. Warp Drive share links use a web URL such as `https://app.warp.dev/drive/notebook/NAME-OBJECT_ID`. You can also open the notebook directly in the app with `warp://drive/notebook?id=OBJECT_ID`. See [Warp URI scheme](/terminal/more-features/uri-scheme/#warp-drive-objects).

Notebooks are not a pane type you can launch from a [Tab Config](/terminal/windows/tab-configs/) today. Use a Drive link, the Command Palette, or the Warp Drive panel after the window opens.

### Working with Notebooks

#### Adding new elements
Expand Down Expand Up @@ -173,4 +181,12 @@ Only one editor is allowed at a given time. Opening the notebook while there is

### Import and export notebooks in Warp Drive

See our [Warp Drive Import and Export](/knowledge-and-collaboration/warp-drive/#import-and-export) instructions.
Notebooks import from and export to Markdown (`.md`). Use the Warp Drive import and export flow described in [Import and export](/knowledge-and-collaboration/warp-drive/#import-and-export).

When you import a Markdown file:

* Headings, paragraphs, lists, tables, and fenced code blocks are preserved as notebook elements when the editor supports them.
* Fenced blocks tagged as shell languages (for example `bash`, `sh`, or `shell`) become **command blocks** you can insert and run in the terminal.
* Other fenced languages become **code blocks** with syntax highlighting when Warp recognizes the language.

Export writes the notebook back to Markdown so you can edit it outside Warp or check it into a repository.
Original file line number Diff line number Diff line change
Expand Up @@ -57,7 +57,9 @@ There is a known issue that can occur that causes online features to break ([Age

### English-only UI

Nov 2021: We have added character support for Chinese, Korean, and Japanese, but our UI currently only supports English.
Warp's interface is English-only. There is no language or locale setting in **Settings**, and no supported workaround to switch the UI to another language.

The terminal can display Chinese, Korean, and Japanese characters in command output and editor text. For localization requests and status, see open [GitHub issues about language support](https://github.com/warpdotdev/Warp/issues?q=is%3Aissue+is%3Aopen+language+OR+i18n+OR+locale).

### Abnormal rendering of Chinese characters

Expand Down
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
title: "Logging out & uninstalling"
description: >-
How to log out from Warp, and how to uninstall Warp.
Log out of Warp, uninstall the Warp app, or remove the Warp Agent CLI and its local files.
sidebar:
label: "Logging Out & Uninstalling"
---
Expand Down Expand Up @@ -165,3 +165,65 @@ If you're using Warp Preview, replace "Warp-Stable" with "Warp-Preview" in the c
```
</TabItem>
</Tabs>

## Uninstalling the Warp Agent CLI

The [Warp Agent CLI](/agents/cli/) is a separate install from the Warp desktop app. Removing the app does not remove the CLI, and removing the CLI does not uninstall the app.

### Install-script installs (macOS, Linux, and Windows)

The install script places a versioned install under a data directory and puts a `warp` entry on your `PATH`.

Default locations:

* **macOS and Linux** - Install root `~/.warp/tui/` (versioned binaries under `versions/`, active build at `current`), symlink at `~/.local/bin/warp`
* **Windows** - Install root `%LOCALAPPDATA%\Warp\tui\`, CLI entry under `%LOCALAPPDATA%\Warp\bin\`

If you overrode the defaults with `WARP_TUI_INSTALL_DIR` or `WARP_TUI_BIN_DIR` when you installed, remove those paths instead.

<Tabs>
<TabItem label="macOS and Linux">
```bash
# Remove the PATH entry for the CLI
rm -f "${WARP_TUI_BIN_DIR:-$HOME/.local/bin}/warp"

# Remove the versioned install (binaries, auto-updater state)
rm -rf "${WARP_TUI_INSTALL_DIR:-$HOME/.warp/tui}"
```
</TabItem>
<TabItem label="Windows">
Run these commands in PowerShell:

```powershell
$installDir = if ($env:WARP_TUI_INSTALL_DIR) { $env:WARP_TUI_INSTALL_DIR } else { Join-Path $env:LOCALAPPDATA 'Warp\tui' }
$binDir = if ($env:WARP_TUI_BIN_DIR) { $env:WARP_TUI_BIN_DIR } else { Join-Path $env:LOCALAPPDATA 'Warp\bin' }

# Remove CLI entries on PATH (name depends on installer version)
Get-ChildItem -Path $binDir -Filter 'warp*' -ErrorAction SilentlyContinue | Remove-Item -Force

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ [IMPORTANT] This wildcard can remove other Warp CLI channels or unrelated warp* launchers from the selected bin directory; document the exact launcher names to remove or constrain the cleanup to the stable CLI entry.


# Remove the versioned install
Remove-Item -Path $installDir -Recurse -Force -ErrorAction SilentlyContinue
```
</TabItem>
</Tabs>

### Homebrew installs

```bash
brew uninstall --cask warp-agent-cli
```

### Optional local data

These directories are shared with other Warp agent surfaces. Remove them only if you no longer need the data:

* **Agent config** - `~/.agents/` (on Windows, `%USERPROFILE%\.agents\`)
* **MCP config and bundled skills** - `~/.warp/.mcp.json` and `~/.warp/skills/` (on Windows, under `%USERPROFILE%\.warp\`)

:::caution
Deleting `~/.warp/` also removes MCP config and skills used by the Warp desktop app. Prefer deleting only the CLI install paths above unless you intend a full cleanup.
:::

To confirm the CLI is gone, open a new terminal and run `warp --version`. The shell should report that the command was not found.

For install steps, see the [Warp Agent CLI quickstart](/agents/cli/quickstart/).
38 changes: 36 additions & 2 deletions src/content/docs/terminal/more-features/uri-scheme.mdx
Original file line number Diff line number Diff line change
@@ -1,8 +1,7 @@
---
title: Warp URI Scheme
description: >-
Warp's URI scheme enables you to programmatically open new windows, tabs,
launch configurations, or tab configs with ease.
Open windows, tabs, Tab Configs, Settings, and Warp Drive objects with warp:// deep links.
sidebar:
label: "Warp URI scheme"
---
Expand All @@ -16,12 +15,47 @@ There are several ways to use the URI scheme:
* Open new tab `warp://action/new_tab?path=<path_to_folder>`
* Open Launch Configuration `warp://launch/<launch_configuration_path>`
* Open Tab Config `warp://tab_config/<name>` — opens the saved [Tab Config](/terminal/windows/tab-configs/) as a new tab in the active window. Append `?new_window=true` to open it in a new window instead. `<name>` is matched case-insensitively against the file stem of the `.toml`, so both `warp://tab_config/my_tab` and `warp://tab_config/my_tab.toml` resolve to `my_tab.toml`.
* Open a Warp Drive object `warp://drive/<object_type>?id=<object_id>` — opens a notebook, workflow, folder, or environment variables object. See [Warp Drive objects](#warp-drive-objects).
* Open Settings `warp://settings` — opens the Settings window. See [Settings deep links](#settings-deep-links) for search, widget, and sub-page options.

:::note
[Warp Preview](/support-and-community/community/warp-preview-and-alpha-program/) URI scheme begins with `warppreview://`
:::

## Warp Drive objects

Open a saved Drive object by type and ID:

```text
warp://drive/notebook?id=OBJECT_ID
warp://drive/workflow?id=OBJECT_ID
warp://drive/folder?id=OBJECT_ID
warp://drive/env-vars?id=OBJECT_ID
```

* **`OBJECT_ID`** - The object's ID from a shared Drive link. When you copy a link from Warp Drive, Warp produces a web URL such as `https://app.warp.dev/drive/notebook/NAME-OBJECT_ID`. The final hyphen-separated segment is the ID to pass as `id`.
* **Optional query params** - `focused_folder_id` focuses a folder in the Drive panel, and `invitee_email` can prefill an invite when the link is used for sharing flows.

Example:

```bash
open "warp://drive/notebook?id=LkDlnAe34vfYD2JXsAkssc"
```

On Linux, pass the same URI to `xdg-open`. On Windows, use `Start-Process` with the URI string.

For creating and sharing notebooks, see [Warp Drive Notebooks](/knowledge-and-collaboration/warp-drive/notebooks/).

## What the URI scheme does not do

The `warp://` scheme opens Warp surfaces. It does **not**:

* Run a shell command, script, or agent prompt in the new tab or window
* Wait for interactive input and return a result to the caller
* Target or control an already-open tab or pane

To open a layout that runs startup commands, save a [Tab Config](/terminal/windows/tab-configs/) and open it with `warp://tab_config/<name>`. For a longer-running agent session you can monitor later, use [Remote Control](/agents/cli-agents/remote-control/) after the agent is already running.

## Settings deep links

Open the Settings window directly, optionally jumping to a specific page, widget, or search:
Expand Down
5 changes: 5 additions & 0 deletions src/content/docs/terminal/settings/file-locations.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -53,6 +53,7 @@ The tables below cover the **Stable** channel. For **Preview**, see [Preview cha
* **MCP server config** - `~/.warp/.mcp.json`
* **Bundled skills** - `~/.warp/skills/`
* **Agent config** - `~/.agents/`
* **Warp Agent CLI install** (install-script default) - `~/.warp/tui/` with a `warp` symlink in `~/.local/bin/`
</TabItem>
<TabItem label="Windows">
On Windows, Warp follows the platform conventions used by the [`directories`](https://docs.rs/directories) crate, which splits user data across `%APPDATA%` (Roaming) and `%LOCALAPPDATA%` (Local). Themes and tab configs are portable and live in Roaming, while settings, logs, and the local database are machine-specific and live in Local. Two separate `data\` directories exist as a result — one under each root — so check the full path when locating files.
Expand Down Expand Up @@ -82,6 +83,7 @@ The tables below cover the **Stable** channel. For **Preview**, see [Preview cha
* **MCP server config** - `%USERPROFILE%\.warp\.mcp.json`
* **Bundled skills** - `%USERPROFILE%\.warp\skills\`
* **Agent config** - `%USERPROFILE%\.agents\`
* **Warp Agent CLI install** (install-script default) - `%LOCALAPPDATA%\Warp\tui\` with CLI entries under `%LOCALAPPDATA%\Warp\bin\`
</TabItem>
<TabItem label="Linux">
On Linux, Warp follows the [XDG Base Directory Specification](https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html). Each path below uses the standard XDG environment variable with its default fallback.
Expand Down Expand Up @@ -110,9 +112,12 @@ The tables below cover the **Stable** channel. For **Preview**, see [Preview cha
* **MCP server config** - `~/.warp/.mcp.json`
* **Bundled skills** - `~/.warp/skills/`
* **Agent config** - `~/.agents/`
* **Warp Agent CLI install** (install-script default) - `~/.warp/tui/` with a `warp` symlink in `~/.local/bin/`
</TabItem>
</Tabs>

For removing the Warp Agent CLI without uninstalling the desktop app, see [Uninstalling the Warp Agent CLI](/support-and-community/troubleshooting-and-support/logging-out-and-uninstalling/#uninstalling-the-warp-agent-cli).

## Preview channel paths

Preview uses a separate set of directories so it never overwrites your Stable config:
Expand Down
Loading