diff --git a/src/content/docs/getting-started/migrate-to-warp/migrate-to-warp-from-claude-code.mdx b/src/content/docs/getting-started/migrate-to-warp/migrate-to-warp-from-claude-code.mdx index d1ccffca..3810b354 100644 --- a/src/content/docs/getting-started/migrate-to-warp/migrate-to-warp-from-claude-code.mdx +++ b/src/content/docs/getting-started/migrate-to-warp/migrate-to-warp-from-claude-code.mdx @@ -43,32 +43,32 @@ Claude Code's authentication (API key or Anthropic account) is handled by Claude ## Switching to Agent Mode from Claude Code -If you're ready to replace Claude Code with Warp's built-in agent, the core workflow is: +If you're ready to replace Claude Code with Warp's built-in Agent, the core workflow is: 1. Open a new tab in Warp. -2. To switch to switch to [Agent Mode](/agent-platform/local-agents/overview/) from terminal mode, press `⌘+Enter` (or `Ctrl+Shift+Enter`) +2. From terminal mode, press `⌘+Enter` (macOS) or `Ctrl+Shift+Enter` (Linux/Windows) to switch to [Agent Mode](/agent-platform/local-agents/overview/). 3. Describe what you want in natural language. -Warp's agent reads your codebase, runs commands, and edits files the same way Claude Code does. +Warp's Agent reads your codebase, runs commands, and edits files the same way Claude Code does. ### What transfers: context and rules -A recurring question from Claude Code users: **what files and context does Warp's agent read automatically?** Warp picks up project rules from an `AGENTS.md` (or `WARP.md`) at your repo root — the direct equivalent of Claude Code's `CLAUDE.md`. Run `/init` in Agent Mode to generate one, or rename your existing rules file and you're done — no rewriting needed. +A recurring question from Claude Code users: **what files and context does Warp's Agent read automatically?** Warp picks up project rules from an `AGENTS.md` (or `WARP.md`) at your repo root — the direct equivalent of Claude Code's `CLAUDE.md`. Run `/init` in Agent Mode to generate one, or rename your existing rules file and you're done — no rewriting needed. -Warp's agent also pulls context from several other explicit sources: +Warp's Agent also pulls context from several other explicit sources: -* **[Codebase Context](/agent-platform/capabilities/codebase-context/)** - when you open a directory, Warp indexes your Git-tracked files so the agent can search and reference your code without you pasting snippets. +* **[Codebase Context](/agent-platform/capabilities/codebase-context/)** - when you open a directory, Warp indexes your Git-tracked files so the Agent can search and reference your code without you pasting snippets. * **[Rules](/agent-platform/capabilities/rules/)** - global and project-scoped rules. `AGENTS.md` and `WARP.md` are automatically picked up at the project root; additional rules live in Warp Drive. -* **[Warp Drive](/knowledge-and-collaboration/warp-drive/)** - notebooks, workflows, and environment variables you've saved are available to the agent as context. -* **[Agent Mode context](/knowledge-and-collaboration/warp-drive/agent-mode-context/)** - pin specific files or notebooks to a conversation so the agent always has them in scope. -* **[MCP](/agent-platform/capabilities/mcp/)** - any MCP servers you've configured give the agent access to external tools and data. +* **[Warp Drive](/knowledge-and-collaboration/warp-drive/)** - notebooks, workflows, and environment variables you've saved are available to the Agent as context. +* **[Agent Mode context](/knowledge-and-collaboration/warp-drive/agent-mode-context/)** - pin specific files or notebooks to a conversation so the Agent always has them in scope. +* **[MCP](/agent-platform/capabilities/mcp/)** - any MCP servers you've configured give the Agent access to external tools and data. ### What to reconfigure * **Bring over your `CLAUDE.md`.** Rename it to `AGENTS.md` (or copy it into a Warp [Rule](/agent-platform/capabilities/rules/) if you want it scoped beyond the repo). Warp applies it automatically to new conversations. * **Set up [MCP servers](/agent-platform/capabilities/mcp/)** you relied on in Claude Code. * **Pick a model** per conversation using the model selector. See [model choice](/agent-platform/capabilities/model-choice/). Warp supports Claude, GPT, Gemini, and Auto. -* **Configure [agent profiles and permissions](/agent-platform/capabilities/agent-profiles-permissions/)** for what the agent can auto-execute. +* **Configure [agent profiles and permissions](/agent-platform/capabilities/agent-profiles-permissions/)** for what the Agent can auto-execute. ### Key differences from Claude Code @@ -79,7 +79,7 @@ Warp's agent also pulls context from several other explicit sources: ## Warp-native equivalents -Claude Code concepts and their closest Warp analog: +Use this table to find the closest Warp equivalent for Claude Code concepts: | From Claude Code | In Warp | | --- | --- | diff --git a/src/content/docs/getting-started/migrate-to-warp/migrate-to-warp-from-cursor.mdx b/src/content/docs/getting-started/migrate-to-warp/migrate-to-warp-from-cursor.mdx index fa431f3c..bb9906a1 100644 --- a/src/content/docs/getting-started/migrate-to-warp/migrate-to-warp-from-cursor.mdx +++ b/src/content/docs/getting-started/migrate-to-warp/migrate-to-warp-from-cursor.mdx @@ -5,22 +5,22 @@ description: >- Cursor, or run Warp alongside Cursor as your agent terminal. --- -Warp gives Cursor users two clean migration paths: keep Cursor as your editor and use Warp for terminal and agent work, or move fully to Warp's built-in code editor and Agent Mode. This page walks through both options. +Warp gives Cursor users two migration paths: keep Cursor as your editor and use Warp for terminal and Agent work, or move fully to Warp's built-in code editor and Agent Mode. This page walks through both options. -## What transfers automatically +## What Warp can help transfer -Warp doesn't ship a Cursor importer. Cursor is built on the VS Code codebase, so its terminal settings live in `settings.json` under keys like `terminal.integrated.fontFamily` and `terminal.integrated.defaultProfile.*`. Open your user settings with **Command Palette** > **Preferences: Open User Settings (JSON)** to reference them while you reconfigure Warp. +Warp doesn't have a one-click Cursor importer. Cursor is built on the VS Code codebase, so its terminal settings live in `settings.json` under keys like `terminal.integrated.fontFamily` and `terminal.integrated.defaultProfile.*`. Because that file is readable, Warp's Agent can translate matching terminal values into Warp's `settings.toml`. In Cursor, open the Command Palette and select **Preferences: Open User Settings (JSON)** to reference your settings while you reconfigure Warp. -## Use Warp's agent to migrate your settings (recommended) +## Use Warp's Agent to migrate your settings (recommended) -The fastest way to bring over your Cursor terminal setup is to ask Warp's agent to translate your `settings.json` directly. Warp ships a [`settings.toml` file](/terminal/settings/) and a bundled `modify-settings` skill that lets the agent read your existing config and write equivalent values into Warp's settings. +The fastest way to bring over your Cursor terminal setup is to ask Warp's Agent to translate your `settings.json` directly. Warp ships a [`settings.toml` file](/terminal/settings/) and a bundled `modify-settings` skill that lets the Agent read your existing config and write equivalent values into Warp's settings. -1. In Warp, open a new tab and switch to [Agent Mode](/agent-platform/local-agents/overview/) with `⌘+I` (macOS) or `Ctrl+I` (Linux/Windows). -2. Paste a prompt like: +1. In the Warp app, open a new tab and switch to [Agent Mode](/agent-platform/local-agents/overview/) with `⌘+I` (macOS) or `Ctrl+I` (Linux/Windows). +2. Paste this prompt into Agent Mode, then press `Enter`. > Read my Cursor `settings.json` (`~/Library/Application Support/Cursor/User/settings.json` on macOS) and port the equivalent terminal settings (font, cursor style, default profile) into my Warp `settings.toml` using the `modify-settings` skill. Show me a diff before applying. -3. Review the proposed diff and approve. Warp hot-reloads `settings.toml`, so changes take effect immediately. +3. Review the proposed diff, then approve the changes. Warp hot-reloads `settings.toml`, so changes take effect immediately. If you'd rather configure each setting manually through the Settings UI, the steps below cover the most common cases. @@ -28,19 +28,19 @@ If you'd rather configure each setting manually through the Settings UI, the ste ### Terminal settings -Terminal settings in Cursor follow the same schema as VS Code. The migration steps are identical to the VS Code terminal migration - see [Migrate to Warp from VS Code terminal](/getting-started/migrate-to-warp/migrate-to-warp-from-vs-code-terminal/) for step-by-step guidance on shell, font, theme, and keybinding setup. +Terminal settings in Cursor follow the same schema as VS Code. The migration steps are identical to the VS Code terminal migration. See [Migrate to Warp from VS Code terminal](/getting-started/migrate-to-warp/migrate-to-warp-from-vs-code-terminal/) for step-by-step guidance on shell, font, theme, and keybinding setup. ### Agent and AI settings -Cursor's Composer and Agent features don't have a one-to-one migration path - they map to different Warp concepts. +Cursor's Composer and Agent features don't have a one-to-one migration path; they map to different Warp concepts. -* **Composer / Agent** in Cursor maps to Warp's [Agent Mode](/agent-platform/local-agents/overview/). Start an agent conversation in any tab. -* **Rules files** (`.cursorrules`) - Warp uses [Rules](/agent-platform/capabilities/rules/) stored in Warp Drive or committed to your repo as `AGENTS.md` (or `WARP.md`). Run `/init` in Agent Mode to generate an `AGENTS.md`, or copy your `.cursorrules` content directly. +* **Composer / Agent** - In Cursor, these features map to Warp's [Agent Mode](/agent-platform/local-agents/overview/). Start an Agent conversation in any tab. +* **Rules files** - Warp uses [Rules](/agent-platform/capabilities/rules/) stored in Warp Drive or committed to your repo as `AGENTS.md` (or `WARP.md`). Run `/init` in Agent Mode to generate an `AGENTS.md`, or copy your `.cursorrules` content directly. * **MCP servers** - Warp supports MCP natively. See [MCP](/agent-platform/capabilities/mcp/) for configuration. ### Model choice -Cursor lets you pick a model per conversation. Warp does the same - use the model selector in any agent conversation. See [model choice](/agent-platform/capabilities/model-choice/). +Cursor lets you pick a model per conversation. Warp does the same; use the model selector in any Agent conversation. See [model choice](/agent-platform/capabilities/model-choice/). ### Keybindings @@ -63,11 +63,11 @@ Warp's built-in [code editor](/code/code-editor/) supports Language Server Proto ## Warp-native equivalents -Cursor features and their Warp counterparts: +Use this table to find Warp equivalents for Cursor features you might look for after switching: | From Cursor | In Warp | | --- | --- | -| Composer / Agent panel | [Agent Mode](/agent-platform/local-agents/overview/) in any tab (toggle with `⌘+I`) | +| Composer / Agent panel | [Agent Mode](/agent-platform/local-agents/overview/) in any tab (toggle with `⌘+I` on macOS or `Ctrl+I` on Linux/Windows) | | Agent tabs | Multiple [agents in parallel](/agent-platform/local-agents/overview/) across tabs | | `.cursorrules` | `AGENTS.md` / `WARP.md` at the project root, picked up as a [Rule](/agent-platform/capabilities/rules/) | | MCP servers | [MCP](/agent-platform/capabilities/mcp/) | diff --git a/src/content/docs/getting-started/migrate-to-warp/migrate-to-warp-from-ghostty.mdx b/src/content/docs/getting-started/migrate-to-warp/migrate-to-warp-from-ghostty.mdx index 634479d5..35b7c5ff 100644 --- a/src/content/docs/getting-started/migrate-to-warp/migrate-to-warp-from-ghostty.mdx +++ b/src/content/docs/getting-started/migrate-to-warp/migrate-to-warp-from-ghostty.mdx @@ -6,22 +6,22 @@ description: >- features. --- -Warp gives Ghostty users a fast path to bring over themes, fonts, and keybindings — plus native equivalents for the Ghostty features you rely on, from the quick terminal to native tabs and splits. +Warp gives Ghostty users a fast path to bring over themes, fonts, and keybindings, plus native equivalents for the Ghostty features you rely on, from the quick terminal to native tabs and splits. -## What transfers automatically +## What Warp can help transfer -Warp doesn't ship a Ghostty importer, but it can do most of the work for you agentically. Ghostty stores its configuration in a plain-text key-value file at `~/.config/ghostty/config`. +Warp doesn't have a one-click Ghostty importer. Because Ghostty stores its configuration in a plain-text key-value file at `~/.config/ghostty/config`, Warp's Agent can read that file and translate matching values into Warp's `settings.toml`. -## Use Warp's agent to migrate your settings (recommended) +## Use Warp's Agent to migrate your settings (recommended) -The fastest way to bring over your Ghostty setup is to ask Warp's agent to translate your config directly. Warp ships a [`settings.toml` file](/terminal/settings/) and a bundled `modify-settings` skill that lets the agent read your existing config and write equivalent values into Warp's settings, including translating your Ghostty theme into a Warp [custom theme](/terminal/appearance/custom-themes/). +The fastest way to bring over your Ghostty setup is to ask Warp's Agent to translate your config directly. Warp ships a [`settings.toml` file](/terminal/settings/) and a bundled `modify-settings` skill that lets the Agent read your existing config and write equivalent values into Warp's settings, including translating your Ghostty theme into a Warp [custom theme](/terminal/appearance/custom-themes/). -1. In Warp, open a new tab and switch to [Agent Mode](/agent-platform/local-agents/overview/) with `⌘+I` (macOS) or `Ctrl+I` (Linux/Windows). -2. Paste a prompt like: +1. In the Warp app, open a new tab and switch to [Agent Mode](/agent-platform/local-agents/overview/) with `⌘+I` (macOS) or `Ctrl+I` (Linux/Windows). +2. Paste this prompt into Agent Mode, then press `Enter`. > Read my Ghostty config at `~/.config/ghostty/config` and any referenced theme files in `~/.config/ghostty/themes/`. Port the equivalent settings (theme, font, keybindings, shell) into my Warp `settings.toml` using the `modify-settings` skill, and create a matching custom theme. Show me a diff before applying. -3. Review the proposed diff and approve. Warp hot-reloads `settings.toml`, so changes take effect immediately. +3. Review the proposed diff, then approve the changes. Warp hot-reloads `settings.toml`, so changes take effect immediately. If you'd rather configure each setting manually through the Settings UI, the steps below cover the most common cases. @@ -29,38 +29,38 @@ If you'd rather configure each setting manually through the Settings UI, the ste ### Theme and colors -1. Open **Settings** > **Appearance** > **Themes** in Warp. -2. Pick a built-in theme that matches your Ghostty setup, or [create a custom theme](/terminal/appearance/custom-themes/) by translating your Ghostty colors into a YAML theme file. -3. Ghostty's theme files live in `~/.config/ghostty/themes/`. Open the file named in your Ghostty `theme` setting to copy the foreground, background, and 16 ANSI color values. +1. In the Warp app, open **Settings** > **Appearance** > **Themes**. +2. Choose a built-in theme that matches your Ghostty setup, or [create a custom theme](/terminal/appearance/custom-themes/) by translating your Ghostty colors into a YAML theme file. +3. If your Ghostty config references a custom theme, open the matching file in `~/.config/ghostty/themes/` and copy the foreground, background, and 16 ANSI color values. ### Font and text -1. In **Settings** > **Appearance** > **Text, fonts, & cursor**, match your Ghostty `font-family` and `font-size` values. -2. If you use font ligatures, ensure **Ligatures** is enabled. +1. In the Warp app, open **Settings** > **Appearance** > **Text, fonts, & cursor** and match your Ghostty `font-family` and `font-size` values. +2. If you use font ligatures, toggle **Ligatures** on. ### Keybindings -Warp's [default keyboard shortcuts](/getting-started/keyboard-shortcuts/) cover most Ghostty bindings. For custom bindings from your Ghostty `keybind` lines, open **Settings** > **Keyboard shortcuts** and add them manually. +Warp's [default keyboard shortcuts](/getting-started/keyboard-shortcuts/) cover most Ghostty bindings. For custom bindings from your Ghostty `keybind` lines, open **Settings** > **Keyboard shortcuts** in the Warp app and add them manually. ### Shell and prompt -Warp detects your login shell automatically. To override it, go to **Settings** > **Features** > **Session** and pick a shell from **Startup shell for new sessions**. +Warp detects your login shell automatically. To override it, open **Settings** > **Features** > **Session** in the Warp app and choose a shell from **Startup shell for new sessions**. For prompts, choose between Warp's [native prompt](/terminal/appearance/prompt/#warp-prompt) (drag-and-drop context chips) or the [shell prompt (PS1)](/terminal/appearance/prompt/#custom-prompt) if you want to keep your existing prompt configuration. ### Quick terminal (Quake mode) -Configure Warp's equivalent via **Settings** > **Features** > **Window** > **Global hotkey**. See [global hotkey](/terminal/windows/global-hotkey/) for the full configuration. +In the Warp app, configure Warp's equivalent from **Settings** > **Features** > **Window** > **Global hotkey**. See [global hotkey](/terminal/windows/global-hotkey/) for the full configuration. ## Warp-native equivalents -Features Ghostty users commonly miss, and where they live in Warp: +Use this table to find the closest Warp equivalent for Ghostty features you might look for after switching: | From Ghostty | In Warp | | --- | --- | | Quick terminal / dropdown window | [Global hotkey](/terminal/windows/global-hotkey/) | | Native tabs and splits | [Tabs](/terminal/windows/tabs/), [vertical tabs](/terminal/windows/vertical-tabs/), [split panes](/terminal/windows/split-panes/) | -| Command palette | [Command Palette](/terminal/command-palette/) (`⌘+P` on macOS, `Ctrl+Shift+P` on Linux) | +| Command palette | [Command Palette](/terminal/command-palette/) (`⌘+P` on macOS, `Ctrl+Shift+P` on Linux/Windows) | | GPU-accelerated rendering | GPU-rendered natively on all supported platforms | | Kitty graphics protocol | Image rendering for most common workflows (see [more features](/terminal/more-features/)) | | Shaders and custom visual effects | Not supported; closest: [size, opacity, and blurring](/terminal/appearance/size-opacity-blurring/) + [pane dimming](/terminal/appearance/pane-dimming/) | diff --git a/src/content/docs/getting-started/migrate-to-warp/migrate-to-warp-from-iterm2.mdx b/src/content/docs/getting-started/migrate-to-warp/migrate-to-warp-from-iterm2.mdx index 5a8aa7f8..c2feec88 100644 --- a/src/content/docs/getting-started/migrate-to-warp/migrate-to-warp-from-iterm2.mdx +++ b/src/content/docs/getting-started/migrate-to-warp/migrate-to-warp-from-iterm2.mdx @@ -32,16 +32,16 @@ To run the importer:
Select a settings profile to import.
-## Use Warp's agent for follow-up settings +## Use Warp's Agent for follow-up settings -If the importer doesn't pick up something you care about — a non-default profile, an unusual keybinding, a specific setting — ask Warp's agent to translate it directly. Warp ships a [`settings.toml` file](/terminal/settings/) and a bundled `modify-settings` skill that lets the agent read your iTerm2 plist and write equivalent values into Warp's settings. +If the importer doesn't pick up something you care about, such as a non-default profile, an unusual keybinding, or a specific setting, ask Warp's Agent to translate it directly. Warp ships a [`settings.toml` file](/terminal/settings/) and a bundled `modify-settings` skill that lets the Agent read your iTerm2 plist and write equivalent values into Warp's settings. -1. In Warp, switch to [Agent Mode](/agent-platform/local-agents/overview/) with `⌘+I`. -2. Paste a prompt like: +1. In the Warp app, switch to [Agent Mode](/agent-platform/local-agents/overview/) with `⌘+I`. +2. Paste this prompt into Agent Mode, then press `Enter`. > Read my iTerm2 preferences with `defaults read com.googlecode.iterm2` and port any settings that the importer didn't cover (extra profiles, custom keybindings) into my Warp `settings.toml` using the `modify-settings` skill. Show me a diff before applying. -3. Review the proposed diff and approve. Warp hot-reloads `settings.toml`. +3. Review the proposed diff, then approve the changes. Warp hot-reloads `settings.toml`. ## What to reconfigure manually @@ -61,7 +61,7 @@ After the import, choose which [prompt](/terminal/appearance/prompt/) to use: ## Warp-native equivalents -Features switchers commonly look for after leaving iTerm2, and where they live in Warp: +Use this table to find Warp equivalents for iTerm2 features you might look for after switching: | From iTerm2 | In Warp | | --- | --- | diff --git a/src/content/docs/getting-started/migrate-to-warp/migrate-to-warp-from-macos-terminal.mdx b/src/content/docs/getting-started/migrate-to-warp/migrate-to-warp-from-macos-terminal.mdx index 16895615..e40d5e47 100644 --- a/src/content/docs/getting-started/migrate-to-warp/migrate-to-warp-from-macos-terminal.mdx +++ b/src/content/docs/getting-started/migrate-to-warp/migrate-to-warp-from-macos-terminal.mdx @@ -5,22 +5,22 @@ description: >- discover what Warp adds beyond the basics. --- -Warp gives Terminal.app users everything they already have — shell, theme, font, prompt — plus split panes, tabs, blocks, and Agent Mode for an AI-assisted workflow. This page walks through both an agent-driven migration and the manual GUI steps. +Warp gives Terminal.app users everything they already have, including shell, theme, font, and prompt settings, plus split panes, tabs, blocks, and Agent Mode for an AI-assisted workflow. This page walks through both an Agent-driven migration and the manual GUI steps. -## What transfers automatically +## What Warp can help transfer -Warp doesn't ship a Terminal.app importer, but it can do most of the work for you agentically. Most Terminal.app users run near-default settings, so the migration usually takes only a few minutes either way. +Warp doesn't have a one-click Terminal.app importer. Because Terminal.app stores profile data in macOS preferences, Warp's Agent can read those preferences with `defaults read com.apple.Terminal` and translate matching theme, font, and window settings into Warp's `settings.toml`. Most Terminal.app users run near-default settings, so the migration usually takes only a few minutes either way. -## Use Warp's agent to migrate your settings (recommended) +## Use Warp's Agent to migrate your settings (recommended) -The fastest way to bring over a Terminal.app theme is to ask Warp's agent to translate it directly. Warp ships a [`settings.toml` file](/terminal/settings/) and a bundled `modify-settings` skill that lets the agent read your Terminal.app preferences and write equivalent values into Warp's settings, including creating a matching [custom theme](/terminal/appearance/custom-themes/). +The fastest way to bring over a Terminal.app theme is to ask Warp's Agent to translate it directly. Warp ships a [`settings.toml` file](/terminal/settings/) and a bundled `modify-settings` skill that lets the Agent read your Terminal.app preferences and write equivalent values into Warp's settings, including creating a matching [custom theme](/terminal/appearance/custom-themes/). -1. In Warp, open a new tab and switch to [Agent Mode](/agent-platform/local-agents/overview/) with `⌘+I`. -2. Paste a prompt like: +1. In the Warp app, open a new tab and switch to [Agent Mode](/agent-platform/local-agents/overview/) with `⌘+I`. +2. Paste this prompt into Agent Mode, then press `Enter`. > Read my Terminal.app preferences with `defaults read com.apple.Terminal` and port the active profile (theme, font, window size) into my Warp `settings.toml` using the `modify-settings` skill. Create a matching custom theme. Show me a diff before applying. -3. Review the proposed diff and approve. Warp hot-reloads `settings.toml`. +3. Review the proposed diff, then approve the changes. Warp hot-reloads `settings.toml`. If you'd rather configure each setting manually through the Settings UI, the steps below cover the most common cases. @@ -30,23 +30,23 @@ If you'd rather configure each setting manually through the Settings UI, the ste Warp auto-detects your login shell on first launch. macOS has shipped with `zsh` as the default since Catalina (2019); if you changed your shell with `chsh`, Warp picks that up too. -To change it later, go to **Settings** > **Features** > **Session** and pick a shell from **Startup shell for new sessions**. +To change it later, open **Settings** > **Features** > **Session** in the Warp app and choose a shell from **Startup shell for new sessions**. ### Theme and colors Terminal.app ships with a handful of profiles (Basic, Pro, Homebrew, Ocean, etc.). Match them in Warp: -1. Open **Settings** > **Appearance** > **Themes**. -2. Pick a preset theme. Warp's built-in library includes many themes similar to Terminal.app's defaults. -3. For exact color matches, [create a custom theme](/terminal/appearance/custom-themes/) using the ANSI color values you can inspect in Terminal.app's **Settings** > **Profiles** > **Text** tab. +1. In the Warp app, open **Settings** > **Appearance** > **Themes**. +2. Choose a preset theme. Warp's built-in library includes many themes similar to Terminal.app's defaults. +3. For exact color matches, [create a custom theme](/terminal/appearance/custom-themes/) using ANSI color values from Terminal.app. In Terminal.app, open **Settings**, select **Profiles**, and click **Text** to inspect those values. ### Font -1. In **Settings** > **Appearance** > **Text, fonts, & cursor**, pick your font family and size to match what you use in Terminal.app. +1. In the Warp app, open **Settings** > **Appearance** > **Text, fonts, & cursor**, then choose your font family and size to match what you use in Terminal.app. ### Window size and transparency -Configure in **Settings** > **Appearance** > **Size, opacity, & blurring**. See [size, opacity, and blurring](/terminal/appearance/size-opacity-blurring/). +Configure window appearance in the Warp app from **Settings** > **Appearance** > **Size, opacity, & blurring**. See [size, opacity, and blurring](/terminal/appearance/size-opacity-blurring/). ### Prompt @@ -55,7 +55,7 @@ Terminal.app uses whatever prompt your shell's PS1 (or zsh's PROMPT) defines. In 1. [**Warp prompt**](/terminal/appearance/prompt/#warp-prompt) - Warp's native prompt with drag-and-drop chips for git branch, directory, and more. 2. [**Shell prompt (PS1)**](/terminal/appearance/prompt/#custom-prompt) - keeps your existing shell prompt exactly as it appears in Terminal.app. -Configure in **Settings** > **Appearance** > **Prompt**. +Configure either prompt in the Warp app from **Settings** > **Appearance** > **Prompt**. ## Warp-native equivalents diff --git a/src/content/docs/getting-started/migrate-to-warp/migrate-to-warp-from-vs-code-terminal.mdx b/src/content/docs/getting-started/migrate-to-warp/migrate-to-warp-from-vs-code-terminal.mdx index 01d1d5ac..4bb00af1 100644 --- a/src/content/docs/getting-started/migrate-to-warp/migrate-to-warp-from-vs-code-terminal.mdx +++ b/src/content/docs/getting-started/migrate-to-warp/migrate-to-warp-from-vs-code-terminal.mdx @@ -7,28 +7,34 @@ description: >- Warp lets VS Code users choose their own path: keep VS Code for editing and run Warp as the terminal alongside it, or replace both with Warp's built-in code editor. This page walks through reconfiguring your terminal settings for either path. -## What transfers automatically +## What Warp can help transfer -Warp doesn't ship a VS Code importer — it's a standalone application, not a VS Code extension — but it can do most of the work for you agentically. Your VS Code terminal settings live in your user `settings.json` under keys like: +Warp doesn't have a VS Code importer because it's a standalone application, not a VS Code extension. Because your VS Code terminal settings live in a readable user `settings.json`, Warp's Agent can translate matching `terminal.integrated.*` values into Warp's `settings.toml`: ```json -"terminal.integrated.defaultProfile.osx": "zsh", -"terminal.integrated.fontFamily": "MesloLGS NF", -"terminal.integrated.fontSize": 14, -"terminal.integrated.cursorStyle": "line", -"terminal.integrated.profiles.osx": { ... } +{ + "terminal.integrated.defaultProfile.osx": "zsh", + "terminal.integrated.fontFamily": "MesloLGS NF", + "terminal.integrated.fontSize": 14, + "terminal.integrated.cursorStyle": "line", + "terminal.integrated.profiles.osx": { + "zsh": { + "path": "zsh" + } + } +} ``` -## Use Warp's agent to migrate your settings (recommended) +## Use Warp's Agent to migrate your settings (recommended) -The fastest way to bring over your VS Code terminal setup is to ask Warp's agent to translate `settings.json` directly. Warp ships a [`settings.toml` file](/terminal/settings/) and a bundled `modify-settings` skill that lets the agent read your existing config and write equivalent values into Warp's settings. +The fastest way to bring over your VS Code terminal setup is to ask Warp's Agent to translate `settings.json` directly. Warp ships a [`settings.toml` file](/terminal/settings/) and a bundled `modify-settings` skill that lets the Agent read your existing config and write equivalent values into Warp's settings. -1. In Warp, open a new tab and switch to [Agent Mode](/agent-platform/local-agents/overview/) with `⌘+I` (macOS) or `Ctrl+I` (Linux/Windows). -2. Paste a prompt like: +1. In the Warp app, open a new tab and switch to [Agent Mode](/agent-platform/local-agents/overview/) with `⌘+I` (macOS) or `Ctrl+I` (Linux/Windows). +2. Paste this prompt into Agent Mode, then press `Enter`. > Read my VS Code `settings.json` (`~/Library/Application Support/Code/User/settings.json` on macOS) and port the equivalent terminal settings (`terminal.integrated.*` keys) into my Warp `settings.toml` using the `modify-settings` skill. Show me a diff before applying. -3. Review the proposed diff and approve. Warp hot-reloads `settings.toml`. +3. Review the proposed diff, then approve the changes. Warp hot-reloads `settings.toml`. If you'd rather configure each setting manually through the Settings UI, the steps below cover the most common cases. @@ -36,25 +42,25 @@ If you'd rather configure each setting manually through the Settings UI, the ste ### Shell -Warp auto-detects your login shell. To override - for example, to match `terminal.integrated.defaultProfile.*` - go to **Settings** > **Features** > **Session** and pick a shell from **Startup shell for new sessions**. +Warp auto-detects your login shell. To override it, for example, to match `terminal.integrated.defaultProfile.*`, open **Settings** > **Features** > **Session** in the Warp app and choose a shell from **Startup shell for new sessions**. ### Font and cursor -In Warp's **Settings** > **Appearance** > **Text, fonts, & cursor**, set the font family and size to match `terminal.integrated.fontFamily` and `terminal.integrated.fontSize`. +In the Warp app, open **Settings** > **Appearance** > **Text, fonts, & cursor**, then set the font family and size to match `terminal.integrated.fontFamily` and `terminal.integrated.fontSize`. ### Theme -VS Code's terminal uses the color scheme from your overall editor theme. In Warp, pick a comparable theme from **Settings** > **Appearance** > **Themes**, or [create a custom theme](/terminal/appearance/custom-themes/) that matches your VS Code theme's `terminal.*` color tokens. +VS Code's terminal uses the color scheme from your overall editor theme. In the Warp app, choose a comparable theme from **Settings** > **Appearance** > **Themes**, or [create a custom theme](/terminal/appearance/custom-themes/) that matches your VS Code theme's `terminal.*` color tokens. ### Keybindings -Warp's [default keyboard shortcuts](/getting-started/keyboard-shortcuts/) are largely consistent with VS Code terminal shortcuts (splits, new tab, find). For any custom bindings you configured in VS Code, add them in Warp's **Settings** > **Keyboard shortcuts**. +Warp's [default keyboard shortcuts](/getting-started/keyboard-shortcuts/) are largely consistent with VS Code terminal shortcuts (splits, new tab, find). For any custom bindings you configured in VS Code, add them in **Settings** > **Keyboard shortcuts** in the Warp app. ## Choosing your setup ### Use Warp alongside VS Code -Many developers keep VS Code as their editor and use Warp as the terminal they switch to for long-running commands, SSH sessions, or AI-assisted workflows. No changes to VS Code needed - just install Warp and open it when you want a richer terminal. +Many developers keep VS Code as their editor and use Warp as the terminal they switch to for long-running commands, SSH sessions, or AI-assisted workflows. You don't need to change VS Code. Install Warp and open it when you want a richer terminal. VS Code's integrated terminal still works; use it for quick one-off commands, and jump to Warp when you need [blocks](/terminal/blocks/), [Agent Mode](/agent-platform/local-agents/overview/), or [persistent sessions](/terminal/sessions/session-restoration/). @@ -66,7 +72,7 @@ Open a directory with `warp .` from the command line to start editing. ## Warp-native equivalents -VS Code terminal features and their Warp equivalents: +Use this table to find Warp equivalents for VS Code terminal features you might look for after switching: | From VS Code terminal | In Warp | | --- | --- | diff --git a/src/content/docs/getting-started/migrate-to-warp/migrate-to-warp-from-windows-terminal.mdx b/src/content/docs/getting-started/migrate-to-warp/migrate-to-warp-from-windows-terminal.mdx index b5698cad..c158be5f 100644 --- a/src/content/docs/getting-started/migrate-to-warp/migrate-to-warp-from-windows-terminal.mdx +++ b/src/content/docs/getting-started/migrate-to-warp/migrate-to-warp-from-windows-terminal.mdx @@ -5,26 +5,26 @@ description: >- shells, fonts, keybindings, and find Warp equivalents. --- -Warp on Windows covers everything you use Windows Terminal for today — profiles, PowerShell, color schemes, keybindings — with Agent Mode and blocks on top. This page walks through the migration. +Warp on Windows covers everything you use Windows Terminal for today, including profiles, PowerShell, color schemes, and keybindings, with Agent Mode and blocks on top. This page walks through the migration. -## What transfers automatically +## What Warp can help transfer -Warp doesn't ship a Windows Terminal importer, but it can do most of the work for you agentically. Windows Terminal stores its settings in a single JSON file at: +Warp doesn't have a one-click Windows Terminal importer. Because Windows Terminal stores profiles, color schemes, and keybindings in a single JSON file, Warp's Agent can read that file and translate matching values into Warp's `settings.toml`: ```powershell %LOCALAPPDATA%\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState\settings.json ``` -## Use Warp's agent to migrate your settings (recommended) +## Use Warp's Agent to migrate your settings (recommended) -The fastest way to bring over your Windows Terminal setup is to ask Warp's agent to translate `settings.json` directly. Warp ships a [`settings.toml` file](/terminal/settings/) and a bundled `modify-settings` skill that lets the agent read your existing config and write equivalent values into Warp's settings, including translating your color schemes into a Warp [custom theme](/terminal/appearance/custom-themes/). +The fastest way to bring over your Windows Terminal setup is to ask Warp's Agent to translate `settings.json` directly. Warp ships a [`settings.toml` file](/terminal/settings/) and a bundled `modify-settings` skill that lets the Agent read your existing config and write equivalent values into Warp's settings, including translating your color schemes into a Warp [custom theme](/terminal/appearance/custom-themes/). -1. In Warp, open a new tab and switch to [Agent Mode](/agent-platform/local-agents/overview/) with `Ctrl+I`. -2. Paste a prompt like: +1. In the Warp app, open a new tab and switch to [Agent Mode](/agent-platform/local-agents/overview/) with `Ctrl+I`. +2. Paste this prompt into Agent Mode, then press `Enter`. > Read my Windows Terminal `settings.json` at `%LOCALAPPDATA%\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState\settings.json` and port the active profile and color scheme into my Warp `settings.toml` using the `modify-settings` skill. Create a matching custom theme. Show me a diff before applying. -3. Review the proposed diff and approve. Warp hot-reloads `settings.toml`. +3. Review the proposed diff, then approve the changes. Warp hot-reloads `settings.toml`. If you'd rather configure each setting manually through the Settings UI, the steps below cover the most common cases. @@ -32,7 +32,7 @@ If you'd rather configure each setting manually through the Settings UI, the ste ### Default shell -Warp on Windows supports PowerShell (`pwsh` and `powershell.exe`), Command Prompt (`cmd`), bash, zsh, and fish. Warp auto-detects your login shell; to override, go to **Settings** > **Features** > **Session** and pick a shell from **Startup shell for new sessions**. +Warp on Windows supports PowerShell (`pwsh` and `powershell.exe`), Command Prompt (`cmd`), bash, zsh, and fish. Warp auto-detects your login shell. To override it, open **Settings** > **Features** > **Session** in the Warp app and choose a shell from **Startup shell for new sessions**. If you use PowerShell modules or a custom `$PROFILE`, Warp loads them the same way Windows Terminal does. @@ -40,10 +40,10 @@ If you use PowerShell modules or a custom `$PROFILE`, Warp loads them the same w Windows Terminal uses profiles to group shell, theme, starting directory, and font together. Warp doesn't have a single profile concept; instead, match each dimension separately: -* **Shell** - **Settings** > **Features** > **Session**. -* **Starting directory** - **Settings** > **Features** > **Session** > Working directory. -* **Font family, size** - **Settings** > **Appearance** > **Text, fonts, & cursor**. -* **Color scheme** - **Settings** > **Appearance** > **Themes**. Translate your Windows Terminal color scheme into a [custom Warp theme](/terminal/appearance/custom-themes/) using the same 16 ANSI color values. +* **Shell** - Configure from **Settings** > **Features** > **Session** in the Warp app. +* **Starting directory** - Configure **Working directory** from **Settings** > **Features** > **Session** in the Warp app. +* **Font family and size** - Configure from **Settings** > **Appearance** > **Text, fonts, & cursor** in the Warp app. +* **Color scheme** - Configure from **Settings** > **Appearance** > **Themes** in the Warp app. Translate your Windows Terminal color scheme into a [custom Warp theme](/terminal/appearance/custom-themes/) using the same 16 ANSI color values. * **Reusable layouts** - create a [tab config](/terminal/windows/tab-configs/) for each workflow that used to be a profile. ### Color scheme @@ -51,19 +51,19 @@ Windows Terminal uses profiles to group shell, theme, starting directory, and fo Windows Terminal's `schemes` array defines foreground, background, cursor, and ANSI colors. To match an existing scheme: 1. Copy the color values from the scheme you use in your `settings.json`. -2. Open **Settings** > **Appearance** > **Themes** in Warp and either pick a preset that matches or [create a custom theme](/terminal/appearance/custom-themes/). +2. In the Warp app, open **Settings** > **Appearance** > **Themes**, then choose a preset that matches or [create a custom theme](/terminal/appearance/custom-themes/). ### Keybindings -Warp's [default keyboard shortcuts](/getting-started/keyboard-shortcuts/) cover most Windows Terminal bindings. For custom bindings from `settings.json`'s `actions` array, add them in **Settings** > **Keyboard shortcuts**. +Warp's [default keyboard shortcuts](/getting-started/keyboard-shortcuts/) cover most Windows Terminal bindings. For custom bindings from `settings.json`'s `actions` array, add them in **Settings** > **Keyboard shortcuts** in the Warp app. ### Prompt -If you use `oh-my-posh` or a custom PowerShell prompt, it continues to work in Warp. To choose between Warp's native prompt and your existing shell prompt, go to **Settings** > **Appearance** > **Prompt**. See [prompt](/terminal/appearance/prompt/). +If you use `oh-my-posh` or a custom PowerShell prompt, it continues to work in Warp. To choose between Warp's native prompt and your existing shell prompt, open **Settings** > **Appearance** > **Prompt** in the Warp app. See [prompt](/terminal/appearance/prompt/). ## Warp-native equivalents -Features Windows Terminal users commonly look for in Warp: +Use this table to find Warp equivalents for Windows Terminal features you might look for after switching: | From Windows Terminal | In Warp | | --- | --- |