warpdotdev · hongyi-chen · Aug 3, 2026 · Aug 3, 2026 · Aug 3, 2026 · Aug 3, 2026
diff --git a/src/content/docs/agent-platform/capabilities/agent-profiles-permissions.mdx b/src/content/docs/agent-platform/capabilities/agent-profiles-permissions.mdx
@@ -39,7 +39,7 @@ Agent Permissions let you define how your Agent in a specific Profile operates
 **Still getting approval prompts?** If the Agent keeps asking for permission to run certain commands (like `curl`, `rm`, or `wget`) even though you've set permissions to "Always allow," check your **Command denylist** in **Settings** > **Agents** > **Profiles**. The denylist takes precedence over your other permission settings. Remove commands from the denylist to allow them to auto-execute, or use [Run until completion](#run-until-completion) to bypass the denylist for the current task.
 :::
 
-You can control how much autonomy the Agent has when performing different types of actions under **Settings** > **Agents** > **Profiles** > **Permissions** . Agent permission types:
+You can control how much autonomy the Agent has when performing different types of actions under **Settings** > **Agents** > **Profiles** > **Permissions**. Agent permission types:
 
 * Apply code diffs
 * Read files
@@ -121,17 +121,17 @@ To learn how to build and configure your own MCP server, check out the [MCP feat
 
 ## Run until completion
 
-During an Agent interaction, you can give the Agent full autonomy for the current task. When auto-approve is on, every suggested command runs immediately until the task finishes, or you stop it with `Ctrl + C`.
+During an Agent interaction, you can give the Agent full autonomy for the current task. When auto-approve is on, every suggested command runs immediately until the task finishes, or you stop it with `Ctrl+C`.
 
 <Tabs>
   <TabItem label="macOS">
-    Auto-approve all Agent actions with: `CMD + SHIFT + I`
+    Auto-approve all Agent actions with: `Cmd+Shift+I`
   </TabItem>
   <TabItem label="Windows">
-    Auto-approve all Agent actions with: `CTRL + SHIFT + I`
+    Auto-approve all Agent actions with: `Ctrl+Shift+I`
   </TabItem>
   <TabItem label="Linux">
-    Auto-approve all Agent actions with: `CTRL + SHIFT + I`
+    Auto-approve all Agent actions with: `Ctrl+Shift+I`
   </TabItem>
 </Tabs>
 

diff --git a/src/content/docs/agent-platform/capabilities/codebase-context.mdx b/src/content/docs/agent-platform/capabilities/codebase-context.mdx
@@ -32,18 +32,18 @@ git clone https://github.com/vercel/next.js.git && cd next.js
 
 ## Indexing your codebase
 
-When you open a directory in Warp, we check if it is part of a Git repository. If it is, Warp begins indexing the source code to provide rich context for Agents. Warp also detects [Git worktree](/code/git-worktrees/) checkouts — each worktree is indexed as its own repository, so Agents always have accurate context for the branch you're working on.
+When you open a directory in Warp, Warp checks whether it's part of a Git repository. If it is, Warp begins indexing the source code to provide rich context for Agents. Warp also detects [Git worktree](/code/git-worktrees/) checkouts — each worktree is indexed as its own repository, so Agents always have accurate context for the branch you're working on.
 
 :::note
-Code indexed with Codebase Context is never stored on our servers. Codebase Context works with both local agent sessions and [cloud agent runs](/platform/). Without Codebase Context enabled, agents will still be able use terminal commands (i.e. `grep`, `sed`) to navigate your code.
+Code indexed with Codebase Context is never stored on our servers. Codebase Context works with both local agent sessions and [cloud agent runs](/platform/). Without Codebase Context enabled, agents will still be able to use terminal commands (i.e. `grep`, `sed`) to navigate your code.
 :::
 
 :::note
 Codebase Context works in SSH sessions when [Warp's SSH extension](/terminal/warpify/ssh/) is installed on the remote host — the remote repository is indexed directly on the remote machine. WSL sessions are not yet supported ([GitHub #6744](https://github.com/warpdotdev/Warp/issues/6744)).
 :::
 
 <figure>
-![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)
+![Codebase indexing settings in Warp, showing sync status and which folders are indexed for AI-powered context and suggestions.](../../../../assets/agent-platform/codebase-context-main.png)
 <figcaption>Codebase indexing settings.</figcaption>
 </figure>
 
@@ -78,7 +78,7 @@ When viewing indexed codebases in Warp under **Settings** > **Code** > **Indexin
 * **Codebase too large** – The number of files in the codebase exceeds your current plan’s limit. You can either reduce the number of files being indexed using `.warpindexingignore`, or [contact sales](https://www.warp.dev/contact-sales) for support with larger codebases.
 
 <figure>
-![View and manage the indexing status of your codebases in Warp. Easily see which projects are synced, in progress, or require attention.](../../../../assets/agent-platform/codebase-context-statuses.png)
+![View and manage the indexing status of your codebases in Warp, showing which projects are synced, in progress, or require attention.](../../../../assets/agent-platform/codebase-context-statuses.png)
 <figcaption>Codebase indexing status overview.</figcaption>
 </figure>
 

diff --git a/src/content/docs/agent-platform/capabilities/full-terminal-use.mdx b/src/content/docs/agent-platform/capabilities/full-terminal-use.mdx
@@ -111,22 +111,22 @@ The behavior differs based on where you start the long-running command:
 <Tabs>
   <TabItem label="From terminal view">
     1. Run an interactive command (e.g., `python`, `psql`)
-    2. Press `⌘↩` (macOS) or `Ctrl+Shift+Enter` (Windows/Linux), or use `⌘I` (macOS) / `Ctrl+I` (Windows/Linux), to tag in the agent
+    2. Press `⌘+↩` (macOS) or `Ctrl+Shift+Enter` (Windows/Linux), or use `⌘+I` (macOS) / `Ctrl+I` (Windows/Linux), to tag in the agent
     3. The input switches to Agent Mode with full controls
     4. When you exit, an agent conversation block appears in your terminal block list
     5. Click the block to reopen the full conversation with your LRC interaction context
   </TabItem>
   <TabItem label="From agent view">
     1. The agent runs an interactive command as part of your conversation
-    2. Use `⌘↩` (macOS) or `Ctrl+Shift+Enter` (Windows/Linux) to tag in if the agent isn't already interacting
+    2. Use `⌘+↩` (macOS) or `Ctrl+Shift+Enter` (Windows/Linux) to tag in if the agent isn't already interacting
     3. The UI stays the same since you're already in agent view
     4. When you exit, the interaction remains part of your conversation. No separate block is created in the terminal block list
     5. Commands run in agent view are automatically included as context
   </TabItem>
 </Tabs>
 
 :::note
-You can also use `CMD + I` (macOS) or `CTRL + I` (Windows/Linux) to toggle agent control in either view.
+You can also use `Cmd+I` (macOS) or `Ctrl+I` (Windows/Linux) to toggle agent control in either view.
 :::
 
 #### Showing and hiding agent responses
@@ -135,7 +135,7 @@ Warp gives you control over how much agent output appears in Full Terminal Use.
 
 **Toggle visibility**
 
-Use the `Hide responses` or `Show responses` button or `CMD + G` in the interactive command footer to switch between showing all agent output or hiding it from the terminal view.
+Use the `Hide responses` or `Show responses` button or `Cmd+G` in the interactive command footer to switch between showing all agent output or hiding it from the terminal view.
 
 Note that this only affects the agent's messages and proposals; your terminal state and command output remain unchanged.
 
@@ -156,10 +156,10 @@ You control how much autonomy the agent has when interacting with the terminal.
 
 Each time the agent wants to take an action inside an interactive shell, you’ll see the agent’s reasoning, a brief explanation, and the proposed command. From there you can:
 
-* Allow the command once (for example by approving it or pressing `ENTER`).
-* Turn on auto-approval for similar commands in this session (for example with `CMD + SHIFT + I`).
-* Refine the request with `CTRL + C`, which clears the proposed action and lets you follow up with a different query.
-* Take over manually with `CMD + I`, which stops the agent from issuing any further PTY writes until you hand control back.
+* Allow the command once (for example by approving it or pressing `Enter`).
+* Turn on auto-approval for similar commands in this session (for example with `Cmd+Shift+I`).
+* Refine the request with `Ctrl+C`, which clears the proposed action and lets you follow up with a different query.
+* Take over manually with `Cmd+I`, which stops the agent from issuing any further PTY writes until you hand control back.
 
 <figure>
 ![Allow, Refine, or Take over an agent response.](../../../../assets/agent-platform/allow-refine-takeover.png)

diff --git a/src/content/docs/agent-platform/capabilities/mcp.mdx b/src/content/docs/agent-platform/capabilities/mcp.mdx
@@ -211,7 +211,7 @@ Tip: We've noticed that some models often work better with MCP servers than othe
 In some cases you may need to reset the auth token for some MCP servers. To do this, delete the local MCP auth files by running the following: `rm -rf ~/.mcp-auth`
 
 :::caution
-Note this will delete all your MCP auth tokens stored locally so you will need to login and re-authenticate.
+Note this will delete all your MCP auth tokens stored locally so you will need to log in and re-authenticate.
 :::
 
 If the above doesn't help and you need to reset or change authentication, you may need to switch to a CLI-based MCP server configuration and provide the token via environment variables. See [Sentry CLI MCP Example](/agent-platform/capabilities/mcp/#sentry).

diff --git a/src/content/docs/agent-platform/capabilities/rules.mdx b/src/content/docs/agent-platform/capabilities/rules.mdx
@@ -39,7 +39,7 @@ If both `WARP.md` and `AGENTS.md` exist in the same directory, `WARP.md` takes p
 :::
 
 :::caution
-The filename must be in **all caps** for Warp to recognize it (e.g., `AGENTS.md`, not `agents.md` or `Agents.md`). We recommend creating `AGENTS.md` for new projects.
+The filename must be in **all caps** for Warp to recognize it (e.g., `AGENTS.md`, not `agents.md` or `Agents.md`). Create `AGENTS.md` for new projects.
 :::
 
 **When you're in a directory:**
@@ -107,7 +107,7 @@ This ensures the most specific, project-relevant rules take priority over broade
 
 #### Project Rules
 
-* **When in a directory, set up Project Rules with a slash command:** Use `/init` in Auto-Detection or Agent Mode to:
+* **When in a directory, set up Project Rules with a slash command:** Use `/init` in Auto-detection or Agent Mode to:
   * Begin indexing your codebase or display indexing status
   * Generate an `AGENTS.md` file with initial context, or
   * Link an existing Rules file to `AGENTS.md`
@@ -131,4 +131,4 @@ When relevant, Agents automatically pull in applicable rules to guide their resp
 
 ### Rules privacy
 
-See our [Privacy page](/support-and-community/privacy-and-security/privacy/) for more information on how we handle data with Rules.
+See the [Privacy page](/support-and-community/privacy-and-security/privacy/) for more information on how Warp handles data with Rules.
diff --git a/src/content/docs/agent-platform/capabilities/skills.mdx b/src/content/docs/agent-platform/capabilities/skills.mdx
@@ -207,7 +207,7 @@ Skills can be stored at two levels: project-level (accessible only within that p
 
 ### Project skills
 
-Project skills live in your repository and are available when you're working in that project. We recommend storing them at your project root, but skills in subdirectories are also discovered when you're working within that subdirectory. This is useful for monorepos with separate `./frontend` and `./backend` directories.
+Project skills live in your repository and are available when you're working in that project. Store them at your project root, but skills in subdirectories are also discovered when you're working within that subdirectory. This is useful for monorepos with separate `./frontend` and `./backend` directories.
 
 Store them in any of these directories:
 

diff --git a/src/content/docs/agent-platform/cli-agents/claude-code.mdx b/src/content/docs/agent-platform/cli-agents/claude-code.mdx
@@ -62,7 +62,7 @@ For plugin source and updates, see the [claude-code-warp GitHub repository](http
 Claude Code supports the full set of Warp's agent integration features:
 
 * **Agent notifications** - Receive in-app and desktop alerts when Claude Code needs your attention. The notification UI displays your current git branch alongside agent status.
-* **Rich input editor** - Press `Ctrl-G` to open an expanded input editor for composing longer prompts.
+* **Rich input editor** - Press `Ctrl+G` to open an expanded input editor for composing longer prompts.
 * **Code review** - Send inline review comments directly to the agent from Warp's code review panel.
 * **Attach code as context** - Select code and send it to the agent as context.
 * **Vertical tabs with agent metadata** - Monitor Claude Code sessions with status indicators in Warp's tab bar.

diff --git a/src/content/docs/agent-platform/cli-agents/codex.mdx b/src/content/docs/agent-platform/cli-agents/codex.mdx
@@ -37,7 +37,7 @@ Then restart Codex. If this config isn't set, Warp displays a setup chip in the
 Codex supports the full set of Warp's agent integration features:
 
 * **Agent notifications** - Receive in-app and desktop alerts when Codex needs your attention. Requires a one-time config change (see [Setting up notifications](#setting-up-notifications)).
-* **Rich input editor** - Press `Ctrl-G` to open an expanded input editor for composing longer prompts.
+* **Rich input editor** - Press `Ctrl+G` to open an expanded input editor for composing longer prompts.
 * **Code review** - Send inline review comments directly to the agent from Warp's code review panel.
 * **Attach code as context** - Select code and send it to the agent as context.
 * **Vertical tabs with agent metadata** - Monitor Codex sessions with status indicators in Warp's tab bar.

diff --git a/src/content/docs/agent-platform/cli-agents/opencode.mdx b/src/content/docs/agent-platform/cli-agents/opencode.mdx
@@ -34,7 +34,7 @@ For plugin source and updates, see the [opencode-warp GitHub repository](https:/
 OpenCode supports the full set of Warp's agent integration features:
 
 * **Agent notifications** - Receive in-app and desktop alerts when OpenCode needs your attention. The notification UI displays your current git branch alongside agent status.
-* **Rich input editor** - Press `Ctrl-G` to open an expanded input editor for composing longer prompts.
+* **Rich input editor** - Press `Ctrl+G` to open an expanded input editor for composing longer prompts.
 * **Code review** - Send inline review comments directly to the agent from Warp's code review panel.
 * **Attach code as context** - Select code and send it to the agent as context.
 * **Vertical tabs with agent metadata** - Monitor OpenCode sessions with status indicators in Warp's tab bar.

diff --git a/src/content/docs/agent-platform/cli-agents/overview.mdx b/src/content/docs/agent-platform/cli-agents/overview.mdx
@@ -47,7 +47,7 @@ Not every feature is available for every agent. The table below shows current su
 
 | Feature&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Claude Code | Codex | OpenCode | Amp | Auggie | Copilot CLI | Cursor | Gemini CLI | Droid | Pi |
 |---|---|---|---|---|---|---|---|---|---|---|
-| Rich input editor (`Ctrl-G`) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
+| Rich input editor (`Ctrl+G`) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
 | Agent notifications | ✓ | ✓ | ✓ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ |
 | Code review comments | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
 | Attach code as context | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |

diff --git a/src/content/docs/agent-platform/cli-agents/rich-input.mdx b/src/content/docs/agent-platform/cli-agents/rich-input.mdx
@@ -6,7 +6,7 @@ description: >-
 ---
 import VideoEmbed from '@components/VideoEmbed.astro';
 
-Warp's rich input editor lets you write prompts for any CLI coding agent with the same editing experience you'd expect from an IDE — mouse support, context attachment, voice, and more. Press `Ctrl-G` (configurable) or click the **Rich Input** button in the agent utility bar to open it.
+Warp's rich input editor lets you write prompts for any CLI coding agent with the same editing experience you'd expect from an IDE — mouse support, context attachment, voice, and more. Press `Ctrl+G` (configurable) or click the **Rich Input** button in the agent utility bar to open it.
 
 <VideoEmbed url="https://youtu.be/f1MqXDv0gFM" title="Rich input editor for CLI agents" />
 
@@ -22,7 +22,7 @@ Warp's rich input editor lets you write prompts for any CLI coding agent with th
 
 There are two ways to open the rich input editor:
 
-1. **Keyboard shortcut** - Press `Ctrl-G` (configurable) while a supported agent is running in the active pane.
+1. **Keyboard shortcut** - Press `Ctrl+G` (configurable) while a supported agent is running in the active pane.
 2. **Rich Input button** - Click the **Rich Input** button in the agent utility bar at the bottom of the pane.
 
 <figure>
@@ -46,7 +46,7 @@ In the Warp app, go to **Settings** > **Agents** > **Third party CLI agents** to
 * **Auto show/hide based on agent status** - Automatically open the rich input editor when the agent needs input, and hide it when the agent is working. Works with agents that have plugin support and the plugin installed (Claude Code and OpenCode).
 * **Auto open on session start** - Automatically open the rich input editor when a CLI agent session starts.
 * **Auto dismiss after submission** - Close the editor after you send a prompt.
-* **Keyboard shortcut** - The default shortcut is `Ctrl-G`. Customize this in **Settings** > **Keyboard shortcuts**.
+* **Keyboard shortcut** - The default shortcut is `Ctrl+G`. Customize this in **Settings** > **Keyboard shortcuts**.
 * **Disable the Rich Input button** - Right-click the agent utility bar and remove the **Rich Input** chip, or disable the footer entirely in **Settings** > **Agents** > **Third party CLI agents**.
 
 <figure>

diff --git a/src/content/docs/agent-platform/getting-started/faqs.mdx b/src/content/docs/agent-platform/getting-started/faqs.mdx
@@ -13,15 +13,15 @@ Answers to frequently asked questions about Warp's agents, including supported m
 
 ### What data is sent and/or stored when using Agents in Warp?
 
-See our [Privacy page](/support-and-community/privacy-and-security/privacy/) for more information on how we handle data used by Agents in Warp.
+See the [Privacy page](/support-and-community/privacy-and-security/privacy/) for more information on how Warp handles data used by Agents in Warp.
 
 ### What happened to the old Warp AI chat panel?
 
 Agent Mode has replaced the previous AI chat panel. Agent Mode is more powerful in all of the chat panel's use cases. Not only can Agent Mode run commands for you, it can also gather context without you needing to copy and paste. To start a similar chat panel, click the AI button in the menu bar to open a new AI pane.
 
 ### Is my data used for model training?
 
-Warp reserves the right to use data collected to train models and improve Warp. Warp has Zero Data Retention with all its model providers (e.g. Anthropic, OpenAI, etc.). Please learn more about telemetry in our [Privacy page](/support-and-community/privacy-and-security/privacy/).
+Warp reserves the right to use data collected to train models and improve Warp. Warp has Zero Data Retention with all its model providers (e.g. Anthropic, OpenAI, etc.). Learn more about telemetry in the [Privacy page](/support-and-community/privacy-and-security/privacy/).
 
 ### What model are you using for Agent Mode?