diff --git a/src/assets/terminal/Blocklist-with-review-changes.png b/src/assets/terminal/block-list-with-review-changes.png similarity index 100% rename from src/assets/terminal/Blocklist-with-review-changes.png rename to src/assets/terminal/block-list-with-review-changes.png diff --git a/src/content/docs/agent-platform/capabilities/computer-use.mdx b/src/content/docs/agent-platform/capabilities/computer-use.mdx index 11c48b6c..3b52d874 100644 --- a/src/content/docs/agent-platform/capabilities/computer-use.mdx +++ b/src/content/docs/agent-platform/capabilities/computer-use.mdx @@ -25,7 +25,7 @@ Computer Use is only available in Warp's sandboxed cloud environments, not in lo --- -## Enabling Computer Use +## Enabling computer use Computer Use is **opt-in** and disabled by default. You can enable it through several entry points: @@ -66,7 +66,7 @@ In the Warp web app, you can enable or disable Computer Use for: --- -## How Computer Use works +## How computer use works ### Setup and requirements diff --git a/src/content/docs/agent-platform/capabilities/full-terminal-use.mdx b/src/content/docs/agent-platform/capabilities/full-terminal-use.mdx index cd2f8659..80b80793 100644 --- a/src/content/docs/agent-platform/capabilities/full-terminal-use.mdx +++ b/src/content/docs/agent-platform/capabilities/full-terminal-use.mdx @@ -19,7 +19,7 @@ With Full Terminal Use, Warp’s agent can attach to interactive tools like `psq You can either ask the agent to start an interactive program, or you can start it yourself and then tag the agent in once the tool is already running. In both cases, the agent sees the same terminal buffer (and PTY session) you do and can act on it. -## How Full Terminal Use works +## How full terminal use works #### Start an interactive command @@ -107,14 +107,14 @@ The behavior differs based on where you start the long-running command: 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 3. The input switches to Agent Mode with full controls - 4. When you exit, an agent conversation block appears in your terminal blocklist + 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 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 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 blocklist + 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 diff --git a/src/content/docs/agent-platform/capabilities/slash-commands.mdx b/src/content/docs/agent-platform/capabilities/slash-commands.mdx index e3a2d51d..4ec561b3 100644 --- a/src/content/docs/agent-platform/capabilities/slash-commands.mdx +++ b/src/content/docs/agent-platform/capabilities/slash-commands.mdx @@ -18,7 +18,7 @@ As you type, the menu filters results in real time, making it easy to find and r Warp currently supports the following built-in Slash Commands: -
Slash CommandDescription
/add-mcpAdd a new MCP server.
/add-promptAdd a new Agent Prompt in Warp Drive.
/add-ruleAdd a new Global Rule for the Agent.
/agentStart a new agent conversation. Optionally include a prompt to send immediately.
/changelogOpen the latest Warp changelog.
/cloud-agentStart a new cloud agent conversation. {'*'}
/compactFree up context by summarizing conversation history.
/compact-andCompact the current conversation and then send a follow-up prompt.
/conversationsOpen conversation history.
/costToggle credit usage details in the current conversation.
/create-environmentCreate a Warp Environment (Docker image + repos) via guided setup. {'*'}
/create-new-projectHave the Agent walk you through creating a new coding project. {'*'}
/export-to-clipboardExport the current conversation to clipboard in markdown format.
/export-to-fileExport the current conversation to a markdown file.
/feedbackSend feedback to the Warp team. Only the Agent-drafted flow consumes credits. See Using /feedback in Warp for details. {'*'}
/forkForks the current conversation into a new thread with the full context and history of the original.

You can optionally include a prompt that will be sent immediately in the forked conversation.
/fork-and-compactForks the current conversation and automatically compacts the forked version.

Useful when you want a fresh, summarized starting point that preserves relevant context while trimming the rest.
/fork-fromOpen a searchable menu to fork the conversation from a specific query. Select a query to create a fork that includes everything up to that point.
/indexIndex the current codebase using Codebase Context.
/initIndex the current codebase and generate an AGENTS.md file. {'*'}
/modelSwitch the base agent model for the current conversation.
/newStart a new agent conversation (alias for /agent).
/open-code-reviewOpen the code review pane.
/open-fileOpen a file for editing in Warp's code editor.
/open-mcp-serversView the status of your MCP servers.
/open-project-rulesOpen the Project Rules file (AGENTS).
/open-repoSwitch to another indexed repository.
/open-rulesView all of your global and project rules.
/open-settings-fileOpen the Warp settings file (settings.toml) in Warp's code editor.
/open-skillOpen an interactive menu to browse and edit project or global skills.
/orchestrateBreak a task into subtasks and run them in parallel with multiple agents. {'*'}
/planPrompt the Agent to do some research and create a plan for a task.
/pr-commentsPull GitHub PR review comments into Warp. {'*'}
/profileSwitch the active execution profile.
/promptsSearch saved prompts.
/rename-tabRename the current tab. Include the new tab name as an argument (for example, /rename-tab deploy).
/rewindRewind to a previous point in the conversation.
/skillsInvoke a skill from a searchable menu.
/usageOpen billing and usage settings.
+
Slash CommandDescription
/add-mcpAdd a new MCP server.
/add-promptAdd a new Agent Prompt in Warp Drive.
/add-ruleAdd a new Global Rule for the Agent.
/agentStart a new agent conversation. Optionally include a prompt to send immediately.
/changelogOpen the latest Warp changelog.
/cloud-agentStart a new cloud agent conversation. {'*'}
/compactFree up context by summarizing conversation history.
/compact-andCompact the current conversation and then send a follow-up prompt.
/conversationsOpen conversation history.
/costToggle credit usage details in the current conversation.
/create-environmentCreate a Warp Environment (Docker image + repos) via guided setup. {'*'}
/create-new-projectHave the Agent walk you through creating a new coding project. {'*'}
/export-to-clipboardExport the current conversation to clipboard in markdown format.
/export-to-fileExport the current conversation to a markdown file.
/feedbackSend feedback to the Warp team. Only the Agent-drafted flow consumes credits. See Using /feedback in Warp for details. {'*'}
/forkForks the current conversation into a new thread with the full context and history of the original.

You can optionally include a prompt that will be sent immediately in the forked conversation.
/fork-and-compactForks the current conversation and automatically compacts the forked version.

Useful when you want a fresh, summarized starting point that preserves relevant context while trimming the rest.
/fork-fromOpen a searchable menu to fork the conversation from a specific query. Select a query to create a fork that includes everything up to that point.
/indexIndex the current codebase using Codebase Context.
/initIndex the current codebase and generate an AGENTS.md file. {'*'}
/modelSwitch the base Agent Model for the current conversation.
/newStart a new agent conversation (alias for /agent).
/open-code-reviewOpen the code review pane.
/open-fileOpen a file for editing in Warp's code editor.
/open-mcp-serversView the status of your MCP servers.
/open-project-rulesOpen the Project Rules file (AGENTS).
/open-repoSwitch to another indexed repository.
/open-rulesView all of your global and project rules.
/open-settings-fileOpen the Warp settings file (settings.toml) in Warp's code editor.
/open-skillOpen an interactive menu to browse and edit project or global skills.
/orchestrateBreak a task into subtasks and run them in parallel with multiple agents. {'*'}
/planPrompt the Agent to do some research and create a plan for a task.
/pr-commentsPull GitHub PR review comments into Warp. {'*'}
/profileSwitch the active execution profile.
/promptsSearch saved prompts.
/rename-tabRename the current tab. Include the new tab name as an argument (for example, /rename-tab deploy).
/rewindRewind to a previous point in the conversation.
/skillsInvoke a skill from a searchable menu.
/usageOpen billing and usage settings.
:::caution Slash commands marked with a `*` consume credits to complete the task. diff --git a/src/content/docs/agent-platform/cloud-agents/faqs.mdx b/src/content/docs/agent-platform/cloud-agents/faqs.mdx index 265a84f7..a988e88e 100644 --- a/src/content/docs/agent-platform/cloud-agents/faqs.mdx +++ b/src/content/docs/agent-platform/cloud-agents/faqs.mdx @@ -49,7 +49,7 @@ If you're not happy with where it landed, you can take over to finish the task. Yes. [Codebase Context](/agent-platform/capabilities/codebase-context/) is enabled for all Oz cloud agent runs, as long as Codebase Context is enabled for your account. This includes runs triggered from the CLI, API/SDK, integrations (Slack, Linear, GitHub Actions), and schedules. No additional configuration is needed — if Codebase Context is enabled, cloud agents use it automatically. -### Can I access a shell inside a cloud agent environment? Are there limitations (Docker, Playwright, etc.)? +### Can I access a shell inside a cloud agent environment? are there limitations (docker, playwright, etc.)? Yes. Cloud agent runs execute in a full Linux environment and behave like a local development session. You can install dependencies, run Docker, and use headless tools like Playwright, subject to standard sandbox resource limits. @@ -78,7 +78,7 @@ Model choice is configurable per **agent** (and often per environment/workflow), Yes. Cloud agents support the same set of models available in Warp. Model selection is configurable per agent or environment. -### Can I authenticate cloud agents with my own ChatGPT or Claude Pro / Max plan? +### Can I authenticate cloud agents with my own chatgpt or claude pro / max plan? We're strong proponents of this, but it ultimately depends on model provider policies. We're actively working with providers to explore whether direct third-party authentication is possible. diff --git a/src/content/docs/agent-platform/cloud-agents/integrations/azure-devops.mdx b/src/content/docs/agent-platform/cloud-agents/integrations/azure-devops.mdx index a76169d5..16d4e83e 100644 --- a/src/content/docs/agent-platform/cloud-agents/integrations/azure-devops.mdx +++ b/src/content/docs/agent-platform/cloud-agents/integrations/azure-devops.mdx @@ -45,7 +45,7 @@ For Azure DevOps Server (self-hosted), sign in at `https://{server}/{collection} --- -## Step 2: Store the token as a Warp-managed secret +## Step 2: store the token as a warp-managed secret Warp injects managed secrets as environment variables at runtime and never exposes them in logs or configuration files. See the [Secrets](/agent-platform/cloud-agents/secrets/) documentation for full details on scoping and managing secrets. diff --git a/src/content/docs/agent-platform/cloud-agents/integrations/bitbucket.mdx b/src/content/docs/agent-platform/cloud-agents/integrations/bitbucket.mdx index 300f4d19..ef066a98 100644 --- a/src/content/docs/agent-platform/cloud-agents/integrations/bitbucket.mdx +++ b/src/content/docs/agent-platform/cloud-agents/integrations/bitbucket.mdx @@ -53,7 +53,7 @@ Bitbucket Cloud API tokens are managed through your Atlassian Account, which is --- -### Step 2: Store the token as a Warp-managed secret +### Step 2: store the token as a warp-managed secret Warp injects managed secrets as environment variables at runtime and never exposes them in logs or configuration files. See the [Secrets](/agent-platform/cloud-agents/secrets/) documentation for full details on scoping and managing secrets. @@ -110,7 +110,7 @@ Setup commands run on a fresh container for every agent run. Write them to be id --- -## Bitbucket Data Center / Server +## Bitbucket data center / server ### Step 1: Generate an HTTP access token @@ -128,7 +128,7 @@ Setup commands run on a fresh container for every agent run. Write them to be id --- -### Step 2: Store the token as a Warp-managed secret +### Step 2: store the token as a warp-managed secret Warp injects managed secrets as environment variables at runtime and never exposes them in logs or configuration files. See the [Secrets](/agent-platform/cloud-agents/secrets/) documentation for full details on scoping and managing secrets. diff --git a/src/content/docs/agent-platform/cloud-agents/integrations/cloud-providers.mdx b/src/content/docs/agent-platform/cloud-agents/integrations/cloud-providers.mdx index b3c99cef..1815cd16 100644 --- a/src/content/docs/agent-platform/cloud-agents/integrations/cloud-providers.mdx +++ b/src/content/docs/agent-platform/cloud-agents/integrations/cloud-providers.mdx @@ -154,7 +154,7 @@ AWS authentication mechanism. The following environment variables are set while ## GCP -### Step 1: Create a Workload Identity Pool and Provider +### Step 1: create a workload identity pool and provider The Oz GCP integration uses [Workload Identity Federation](https://docs.cloud.google.com/iam/docs/workload-identity-federation). You will need to configure a pool and provider to trust OIDC tokens produced by Oz. @@ -212,7 +212,7 @@ gcloud projects add-iam-policy-binding \ See [Workload Identity Federation principal types](https://docs.cloud.google.com/iam/docs/workload-identity-federation#principal-types) for the full syntax supported. -### Step 3: Enable Workload Identity Federation in your cloud agent environment +### Step 3: enable workload identity federation in your cloud agent environment Finally, configure the Oz cloud agent environment to use your Workload Identity Federation provider. diff --git a/src/content/docs/agent-platform/cloud-agents/integrations/gitlab.mdx b/src/content/docs/agent-platform/cloud-agents/integrations/gitlab.mdx index aa6fc21b..5d432020 100644 --- a/src/content/docs/agent-platform/cloud-agents/integrations/gitlab.mdx +++ b/src/content/docs/agent-platform/cloud-agents/integrations/gitlab.mdx @@ -46,7 +46,7 @@ These steps generate a personal access token tied to your GitLab account. If you --- -## Step 2: Store the token as a Warp-managed secret +## Step 2: store the token as a warp-managed secret Warp injects managed secrets as environment variables at runtime and never exposes them in logs or configuration files. See the [Secrets](/agent-platform/cloud-agents/secrets/) documentation for full details on scoping and managing secrets. diff --git a/src/content/docs/agent-platform/cloud-agents/integrations/linear.mdx b/src/content/docs/agent-platform/cloud-agents/integrations/linear.mdx index 3b8305f4..bc77f7fb 100644 --- a/src/content/docs/agent-platform/cloud-agents/integrations/linear.mdx +++ b/src/content/docs/agent-platform/cloud-agents/integrations/linear.mdx @@ -94,7 +94,7 @@ You can create an environment via: For full instructions, see our [Environment Setup](/agent-platform/cloud-agents/integrations/) docs. -#### 2. Create the Linear integration +#### 2. create the linear integration Once your environment exists, create the integration. diff --git a/src/content/docs/agent-platform/cloud-agents/integrations/quickstart-github-actions.mdx b/src/content/docs/agent-platform/cloud-agents/integrations/quickstart-github-actions.mdx index 82e28bb3..411514dd 100644 --- a/src/content/docs/agent-platform/cloud-agents/integrations/quickstart-github-actions.mdx +++ b/src/content/docs/agent-platform/cloud-agents/integrations/quickstart-github-actions.mdx @@ -18,7 +18,7 @@ Add Oz agents to your GitHub Actions workflows with [`oz-agent-action`](https:// --- -## 1. Add your API key as a GitHub Actions secret +## 1. Save your API key as a secret Store your Warp API key as a GitHub Actions secret so workflows can authenticate without exposing the key in your code. diff --git a/src/content/docs/agent-platform/cloud-agents/integrations/quickstart.mdx b/src/content/docs/agent-platform/cloud-agents/integrations/quickstart.mdx index b411e5f2..88ae1a1f 100644 --- a/src/content/docs/agent-platform/cloud-agents/integrations/quickstart.mdx +++ b/src/content/docs/agent-platform/cloud-agents/integrations/quickstart.mdx @@ -23,7 +23,7 @@ Oz integrations let you trigger cloud agents directly from the tools your team a --- -## 1. Connect the Slack integration +## 1. connect the slack integration The simplest way to set up the integration is **using the Oz web app**: @@ -51,7 +51,7 @@ oz integration create slack \ --prompt "Always open a draft PR and request review from the team-leads group." ``` -## 2. Tag @Oz in Slack +## 2. tag @oz in slack In any channel or thread in your Slack workspace, tag @Oz with a task: diff --git a/src/content/docs/agent-platform/cloud-agents/integrations/slack.mdx b/src/content/docs/agent-platform/cloud-agents/integrations/slack.mdx index 9d257977..14afd007 100644 --- a/src/content/docs/agent-platform/cloud-agents/integrations/slack.mdx +++ b/src/content/docs/agent-platform/cloud-agents/integrations/slack.mdx @@ -117,7 +117,7 @@ oz environment create \ See the [Environment Setup](/agent-platform/cloud-agents/integrations/) docs for detailed instructions. -#### 2. Create the Slack integration +#### 2. create the slack integration Once your environment is ready, create the integration. diff --git a/src/content/docs/agent-platform/cloud-agents/self-hosting/managed-direct.mdx b/src/content/docs/agent-platform/cloud-agents/self-hosting/managed-direct.mdx index 4122931f..dfb320ab 100644 --- a/src/content/docs/agent-platform/cloud-agents/self-hosting/managed-direct.mdx +++ b/src/content/docs/agent-platform/cloud-agents/self-hosting/managed-direct.mdx @@ -53,7 +53,7 @@ Export the API key so the worker can authenticate to Oz: export WARP_API_KEY="your_team_api_key" ``` -### 2. Start the worker with the Direct backend +### 2. start the worker with the direct backend Pass `--backend direct`: diff --git a/src/content/docs/agent-platform/cloud-agents/self-hosting/managed-kubernetes.mdx b/src/content/docs/agent-platform/cloud-agents/self-hosting/managed-kubernetes.mdx index df89b141..933a5250 100644 --- a/src/content/docs/agent-platform/cloud-agents/self-hosting/managed-kubernetes.mdx +++ b/src/content/docs/agent-platform/cloud-agents/self-hosting/managed-kubernetes.mdx @@ -68,7 +68,7 @@ Create the namespace if it doesn't exist: kubectl create namespace warp-oz ``` -### 2. Create the API key Secret +### 2. create the API key secret If you're not using an existing Secret, create one with the API key: diff --git a/src/content/docs/agent-platform/cloud-agents/self-hosting/troubleshooting.mdx b/src/content/docs/agent-platform/cloud-agents/self-hosting/troubleshooting.mdx index d0b90d83..05d65cc3 100644 --- a/src/content/docs/agent-platform/cloud-agents/self-hosting/troubleshooting.mdx +++ b/src/content/docs/agent-platform/cloud-agents/self-hosting/troubleshooting.mdx @@ -37,7 +37,7 @@ The steps below apply to the [managed architecture](/agent-platform/cloud-agents 2. Confirm the worker's namespace has these permissions: `create`, `get`, `list`, `watch`, `delete` on `jobs`; `get`, `list`, `watch` on `pods`; `get` on `pods/log`; `list` on `events`. 3. Confirm the task namespace allows pods with a **root init container** (required for sidecar materialization). 4. If your cluster restricts image sources, set `preflight_image` in the worker config to an allowlisted image (default is `busybox:1.36`). -5. To pull the preflight image from a private registry, configure `imagePullSecrets` in `pod_template` — these secrets also apply to the preflight Job. +5. To pull the preflight image from a private registry, configure **imagePullSecrets** in `pod_template` — these secrets also apply to the preflight Job. ### Direct backend @@ -117,7 +117,7 @@ See [Monitoring](/agent-platform/cloud-agents/self-hosting/monitoring/) for the 1. Check task Job and Pod status: `kubectl get jobs,pods -n `. 2. Common issues: * **Unschedulable pods** — Check node selectors, tolerations, and resource requests in `pod_template`. - * **Image pull failures** — Check `imagePullSecrets` in `pod_template`. + * **Image pull failures** — Inspect the `imagePullSecrets` value in `pod_template`. * **Admission policy rejections** — Review Pod Security Standards, OPA Gatekeeper, Kyverno, or similar admission controllers. 3. The worker fails a task early if its pod remains unschedulable beyond `unschedulable_timeout` (default `30s`). Raise the timeout or fix the scheduling issue. diff --git a/src/content/docs/agent-platform/cloud-agents/self-hosting/unmanaged.mdx b/src/content/docs/agent-platform/cloud-agents/self-hosting/unmanaged.mdx index 84a2a11f..5fd60368 100644 --- a/src/content/docs/agent-platform/cloud-agents/self-hosting/unmanaged.mdx +++ b/src/content/docs/agent-platform/cloud-agents/self-hosting/unmanaged.mdx @@ -2,7 +2,7 @@ title: Unmanaged architecture description: >- Run Oz agents in your existing CI, Kubernetes, or dev environments using - the oz agent run CLI with Warp tracking and observability. + `oz agent run`, with Warp tracking and observability. sidebar: label: "Unmanaged" --- diff --git a/src/content/docs/agent-platform/local-agents/agent-context/blocks-as-context.mdx b/src/content/docs/agent-platform/local-agents/agent-context/blocks-as-context.mdx index fbe910c3..4ef9e74e 100644 --- a/src/content/docs/agent-platform/local-agents/agent-context/blocks-as-context.mdx +++ b/src/content/docs/agent-platform/local-agents/agent-context/blocks-as-context.mdx @@ -10,7 +10,7 @@ import { Tabs, TabItem } from '@astrojs/starlight/components'; Warp’s Agent can use blocks from your Agent conversations as context to better understand your queries and generate more relevant responses. -You can attach a block directly from the terminal blocklist by clicking the AI sparkles icon on it and selecting “Attach as context.” +You can attach a block directly from the terminal block list by clicking the AI sparkles icon on it and selecting “Attach as context.”
![From a block of output, attach the block and ask Agent Mode to remove all untracked files.](../../../../../assets/agent-platform/remove_all_untracked_files.png) @@ -75,8 +75,8 @@ The most common use case is to ask the AI to fix an error. You can attach the er Blocks in Warp belong to either the terminal view or a specific agent conversation: -* **Terminal blocks** - Commands you run directly in the terminal. These always appear in your terminal blocklist and can be attached as context to multiple conversations. -* **Agent conversation blocks** - Commands executed within an agent conversation (either by you or the agent). These only appear within that specific conversation and don't clutter your terminal blocklist. +* **Terminal blocks** - Commands you run directly in the terminal. These always appear in your terminal block list and can be attached as context to multiple conversations. +* **Agent conversation blocks** - Commands executed within an agent conversation (either by you or the agent). These only appear within that specific conversation and don't clutter your terminal block list. This separation keeps your terminal view clean while preserving full context within each conversation. diff --git a/src/content/docs/agent-platform/local-agents/interacting-with-agents/conversation-forking.mdx b/src/content/docs/agent-platform/local-agents/interacting-with-agents/conversation-forking.mdx index ad1b06c9..31ac2d4b 100644 --- a/src/content/docs/agent-platform/local-agents/interacting-with-agents/conversation-forking.mdx +++ b/src/content/docs/agent-platform/local-agents/interacting-with-agents/conversation-forking.mdx @@ -41,7 +41,7 @@ You can also access this conversation view from the conversation chip in the cur #### **2. From the footer of the most recent AI response block** -In any conversation in the blocklist, click the **fork button** in the footer of the most recent AI block. A new conversation opens in a separate pane with the full context of the original. +In any conversation in the block list, click the **fork button** in the footer of the most recent AI block. A new conversation opens in a separate pane with the full context of the original. ![Fork conversation button in the footer of the most recent agent response block](../../../../../assets/agent-platform/conversation-forking-footer.png) diff --git a/src/content/docs/agent-platform/local-agents/interacting-with-agents/index.mdx b/src/content/docs/agent-platform/local-agents/interacting-with-agents/index.mdx index 9aa4a052..1aebb392 100644 --- a/src/content/docs/agent-platform/local-agents/interacting-with-agents/index.mdx +++ b/src/content/docs/agent-platform/local-agents/interacting-with-agents/index.mdx @@ -140,9 +140,9 @@ If you switch models during a conversation, the context usage indicator updates Warp automatically detects when your query has shifted to a new topic. When this happens, it suggests starting a new conversation instead of continuing in the same context. -These options appear in the blocklist, where you can decide whether to branch off into a new conversation or keep going with the current one. +These options appear in the block list, where you can decide whether to branch off into a new conversation or keep going with the current one. -![Suggestion in the blocklist to start a new conversation when Warp detects a topic shift.](../../../../../assets/agent-platform/conversation-segmentation.png) +![Suggestion in the block list to start a new conversation when Warp detects a topic shift.](../../../../../assets/agent-platform/conversation-segmentation.png) You can also create a new conversation manually at any time by using the keyboard shortcut, opening a new tab, or opening a new pane. diff --git a/src/content/docs/agent-platform/local-agents/interacting-with-agents/terminal-and-agent-modes.mdx b/src/content/docs/agent-platform/local-agents/interacting-with-agents/terminal-and-agent-modes.mdx index d7386c6c..4ceb8f5b 100644 --- a/src/content/docs/agent-platform/local-agents/interacting-with-agents/terminal-and-agent-modes.mdx +++ b/src/content/docs/agent-platform/local-agents/interacting-with-agents/terminal-and-agent-modes.mdx @@ -98,14 +98,14 @@ Agent Mode-specific items include the model selector, autodetection toggle, Cont Blocks in Warp belong to either the terminal view or a specific agent conversation: -* **Terminal blocks** - Commands you run directly in the terminal always appear in your terminal blocklist and can be attached as context to any conversation. -* **Agent conversation blocks** - Commands executed within an agent conversation (either by you or the agent) only appear within that specific conversation and don't appear in the terminal blocklist. +* **Terminal blocks** - Commands you run directly in the terminal always appear in your terminal block list and can be attached as context to any conversation. +* **Agent conversation blocks** - Commands executed within an agent conversation (either by you or the agent) only appear within that specific conversation and don't appear in the terminal block list. In agent conversations, context is managed automatically, with optional manual attachment from terminal view: * **Automatic context** - Commands executed within an agent conversation are included as context for subsequent prompts. * **Manual attachment** - You can attach terminal blocks to bring in outputs from outside the conversation. -* **Conversation scope** - Agent conversation blocks stay scoped to that conversation, while terminal blocks remain in the terminal blocklist. +* **Conversation scope** - Agent conversation blocks stay scoped to that conversation, while terminal blocks remain in the terminal block list. This separation keeps your terminal view clean while preserving full context within each conversation. For shortcuts, pending vs. attached context, and block selection behavior, see [Blocks as Context](/agent-platform/local-agents/agent-context/blocks-as-context/). @@ -242,7 +242,7 @@ While you're in an agent conversation, you can access Warp's [slash commands](/a * Type `/` to open the command menu * Keep typing to filter commands (for example: `/conversations`, `/compact`) -* Use `↑` / `↓` to navigate and `Enter` to run +* Use `↑` / `↓` to navigate and **Enter** to run * Press `esc` to dismiss the menu **Key slash commands in Agent Mode:** @@ -292,7 +292,7 @@ Use `/fork from` to choose exactly where in the conversation you want to branch 1. Type `/fork from` and press `Enter`. 2. A menu shows your previous queries in the conversation. 3. Select the query you want to fork from. -4. Choose `Enter` (existing pane) or `⌘↩` / `Ctrl+Shift+Enter` (new pane). +4. Press `Enter` for an existing pane, or `⌘↩` / `Ctrl+Shift+Enter` for a new pane. This is helpful when you want to go back to an earlier point and try a different approach. diff --git a/src/content/docs/code/code-review.mdx b/src/content/docs/code/code-review.mdx index f532917d..25ec20af 100644 --- a/src/content/docs/code/code-review.mdx +++ b/src/content/docs/code/code-review.mdx @@ -48,7 +48,7 @@ In terminal mode, when you're in a Git repository with changes, the Git diff chi When an Agent makes code edits in an [Agent Conversation](/agent-platform/local-agents/interacting-with-agents/), a `Review changes` button appears at the bottom of the conversation. Click the button to open the code review panel. -![Review changes at bottom of Agent Conversation.](../../../assets/terminal/Blocklist-with-review-changes.png) +![Review changes at bottom of Agent Conversation.](../../../assets/terminal/block-list-with-review-changes.png) ![Agent conversation footer with feedback buttons and a Review changes button](../../../assets/terminal/review-changes-in-footer.png) diff --git a/src/content/docs/enterprise/enterprise-features/bring-your-own-llm.mdx b/src/content/docs/enterprise/enterprise-features/bring-your-own-llm.mdx index 326b7314..93474f78 100644 --- a/src/content/docs/enterprise/enterprise-features/bring-your-own-llm.mdx +++ b/src/content/docs/enterprise/enterprise-features/bring-your-own-llm.mdx @@ -154,7 +154,7 @@ If no fallback is available (e.g., the admin disabled all non-Bedrock models), W * **Per-user authentication** — Each team member authenticates individually; credentials are not shared. * **No storage or logging** — Warp never stores or logs your cloud session tokens on its servers. -### Zero Data Retention (ZDR) +### Zero data retention (ZDR) Warp maintains **SOC 2 compliance** and has **Zero Data Retention (ZDR)** agreements with its contracted LLM providers. diff --git a/src/content/docs/enterprise/getting-started/getting-started-developers.mdx b/src/content/docs/enterprise/getting-started/getting-started-developers.mdx index 66ba2fe1..ef0c60b3 100644 --- a/src/content/docs/enterprise/getting-started/getting-started-developers.mdx +++ b/src/content/docs/enterprise/getting-started/getting-started-developers.mdx @@ -181,7 +181,7 @@ Warp Drive is your workspace for saving and sharing Workflows, Notebooks, Prompt Your team admin may have already created shared resources. Explore the Team section of Warp Drive to see what's available—including onboarding notebooks, deployment workflows, and coding standards rules. -### MCP (Model Context Protocol) +### MCP (model context protocol) MCP connects Warp's agents to external tools and services for enhanced context. diff --git a/src/content/docs/enterprise/getting-started/getting-started-enterprise.mdx b/src/content/docs/enterprise/getting-started/getting-started-enterprise.mdx index 478d07b8..c4c7366c 100644 --- a/src/content/docs/enterprise/getting-started/getting-started-enterprise.mdx +++ b/src/content/docs/enterprise/getting-started/getting-started-enterprise.mdx @@ -17,7 +17,7 @@ Before you begin: * You have admin access to your organization's identity provider (Okta, Microsoft Entra ID, Google Workspace, etc.) * You've identified which team members should have admin privileges in Warp -## Step 1: Configure Single Sign-On (SSO) +## Step 1: configure single sign-on (SSO) Warp uses SSO to authenticate users and control access to your organization's Warp team. Warp supports Okta, Microsoft Entra ID, Google Workspace, OneLogin, and any SAML 2.0 or OIDC compatible provider through [WorkOS](https://workos.com). diff --git a/src/content/docs/enterprise/getting-started/quickstart.mdx b/src/content/docs/enterprise/getting-started/quickstart.mdx index 963e162c..c885626a 100644 --- a/src/content/docs/enterprise/getting-started/quickstart.mdx +++ b/src/content/docs/enterprise/getting-started/quickstart.mdx @@ -26,7 +26,7 @@ If you have an existing Warp account from before your organization enabled SSO, 1. Visit [warp.dev/download](https://warp.dev/download) and select your platform (macOS, Linux, or Windows). 2. Install Warp: - * **macOS** - Open the `.dmg` and drag Warp to Applications. + * **macOS** - Open the **.dmg** and drag Warp to Applications. * **Linux** - Install via `.deb`, `.rpm`, or the install script. * **Windows** - Run the `.exe` installer. 3. Launch Warp and log in with SSO (Step 1). diff --git a/src/content/docs/enterprise/index.mdx b/src/content/docs/enterprise/index.mdx index b373bec5..07d336af 100644 --- a/src/content/docs/enterprise/index.mdx +++ b/src/content/docs/enterprise/index.mdx @@ -9,7 +9,7 @@ Warp Enterprise is built for organizations that want to accelerate software deve Warp has two core products: -* **Warp Terminal** - A modern terminal designed for agentic development where developers run commands, collaborate with agents, and orchestrate autonomous work from the command line. +* **Warp** - A modern terminal designed for agentic development where developers run commands, collaborate with agents, and orchestrate autonomous work from the command line. * **Oz** - Warp's programmable agent for running and coordinating agents at scale. Oz powers all agents in Warp, whether they run locally or in the cloud, and provides the orchestration, tracking, and control plane for scalable agent workflows. ## Who Warp Enterprise is for diff --git a/src/content/docs/enterprise/security-and-compliance/security-overview.mdx b/src/content/docs/enterprise/security-and-compliance/security-overview.mdx index d5f40686..c2bfa95b 100644 --- a/src/content/docs/enterprise/security-and-compliance/security-overview.mdx +++ b/src/content/docs/enterprise/security-and-compliance/security-overview.mdx @@ -20,7 +20,7 @@ Warp's security philosophy centers on **transparency and developer control**: ## What telemetry does Warp collect and why? -### Zero Data Retention (ZDR) +### Zero data retention (ZDR) Warp has **Zero Data Retention (ZDR)** agreements with its contracted LLM providers (Anthropic, OpenAI, Google), meaning they do not store or train on your data. ZDR applies across all Warp plans. @@ -162,7 +162,7 @@ Security-relevant controls include: ## Security features for developers -### Bring Your Own LLM (BYOLLM) +### Bring your own LLM (BYOLLM) Route agent inference through your own cloud infrastructure for complete control: diff --git a/src/content/docs/guides/agent-workflows/how-to-edit-agent-code-in-warp.mdx b/src/content/docs/guides/agent-workflows/how-to-edit-agent-code-in-warp.mdx index 434a7e38..ffa69c4d 100644 --- a/src/content/docs/guides/agent-workflows/how-to-edit-agent-code-in-warp.mdx +++ b/src/content/docs/guides/agent-workflows/how-to-edit-agent-code-in-warp.mdx @@ -15,7 +15,7 @@ This makes debugging and bug-fix workflows fast, transparent, and interactive. --- -### 1. Starting an Agent Task +### 1. starting an agent task When you start an agent task, Warp: @@ -30,7 +30,7 @@ Warp shows progress step-by-step, including what it’s searching and which file --- -### 2. Reviewing Diffs +### 2. reviewing diffs Warp generates diffs for every proposed change.\ You can: @@ -43,7 +43,7 @@ This editor view works like a lightweight IDE — perfect for quick corrections --- -### 3. Applying or Skipping Changes +### 3. applying or skipping changes Once you’re happy with a diff: @@ -54,7 +54,7 @@ You can control this level of autonomy globally in Settings → AI → Autonomy. --- -### 4. Compiling and Verifying Fixes +### 4. compiling and verifying fixes After applying changes, you can immediately test your build, like: @@ -66,7 +66,7 @@ Warp monitors compilation, verifies results, and runs post-checks automatically. --- -### 5. Visual Verification +### 5. visual verification In this example, the bug involved a checkbox not being honored in the UI.\ \ diff --git a/src/content/docs/guides/agent-workflows/how-to-run-3-agents-in-parallel-summarize-logs-analyze-pr-modify-ui.mdx b/src/content/docs/guides/agent-workflows/how-to-run-3-agents-in-parallel-summarize-logs-analyze-pr-modify-ui.mdx index 0d4ab8cf..abb07843 100644 --- a/src/content/docs/guides/agent-workflows/how-to-run-3-agents-in-parallel-summarize-logs-analyze-pr-modify-ui.mdx +++ b/src/content/docs/guides/agent-workflows/how-to-run-3-agents-in-parallel-summarize-logs-analyze-pr-modify-ui.mdx @@ -49,7 +49,7 @@ In the demo, we run three parallel workflows: Analyze how many pull requests a team member has assigned. ``` - Use the Github CLI tool to summarize all open PRs for review that are assigned to user. I'd like to see who is the author of the PR, when was it opened, how long has it been open for, which repo is it in, are there open an dunaddressed commens on it, and is it ready for review? + Use the GitHub CLI tool to summarize all open PRs for review that are assigned to user. I'd like to see who is the author of the PR, when was it opened, how long has it been open for, which repo is it in, are there open an dunaddressed commens on it, and is it ready for review? ``` diff --git a/src/content/docs/guides/agent-workflows/how-to-run-multiple-ai-coding-agents.mdx b/src/content/docs/guides/agent-workflows/how-to-run-multiple-ai-coding-agents.mdx index 21f5e985..4b52a26b 100644 --- a/src/content/docs/guides/agent-workflows/how-to-run-multiple-ai-coding-agents.mdx +++ b/src/content/docs/guides/agent-workflows/how-to-run-multiple-ai-coding-agents.mdx @@ -120,7 +120,7 @@ Tab configs are TOML files that define the directory, startup commands, and layo Tab configs pair well with [Git worktrees](/code/git-worktrees/). Create a worktree for each agent so they work on isolated branches, then merge the best results. ::: -## 6. Use Git worktrees for isolated agent workspaces +## 6. use git worktrees for isolated agent workspaces When multiple agents modify the same files, they can create conflicts. Git worktrees solve this by giving each agent its own copy of your repo on a separate branch. diff --git a/src/content/docs/guides/agent-workflows/running-multiple-agents-at-once-with-warp.mdx b/src/content/docs/guides/agent-workflows/running-multiple-agents-at-once-with-warp.mdx index cce8860c..b280b4f9 100644 --- a/src/content/docs/guides/agent-workflows/running-multiple-agents-at-once-with-warp.mdx +++ b/src/content/docs/guides/agent-workflows/running-multiple-agents-at-once-with-warp.mdx @@ -10,7 +10,7 @@ import VideoEmbed from '@components/VideoEmbed.astro'; -### 1. Why Multiple Agents Matter +### 1. why multiple agents matter Sometimes you need to work on several coding tasks at once — fix a PR, add a feature, debug a build — without losing context.\ \ @@ -18,7 +18,7 @@ Warp lets you run multiple agent tasks simultaneously, all within one workspace. --- -### 2. How It Works +### 2. how it works Each agent runs in its own thread, complete with: @@ -30,7 +30,7 @@ Because Warp is a desktop app, it can send system notifications to alert you whe --- -### 3. Example: Reverting a PR and Editing a Shortcut +### 3. example: reverting a PR and editing a shortcut Ben uses voice mode to quickly start tasks. @@ -54,7 +54,7 @@ Warp modifies `input.rs`, previews the diff, and Ben applies the change directly --- -### 4. Managing Multiple Tasks +### 4. managing multiple tasks You can switch between concurrent agents: @@ -66,7 +66,7 @@ You can even fast-forward agents to auto-approve all code diffs once you trust t --- -### 5. Parallel Contexts +### 5. parallel contexts In another repo, Ben adds a new Eval test via a different agent: @@ -83,7 +83,7 @@ Meanwhile, the first agent continues working on the keyboard shortcut task. --- -### 6. Reviewing All Active Agents +### 6. reviewing all active agents Open the Agent Mode Dashboard to see: diff --git a/src/content/docs/guides/agent-workflows/understanding-your-codebase.mdx b/src/content/docs/guides/agent-workflows/understanding-your-codebase.mdx index ffbaa5cb..e125bb9e 100644 --- a/src/content/docs/guides/agent-workflows/understanding-your-codebase.mdx +++ b/src/content/docs/guides/agent-workflows/understanding-your-codebase.mdx @@ -10,7 +10,7 @@ import VideoEmbed from '@components/VideoEmbed.astro'; -### 1. The Challenge +### 1. the challenge Kevin, who worked on Warp’s Windows and Linux builds, wanted to jump into a feature he hadn’t touched before: Block Sharing.\ \ @@ -35,7 +35,7 @@ This prompt tells Warp to: --- -### 3. Real Example: Block Sharing +### 3. real example: block sharing Kevin types `block sharing` into Warp’s shared workflow.\ Warp: @@ -54,7 +54,7 @@ No more manual onboarding or guessing file names. --- -### 4. Incremental Syncing +### 4. incremental syncing Whenever you change a file in an indexed repo: @@ -66,7 +66,7 @@ That means agents never reference stale code. --- -### 5. Why It’s Game-Changing +### 5. why it’s game-changing Codebase Context helps teams: diff --git a/src/content/docs/guides/agent-workflows/using-images-as-context-with-warp.mdx b/src/content/docs/guides/agent-workflows/using-images-as-context-with-warp.mdx index 82dbb86c..de7897ca 100644 --- a/src/content/docs/guides/agent-workflows/using-images-as-context-with-warp.mdx +++ b/src/content/docs/guides/agent-workflows/using-images-as-context-with-warp.mdx @@ -10,7 +10,7 @@ import VideoEmbed from '@components/VideoEmbed.astro'; -### 1. Why Images Matter +### 1. why images matter Humans process visuals much faster than text — and the same applies to AI.\ \ @@ -22,7 +22,7 @@ That’s why Warp supports images as context — letting you attach screenshots --- -### 2. What Image Context Does +### 2. what image context does Image Context allows you to: @@ -38,15 +38,15 @@ This is especially useful for frontend tasks like: --- -### 3. Building an MCP Marketplace from Figma +### 3. building an MCP marketplace from figma Taking a Figma mock of an MCP Server Marketplace and using it as input for Warp. -#### Step 1. Capture the Mock +#### Step 1. capture the mock Take a screenshot of your design (e.g., the MCP Marketplace layout). -#### Step 2. Attach the Image +#### Step 2. attach the image In Warp: @@ -56,7 +56,7 @@ In Warp: --- -### 4. Running the Task +### 4. running the task Once attached, Warp’s agent: @@ -71,7 +71,7 @@ You can view and edit these diffs in the Code Diff Viewer, similar to GitHub’s --- -### 5. Reviewing the Results +### 5. reviewing the results The agent built: @@ -85,7 +85,7 @@ The agent built: --- -### 6. Optimizing for Performance +### 6. optimizing for performance Because images can consume tokens quickly, Warp automatically: diff --git a/src/content/docs/guides/agent-workflows/warp-for-product-managers.mdx b/src/content/docs/guides/agent-workflows/warp-for-product-managers.mdx index bac5158b..b6cf1e6d 100644 --- a/src/content/docs/guides/agent-workflows/warp-for-product-managers.mdx +++ b/src/content/docs/guides/agent-workflows/warp-for-product-managers.mdx @@ -1,5 +1,5 @@ --- -title: "5 AI agent workflows for product managers" +title: "5 agent workflows for product managers" description: >- Five agent workflows that automate status updates, documentation, Slack search, and meeting prep for product managers. @@ -64,7 +64,7 @@ The result is a structured first draft, grounded in your specific context, ready **Without MCP**: Copy the finished draft and paste it into your docs tool manually. ::: -## 3. Search Slack for meeting prep +## 3. search slack for meeting prep Before a meeting or project check-in, you often need to catch up on activity across multiple Slack channels. Manually reading through 10+ channels is slow. With the Slack MCP server, you can search and summarize in one prompt. diff --git a/src/content/docs/guides/agent-workflows/warp-vs-claude-code.mdx b/src/content/docs/guides/agent-workflows/warp-vs-claude-code.mdx index 97448f83..bb8d03f1 100644 --- a/src/content/docs/guides/agent-workflows/warp-vs-claude-code.mdx +++ b/src/content/docs/guides/agent-workflows/warp-vs-claude-code.mdx @@ -25,7 +25,7 @@ Both can: --- -### 2. Setup and Interface +### 2. setup and interface #### Claude Code @@ -41,7 +41,7 @@ Both can: --- -### 3. Reviewing Diffs +### 3. reviewing diffs In Claude Code: @@ -56,7 +56,7 @@ In Warp: --- -### 4. Planning & Context Gathering +### 4. planning & context gathering Both support planning mode for complex tasks: @@ -70,7 +70,7 @@ For context: --- -### 5. Model Selection +### 5. model selection Claude Code lets you pick between Claude 3 models (`Sonnet`, `Opus`, `Haiku`) via the `/model` menu. @@ -102,7 +102,7 @@ Warp also supports codebase indexing, which creates embeddings for faster semant --- -### 7. Managing Agents Over Time +### 7. managing agents over time Claude Code: @@ -116,7 +116,7 @@ Warp: --- -### 8. Performance Comparison +### 8. performance comparison Ben ran both tools on the same coding task — fixing a bug in the `renderKeyboardShortcut` function from a Sentry issue. diff --git a/src/content/docs/guides/build-an-app-in-warp/building-a-real-time-chat-app-github-mcp-railway.mdx b/src/content/docs/guides/build-an-app-in-warp/building-a-real-time-chat-app-github-mcp-railway.mdx index 52526d23..de00ac81 100644 --- a/src/content/docs/guides/build-an-app-in-warp/building-a-real-time-chat-app-github-mcp-railway.mdx +++ b/src/content/docs/guides/build-an-app-in-warp/building-a-real-time-chat-app-github-mcp-railway.mdx @@ -1,5 +1,5 @@ --- -title: Building a Real-time Chat App (Github MCP + Railway ) +title: Building a Real-time Chat App (GitHub MCP + Railway ) description: >- Build and deploy a real-time chat app with Python, FastAPI, and JavaScript — from idea to production, all inside Warp. @@ -229,6 +229,6 @@ The project: a **real-time chat application** built with **Python (FastAPI)** an ### Appendix -* [Github MCP Server](https://github.com/github/github-mcp-server) +* [GitHub MCP Server](https://github.com/github/github-mcp-server) * [Docker Desktop download](https://www.docker.com/products/docker-desktop/) * [Railway](https://railway.com/) diff --git a/src/content/docs/guides/build-an-app-in-warp/building-a-slackbot.mdx b/src/content/docs/guides/build-an-app-in-warp/building-a-slackbot.mdx index 58e1a9a9..45e2cdb8 100644 --- a/src/content/docs/guides/build-an-app-in-warp/building-a-slackbot.mdx +++ b/src/content/docs/guides/build-an-app-in-warp/building-a-slackbot.mdx @@ -40,7 +40,7 @@ The setup takes just a few steps — clone, configure, and run — and requires cp .env.example .env ``` - Then open `.env` and fill in the following values: + Then open **.env** and fill in the following values: * `SLACK_BOT_TOKEN` – Your bot token from Slack, which starts with `xoxb-`. You can find this under your Slack app’s **OAuth & Permissions** page. * `SLACK_APP_TOKEN` – Your app-level token from Slack, which starts with `xapp-`. Create this in your Slack app’s **Basic Information → App-Level Tokens**, and ensure it has the `connections:write` scope (required for Socket Mode). @@ -57,7 +57,7 @@ The setup takes just a few steps — clone, configure, and run — and requires cp repos.yaml.template repos.yaml ``` - Then open `repos.yaml` and list the repositories you want the bot to monitor, for example: + Then open **repos.yaml** and list the repositories you want the bot to monitor, for example: ```yaml repositories: diff --git a/src/content/docs/guides/build-an-app-in-warp/building-warps-input-with-warp.mdx b/src/content/docs/guides/build-an-app-in-warp/building-warps-input-with-warp.mdx index 54a369bc..a5f0f993 100644 --- a/src/content/docs/guides/build-an-app-in-warp/building-warps-input-with-warp.mdx +++ b/src/content/docs/guides/build-an-app-in-warp/building-warps-input-with-warp.mdx @@ -24,7 +24,7 @@ Most people were excited, but engineering resources were stretched thin — focu So I thought: _“What if I just Warp it?”_ -#### Step 1. Locating the Git Diff Chip Code +#### Step 1. locating the git diff chip code Inside the universal input, there’s a small Git Diff chip — it shows your current branch and open changes. It was one pixel too tall. That tiny visual bug drove me nuts, so I used Warp to find where it lived. @@ -37,7 +37,7 @@ It used a combination of semantic search, code indexing, and traditional grep to --- -#### Step 2. Modifying the Font Size +#### Step 2. modifying the font size Once Warp located the implementation, I asked it to reduce the font size by 1 pixel. @@ -50,7 +50,7 @@ I reviewed the diffs to confirm everything looked good. --- -#### Step 3. Building and Testing the Change +#### Step 3. building and testing the change Next, I rebuilt the app using: diff --git a/src/content/docs/guides/configuration/creating-rules-for-agents.mdx b/src/content/docs/guides/configuration/creating-rules-for-agents.mdx index 5a46b6b3..bd69be24 100644 --- a/src/content/docs/guides/configuration/creating-rules-for-agents.mdx +++ b/src/content/docs/guides/configuration/creating-rules-for-agents.mdx @@ -12,7 +12,7 @@ _Speaker: Maggie — Engineer at Warp_ -### 1. Starting with Agent Mode Evals +### 1. starting with Agent Mode evals I’m currently adding **Evals** (short for evaluations) to test a new feature I’ve been building. @@ -22,7 +22,7 @@ This makes onboarding onto new tasks fast and collaborative. --- -### 2. Adding a Rust Syntax Eval +### 2. adding a rust syntax eval Next, I want to add an Eval that tests for Rust syntax errors.\ So I ask Warp to update the Dockerfile to include Rust. @@ -32,7 +32,7 @@ It also includes `gcc` and `python` via a single `apt-get` line, which doesn’t --- -### 3. Stashing Changes & Creating a Rule +### 3. stashing changes & creating a rule Instead of fixing this manually every time, I decide to stash the current changes and create a reusable Rule that encodes our convention: diff --git a/src/content/docs/guides/configuration/how-to-create-project-rules-for-an-existing-project-astro-typescript-tailwind.mdx b/src/content/docs/guides/configuration/how-to-create-project-rules-for-an-existing-project-astro-typescript-tailwind.mdx index 9b03c575..6cd09c5a 100644 --- a/src/content/docs/guides/configuration/how-to-create-project-rules-for-an-existing-project-astro-typescript-tailwind.mdx +++ b/src/content/docs/guides/configuration/how-to-create-project-rules-for-an-existing-project-astro-typescript-tailwind.mdx @@ -67,7 +67,7 @@ Share Your Brewfiles is an Astro-based website that allows developers to share a * `exchangeCodeForAccessToken.ts` - GitHub OAuth token exchange * `logSearch.json.ts` - Analytics for search functionality -### Core Library Functions (`src/lib/`) +### Core library functions (`src/lib/`) * `generatePersonality.ts` - Complex algorithm that analyzes brewfile packages and assigns personality types (15 different personalities) * `personalityBuckets.ts` - Defines personality type metadata and descriptions * `validateBrewfileData.ts` - Data validation for brewfile uploads @@ -121,7 +121,7 @@ curl "http://localhost:4321/api/getRankedPackages.json" ## Architecture Notes -### Personality Generation System +### Personality generation system The core feature analyzes brewfile packages against a curated dictionary (`labelledBrewfiles.ts`) that categorizes packages by: - Developer type (Backend, Frontend, DevOps, Security, Data, General) - Package characteristics (AI tools, organization tools, customization, popularity rank) @@ -135,7 +135,7 @@ The system calculates percentage distributions and applies complex rules to assi - Real-time personality generation happens asynchronously after uploads - GitHub OAuth integration for user authentication -### Path Alias System +### Path alias system Uses TypeScript path mapping with `@/*` pointing to `./src/*` for clean imports. ### Astro Configuration @@ -144,27 +144,27 @@ Uses TypeScript path mapping with `@/*` pointing to `./src/*` for clean imports. - Sitemap generation for SEO - Prefetch enabled for performance -## Development Environment Setup +## Development environment setup ### Prerequisites - Node.js (version compatible with Astro 4) - Access to Firebase project (config is in source but consider security implications) - GitHub OAuth app for testing upload functionality -### Local Development Notes +### Local development notes - The site uses server-side rendering so API routes work in development - Firebase config is currently in source code - be aware of security implications - GitHub OAuth integration requires valid access tokens for uploads - Personality generation is computationally expensive with large datasets -### Custom Tailwind Configuration +### Custom tailwind configuration - Dark theme with custom color palette (`bkg: #111111`) - Custom accent colors (teal, orange, green, pink, blue variants) - Marquee animations for scrolling elements - Responsive typography with fluid scaling - Container queries support -## File Structure Navigation +## File structure navigation - src/ - pages/ @@ -179,20 +179,20 @@ Uses TypeScript path mapping with `@/*` pointing to `./src/*` for clean imports. - firebase/ Firebase configuration -## Common Development Tasks +## Common development tasks -### Adding New Personality Types +### Adding new personality types 1. Update `DeveloperPersonalityType` enum in `src/types/personality.ts` 2. Add detection function in `src/lib/generatePersonality.ts` 3. Update `personalityBuckets.ts` with new personality metadata 4. Add corresponding image to `public/images/` -### Modifying Package Analysis +### Modifying package analysis - Update `labelledBrewfiles.ts` to modify package categorization - Adjust percentage thresholds in personality detection functions - Test with different brewfile compositions -### API Route Development +### API route development - All routes in `src/pages/api/` become serverless functions on Vercel - Use `export const prerender = false;` for dynamic routes - Handle errors consistently with try/catch blocks @@ -200,7 +200,7 @@ Uses TypeScript path mapping with `@/*` pointing to `./src/*` for clean imports. --- -## Keep the File Lean and Intentional +## Keep the file lean and intentional @@ -220,7 +220,7 @@ If the file grows large (e.g., **500+ lines**), run it through a **prompt optimi --- -## Use Sub‑directory Rules for Monorepos +## Use sub‑directory rules for monorepos For large repos, you can generate localized rule files in sub‑trees. Navigate into a subfolder and run `/init` again to create a **directory‑scoped `Warp.md`** tailored to that area: diff --git a/src/content/docs/guides/configuration/how-to-set-up-self-serve-data-analytics-with-skills.mdx b/src/content/docs/guides/configuration/how-to-set-up-self-serve-data-analytics-with-skills.mdx index d9d78fe2..a5018c97 100644 --- a/src/content/docs/guides/configuration/how-to-set-up-self-serve-data-analytics-with-skills.mdx +++ b/src/content/docs/guides/configuration/how-to-set-up-self-serve-data-analytics-with-skills.mdx @@ -23,7 +23,7 @@ In this 40-minute livestream, Warp's data team demonstrates the workflow end-to- -## 1. Install the two Skills +## 1. install the two skills Warp automatically discovers any Skill stored under `.agents/skills/` in your repo, so committing the two directories makes them available to every teammate's Agent runs. Clone the public [warpdotdev/oz-skills](https://github.com/warpdotdev/oz-skills) repo and copy the two Skill directories into your own dbt repo: diff --git a/src/content/docs/guides/configuration/trigger-reusable-actions-with-saved-prompts.mdx b/src/content/docs/guides/configuration/trigger-reusable-actions-with-saved-prompts.mdx index 51ac55c0..153897df 100644 --- a/src/content/docs/guides/configuration/trigger-reusable-actions-with-saved-prompts.mdx +++ b/src/content/docs/guides/configuration/trigger-reusable-actions-with-saved-prompts.mdx @@ -10,7 +10,7 @@ import VideoEmbed from '@components/VideoEmbed.astro'; -### 1. Automating Commits +### 1. automating commits When working on a PR, instead of typing long commit messages, you can use a saved prompt. @@ -30,7 +30,7 @@ Because it’s saved in your team drive, anyone can reuse it. --- -### 2. Reviewing Code with Prompts +### 2. reviewing code with prompts Before creating a PR, you can run another saved prompt. @@ -49,7 +49,7 @@ Warp automatically surfaces real issues before you even open a PR — saving tim --- -### 3. Opening a Pull Request Automatically +### 3. opening a pull request automatically Once your code looks clean, trigger your final saved prompt. @@ -62,7 +62,7 @@ Warp will: --- -### 4. Sharing and Team Usage +### 4. sharing and team usage All saved prompts live in your Team Warp Drive, meaning: diff --git a/src/content/docs/guides/devops/how-to-write-sql-commands-inside-a-postgres-repl.mdx b/src/content/docs/guides/devops/how-to-write-sql-commands-inside-a-postgres-repl.mdx index fef8338b..fa154823 100644 --- a/src/content/docs/guides/devops/how-to-write-sql-commands-inside-a-postgres-repl.mdx +++ b/src/content/docs/guides/devops/how-to-write-sql-commands-inside-a-postgres-repl.mdx @@ -153,7 +153,7 @@ You’ll learn how to: --- -### 🏁 Key Takeaways +### 🏁 key takeaways * **Command + I** activates Warp’s AI input within any interactive shell. * Warp understands natural language and produces valid commands for the current REPL. diff --git a/src/content/docs/guides/external-tools/github-mcp-summarizing-open-prs-and-creating-gh-issues.mdx b/src/content/docs/guides/external-tools/github-mcp-summarizing-open-prs-and-creating-gh-issues.mdx index 651354bf..64535f10 100644 --- a/src/content/docs/guides/external-tools/github-mcp-summarizing-open-prs-and-creating-gh-issues.mdx +++ b/src/content/docs/guides/external-tools/github-mcp-summarizing-open-prs-and-creating-gh-issues.mdx @@ -1,5 +1,5 @@ --- -title: "Github MCP: Summarizing Open PRs & Creating GH Issues" +title: "GitHub MCP: Summarizing Open PRs & Creating GH Issues" description: >- Connect the GitHub MCP server to Warp to summarize open PRs, create issues from TODO comments, and automate repo management. @@ -16,7 +16,7 @@ The GitHub MCP Server lets Warp agents read, write, and automate tasks in your G ### 2. Setup -#### Step 1. Get a GitHub Personal Access Token +#### Step 1. get a github personal access token 1. Go to **GitHub → Settings → Developer Settings → Personal Access Tokens** 2. Create a new token and enable: @@ -25,7 +25,7 @@ The GitHub MCP Server lets Warp agents read, write, and automate tasks in your G --- -#### Step 2. Add the Server in Warp +#### Step 2. add the server in warp 1. Open the **MCP Panel** via Command Palette (`Cmd + P`) 2. Click **Add Server** @@ -34,7 +34,7 @@ The GitHub MCP Server lets Warp agents read, write, and automate tasks in your G --- -### 3. Workflow 1 — Summarize All Open PRs +### 3. workflow 1 — summarize all open prs Use Warp’s agent to summarize pull requests: @@ -48,7 +48,7 @@ Perfect for daily PR triage or stand-ups. --- -### 4. Workflow 2 — Create GitHub Issues from TODOs +### 4. workflow 2 — create github issues from todos Use a saved prompt to automate issue creation. @@ -62,7 +62,7 @@ This turns scattered notes into trackable tickets instantly. --- -### 5. Why It’s Useful +### 5. why it’s useful * Save 20–30 minutes per session * Keep repos synchronized automatically diff --git a/src/content/docs/guides/external-tools/how-to-set-up-claude-code.mdx b/src/content/docs/guides/external-tools/how-to-set-up-claude-code.mdx index f4b0044f..31953e87 100644 --- a/src/content/docs/guides/external-tools/how-to-set-up-claude-code.mdx +++ b/src/content/docs/guides/external-tools/how-to-set-up-claude-code.mdx @@ -15,7 +15,7 @@ Claude Code is Anthropic's AI coding agent. It reads your codebase, writes and e * **macOS 13+, Windows 10+, or Ubuntu 20.04+** — See [Claude Code system requirements](https://docs.anthropic.com/en/docs/claude-code/setup) for full platform details. * **Git** — Claude Code works best inside a Git repository. On Windows, [Git for Windows](https://git-scm.com) is required. -## 1. Install Claude Code +## 1. install claude code Follow Anthropic's [official installation guide](https://docs.anthropic.com/en/docs/claude-code/quickstart) to install Claude Code. The native installer (recommended) requires no dependencies and auto-updates in the background. diff --git a/src/content/docs/guides/external-tools/how-to-set-up-codex-cli.mdx b/src/content/docs/guides/external-tools/how-to-set-up-codex-cli.mdx index 6ea6efac..1812b190 100644 --- a/src/content/docs/guides/external-tools/how-to-set-up-codex-cli.mdx +++ b/src/content/docs/guides/external-tools/how-to-set-up-codex-cli.mdx @@ -15,7 +15,7 @@ Codex CLI is OpenAI's open-source coding agent. It reads your codebase, edits fi * **Node.js 18+** (for npm install) or **Homebrew** (for macOS) — Choose your preferred package manager. * **macOS or Linux** — Windows support is experimental; for the best Windows experience, use Codex in a WSL workspace. -## 1. Install Codex CLI +## 1. install codex CLI Install Codex CLI globally with npm or Homebrew: diff --git a/src/content/docs/guides/external-tools/how-to-set-up-gemini-cli.mdx b/src/content/docs/guides/external-tools/how-to-set-up-gemini-cli.mdx index 6be725af..ce4dbdd4 100644 --- a/src/content/docs/guides/external-tools/how-to-set-up-gemini-cli.mdx +++ b/src/content/docs/guides/external-tools/how-to-set-up-gemini-cli.mdx @@ -15,7 +15,7 @@ Gemini CLI is Google's open-source coding agent. It brings Gemini directly into * **Node.js 20+** — Required for installation. Check with `node -v`. * **macOS, Linux, or Windows** — See [Gemini CLI system requirements](https://geminicli.com/docs/get-started/installation/) for recommended specifications. -## 1. Install Gemini CLI +## 1. install gemini CLI Follow Google's [official installation guide](https://geminicli.com/docs/get-started/installation/) to install Gemini CLI. The two most common methods: diff --git a/src/content/docs/guides/external-tools/how-to-set-up-ollama.mdx b/src/content/docs/guides/external-tools/how-to-set-up-ollama.mdx index 9df5eebb..6022b3f3 100644 --- a/src/content/docs/guides/external-tools/how-to-set-up-ollama.mdx +++ b/src/content/docs/guides/external-tools/how-to-set-up-ollama.mdx @@ -16,7 +16,7 @@ In this guide, we’ll walk through how to use Warp to install, profile, and int --- -### 1. Check Your System Specs +### 1. check your system specs Before running large language models (LLMs) locally, confirm your hardware can handle them. @@ -29,7 +29,7 @@ Example setups: --- -### 2. Run Your First Model +### 2. run your first model Run a model locally: @@ -45,7 +45,7 @@ Use Warp to easily monitor GPU usage and model response time. --- -### 3. Understanding Model Terms +### 3. understanding model terms Here’s a quick glossary for choosing the right local model: @@ -59,7 +59,7 @@ Here’s a quick glossary for choosing the right local model: --- -### 4. Integrate Ollama into Your App +### 4. integrate ollama into your app Most apps use OpenAI-compatible APIs, so integration is simple. @@ -72,7 +72,7 @@ Warp helps you quickly locate, edit, and test the integration directly from the --- -### 6. Customize Model Behavior +### 6. customize model behavior Pull and modify a model. diff --git a/src/content/docs/guides/external-tools/linear-mcp-retrieve-issue-data.mdx b/src/content/docs/guides/external-tools/linear-mcp-retrieve-issue-data.mdx index fe9a8f4d..74ac55d3 100644 --- a/src/content/docs/guides/external-tools/linear-mcp-retrieve-issue-data.mdx +++ b/src/content/docs/guides/external-tools/linear-mcp-retrieve-issue-data.mdx @@ -19,7 +19,7 @@ This tutorial covers how to: * Add and configure a Linear MCP server in Warp * Use MCP to query and retrieve issue data -### 1. Adding the Linear MCP Serve +### 1. adding the linear MCP serve #### Add a new server in Warp @@ -45,7 +45,7 @@ This tutorial covers how to: --- -### 2. Testing the Connection +### 2. testing the connection After saving, retry your earlier query: diff --git a/src/content/docs/guides/external-tools/using-mcp-servers-with-warp.mdx b/src/content/docs/guides/external-tools/using-mcp-servers-with-warp.mdx index 183ad825..fbde7baa 100644 --- a/src/content/docs/guides/external-tools/using-mcp-servers-with-warp.mdx +++ b/src/content/docs/guides/external-tools/using-mcp-servers-with-warp.mdx @@ -10,7 +10,7 @@ import VideoEmbed from '@components/VideoEmbed.astro'; -### 1. What Are MCP Servers? +### 1. what are MCP servers? MCP (Model Context Protocol) servers let Warp agents connect to external systems like GitHub, Linear, or Jira — so they can read, write, and reason about those systems natively. @@ -22,7 +22,7 @@ For example: --- -### 2. Problem Setup +### 2. problem setup Andrew starts with Warp’s universal input, but it doesn’t yet know what a “ticket” is. @@ -33,7 +33,7 @@ At this point, Warp can’t find or interpret the ticket, because no MCP server --- -### 3. Adding the Linear MCP Server +### 3. adding the linear MCP server To connect Linear: @@ -49,7 +49,7 @@ Once added, Warp: --- -### 4. Using Rules with MCP Servers +### 4. using rules with MCP servers Andrew adds a rule called **check-linear**, which helps the agent automatically associate “tickets” with the Linear MCP Server. @@ -60,7 +60,7 @@ Rules make context switching between systems seamless — the agent doesn’t ne --- -### 5. Dynamic Context Loading +### 5. dynamic context loading Warp’s MCP support is **dynamic**: @@ -72,7 +72,7 @@ No need to restart Warp or reset your session. --- -### 6. Running the Task +### 6. running the task After adding Linear, Andrew runs: diff --git a/src/content/docs/guides/getting-started/10-coding-features-you-should-know.mdx b/src/content/docs/guides/getting-started/10-coding-features-you-should-know.mdx index ae95af78..3ac64a39 100644 --- a/src/content/docs/guides/getting-started/10-coding-features-you-should-know.mdx +++ b/src/content/docs/guides/getting-started/10-coding-features-you-should-know.mdx @@ -8,7 +8,7 @@ sidebar: --- import VideoEmbed from '@components/VideoEmbed.astro'; -## 10 Coding Features You Should Know in Warp +## 10 coding features you should know in warp If you didn’t already know, you can code directly in Warp. @@ -21,7 +21,7 @@ Let’s walk through the 10 core features you need to know to get started. --- -### 1. Search for Files +### 1. search for files Open the **Command Palette**: @@ -37,14 +37,14 @@ From here, you can search and open any file in your project — no need to `cd` --- -### 2. Tabbed File Viewer +### 2. tabbed file viewer When you open files, Warp shows them in **tabs** rather than split panes.\ This keeps your workspace clean while still allowing you to switch quickly between multiple files. --- -### 3. Full Editor Support +### 3. full editor support You can edit code directly inside Warp — just like any modern editor. @@ -55,7 +55,7 @@ No need for memorized shortcuts: --- -### 4. Find and Replace +### 4. find and replace Warp supports full **find and replace** with: @@ -68,7 +68,7 @@ These features make renaming variables or refactoring code fast and consistent. --- -### 5. Syntax Highlighting +### 5. syntax highlighting Warp supports syntax highlighting for **dozens of languages and frameworks**.\ It appears both in: @@ -80,7 +80,7 @@ This makes it easy to visually scan code at a glance. --- -### 6. Linked File References +### 6. linked file references When Warp’s agent references a file, it automatically **links to the exact line of code**.\ Clicking the link opens that file at that line inside Warp — perfect for tracing logic or verifying changes. @@ -102,7 +102,7 @@ This reduces hallucinations and keeps agents grounded in your actual code. --- -### 8. Code Snippet References +### 8. code snippet references When Warp explains something about your codebase, it surfaces the **exact code snippet**.\ You can attach that snippet as fresh context for your next prompt. This keeps token usage lean and the agent's focus sharp. @@ -120,6 +120,6 @@ This makes it easier for agents to: --- -### 10. File Tree View +### 10. file tree view Click the file-tree icon in Warp to **browse your entire repo** and open any file with a single click. diff --git a/src/content/docs/guides/getting-started/how-to-customize-warps-appearance.mdx b/src/content/docs/guides/getting-started/how-to-customize-warps-appearance.mdx index fd7df39d..d1ef0943 100644 --- a/src/content/docs/guides/getting-started/how-to-customize-warps-appearance.mdx +++ b/src/content/docs/guides/getting-started/how-to-customize-warps-appearance.mdx @@ -16,7 +16,7 @@ Here’s a quick walkthrough of how to make Warp feel like _your_ development en --- -### 1. Changing Themes +### 1. changing themes Open the **Command Palette** with: @@ -29,7 +29,7 @@ You can preview and apply any theme instantly — for example, switching from th --- -### 2. Adjusting Input Placement +### 2. adjusting input placement Warp’s **input bar** can live in three different positions: @@ -39,7 +39,7 @@ Warp’s **input bar** can live in three different positions: --- -### 3. Managing AI & Agent Settings +### 3. managing AI & agent settings Open **Settings → AI** to control: @@ -54,7 +54,7 @@ You can also allowlist or block specific commands that always require confirmati --- -### 4. Indexing Your Codebases +### 4. indexing your codebases Warp prompts you to index your codebase the first time you `cd` into it.\ Indexing enables faster: @@ -67,7 +67,7 @@ You can also manually re-index a folder from the sidebar anytime. --- -### 5. Team Collaboration +### 5. team collaboration In the Teams tab, you can: @@ -78,7 +78,7 @@ This makes Warp a shared, contextual workspace — not just an individual tool. --- -### 6. Look & Feel +### 6. look & feel Under Appearance, you can tweak: diff --git a/src/content/docs/guides/getting-started/how-to-make-warps-ui-more-minimal.mdx b/src/content/docs/guides/getting-started/how-to-make-warps-ui-more-minimal.mdx index 31890412..10934ea5 100644 --- a/src/content/docs/guides/getting-started/how-to-make-warps-ui-more-minimal.mdx +++ b/src/content/docs/guides/getting-started/how-to-make-warps-ui-more-minimal.mdx @@ -22,7 +22,7 @@ Warp will surface options that let you quickly hide features and visual elements --- -### 2. Key UI Toggles to Disable +### 2. key UI toggles to disable #### Inline & AI Features @@ -40,7 +40,7 @@ Warp will surface options that let you quickly hide features and visual elements --- -### 3. Choose a Simpler Theme +### 3. choose a simpler theme Visual noise can come from colors too.\ Try switching to a calmer theme from the Command Palette: @@ -55,7 +55,7 @@ A consistent neutral palette makes Warp feel lighter and easier on the eyes. --- -### 4. Switch to the Classic Prompt +### 4. switch to the classic prompt Warp’s Universal Prompt is great for AI workflows — it supports: @@ -76,7 +76,7 @@ This instantly gives Warp a retro, text-first look — no clutter, no distractio --- -### 5. Reduce Tab Bar Visibility +### 5. reduce tab bar visibility You can make the tab bar appear only when you hover: diff --git a/src/content/docs/guides/getting-started/how-to-master-warps-code-review-panel.mdx b/src/content/docs/guides/getting-started/how-to-master-warps-code-review-panel.mdx index 04643fbc..8a535d28 100644 --- a/src/content/docs/guides/getting-started/how-to-master-warps-code-review-panel.mdx +++ b/src/content/docs/guides/getting-started/how-to-master-warps-code-review-panel.mdx @@ -11,13 +11,13 @@ import VideoEmbed from '@components/VideoEmbed.astro'; -### 1. Why Use the Code Review Panel +### 1. why use the Code Review panel Warp’s Code Review Panel helps you stay focused while coding by showing all active file diffs, additions, and deletions — without leaving your workspace. --- -### 2. Start with a Coding Task +### 2. start with a coding task The app has a UI issue: the hover text is black on dark gray, making it unreadable. @@ -42,7 +42,7 @@ The panel shows: --- -### 4. Editing and Reviewing Code +### 4. editing and reviewing code You can open any file directly from the panel in Warp’s **built-in editor**: @@ -54,7 +54,7 @@ Save changes — and they’ll reflect instantly in the diff view. --- -### 5. Componentizing Changes +### 5. componentizing changes Want that same hover fix across the app?\ Prompt Warp to componentize the hover style. @@ -64,7 +64,7 @@ The agent then creates a `Tooltip` component that reuses your schema everywhere. --- -### 6. Reviewing and Committing +### 6. reviewing and committing Once the fix looks correct: diff --git a/src/content/docs/guides/getting-started/welcome-to-warp.mdx b/src/content/docs/guides/getting-started/welcome-to-warp.mdx index 44f771bd..4377bf30 100644 --- a/src/content/docs/guides/getting-started/welcome-to-warp.mdx +++ b/src/content/docs/guides/getting-started/welcome-to-warp.mdx @@ -43,7 +43,7 @@ Warp’s agent will review your current branch, run git commands in the backgrou --- -### 3. Blending Terminal and Agentic Workflows +### 3. blending terminal and agentic workflows The beauty of Warp is in how seamlessly it blends traditional CLI workflows with AI-driven automation.\ You can: diff --git a/src/content/docs/quickstart.mdx b/src/content/docs/quickstart.mdx index 92755569..3a3b1761 100644 --- a/src/content/docs/quickstart.mdx +++ b/src/content/docs/quickstart.mdx @@ -48,7 +48,7 @@ Download Warp from [warp.dev](https://www.warp.dev/download) and follow the inst When you launch Warp, you'll see a terminal session ready for input. You can optionally sign up for an account (top right), or skip and start using Warp immediately. -## 2. Run a command and see Blocks +## 2. run a command and see blocks Run any command you'd normally use, for example: diff --git a/src/content/docs/reference/api-and-sdk/demo-sentry-monitoring-with-sdk.mdx b/src/content/docs/reference/api-and-sdk/demo-sentry-monitoring-with-sdk.mdx index 776b2da1..5135b88b 100644 --- a/src/content/docs/reference/api-and-sdk/demo-sentry-monitoring-with-sdk.mdx +++ b/src/content/docs/reference/api-and-sdk/demo-sentry-monitoring-with-sdk.mdx @@ -6,7 +6,7 @@ description: >- --- import VideoEmbed from '@components/VideoEmbed.astro'; -### Turn Production Errors into Draft PRs with Cloud Agents + TypeScript SDK +### Turn production errors into draft prs with cloud agents + typescript SDK diff --git a/src/content/docs/reference/api-and-sdk/quickstart.mdx b/src/content/docs/reference/api-and-sdk/quickstart.mdx index f3472053..1caa4361 100644 --- a/src/content/docs/reference/api-and-sdk/quickstart.mdx +++ b/src/content/docs/reference/api-and-sdk/quickstart.mdx @@ -70,7 +70,7 @@ The `state` has the following possible values: * `QUEUED` - The run is waiting to start. * `INPROGRESS` - The agent is actively running. * `SUCCEEDED` - The run completed successfully. -* `FAILED` - The run encountered an error. Check the `status_message` field in the response for details. +* `FAILED` - The run encountered an error. Check the **status_message** field in the response for details. These are the most common states. See the [full API reference](/reference/api-and-sdk/) for all possible values. diff --git a/src/content/docs/reference/api-and-sdk/troubleshooting/errors/invalid-request.mdx b/src/content/docs/reference/api-and-sdk/troubleshooting/errors/invalid-request.mdx index 86a83033..0fbee2a7 100644 --- a/src/content/docs/reference/api-and-sdk/troubleshooting/errors/invalid-request.mdx +++ b/src/content/docs/reference/api-and-sdk/troubleshooting/errors/invalid-request.mdx @@ -27,7 +27,7 @@ This error is returned when: * A referenced identifier is in the wrong format * A team-owned task references a personal environment (team tasks require team-scoped environments) -The `detail` field in the response will describe the specific validation issue. +The **detail** field in the response will describe the specific validation issue. --- @@ -49,7 +49,7 @@ The `detail` field in the response will describe the specific validation issue. ## How to resolve -1. Check the `detail` field for the specific validation issue. +1. Review the `detail` field for the specific validation issue. 2. Correct the request parameters according to the [API documentation](/reference/api-and-sdk/). 3. Retry the request. diff --git a/src/content/docs/reference/cli/troubleshooting.mdx b/src/content/docs/reference/cli/troubleshooting.mdx index 81658beb..f5c67f97 100644 --- a/src/content/docs/reference/cli/troubleshooting.mdx +++ b/src/content/docs/reference/cli/troubleshooting.mdx @@ -174,7 +174,7 @@ This usually means the Docker image is missing required dependencies. Fix by eit * Updating the Dockerfile used to build the image, then pushing a new version to Docker Hub and updating the environment with the new image, or * Adding additional setup commands to install the missing tools: `oz environment update --setup-command "apt-get update && apt-get install -y "` -#### **I see "VM failed before the agent could run. This is likely an issue with your Docker image"** +#### **I see "VM failed before the agent could run. this is likely an issue with your docker image"** This typically means your Docker image uses musl libc instead of glibc. Alpine Linux and other musl-based images are not compatible with the agent runtime. diff --git a/src/content/docs/support-and-community/community/open-source-licenses.mdx b/src/content/docs/support-and-community/community/open-source-licenses.mdx index 9ea00ffa..42bdf4fc 100644 --- a/src/content/docs/support-and-community/community/open-source-licenses.mdx +++ b/src/content/docs/support-and-community/community/open-source-licenses.mdx @@ -741,7 +741,7 @@ sidebar: | Windows Terminal | MIT | | GitHub Desktop | MIT | -## Full License Text +## Full license text ```text Third-Party Licenses for Warp @@ -18498,7 +18498,7 @@ This is the Community Data License Agreement - Permissive, Version 2.0 (the "agreement"). Data Provider(s) and Data Recipient(s) agree as follows: -## 1. Provision of the Data +## 1. provision of the data 1.1. A Data Recipient may use, modify, and share the Data made available by Data Provider(s) under this agreement if that Data @@ -18509,18 +18509,18 @@ Recipient's use, modification, or sharing of any portions of the Data that are in the public domain or that may be used, modified, or shared under any other legal exception or limitation. -## 2. Conditions for Sharing Data +## 2. conditions for sharing data 2.1. A Data Recipient may share Data, with or without modifications, so long as the Data Recipient makes available the text of this agreement with the shared Data. -## 3. No Restrictions on Results +## 3. no restrictions on results 3.1. This agreement does not impose any restriction or obligations with respect to the use, modification, or sharing of Results. -## 4. No Warranty; Limitation of Liability +## 4. no warranty; limitation of liability 4.1. All Data Recipients receive the Data subject to the following terms: diff --git a/src/content/docs/support-and-community/plans-and-billing/bring-your-own-api-key.mdx b/src/content/docs/support-and-community/plans-and-billing/bring-your-own-api-key.mdx index cd2f84c7..ad6ac3be 100644 --- a/src/content/docs/support-and-community/plans-and-billing/bring-your-own-api-key.mdx +++ b/src/content/docs/support-and-community/plans-and-billing/bring-your-own-api-key.mdx @@ -99,7 +99,7 @@ You can choose to enable **Warp credit fallback**. When enabled, if an agent req ![Setting to enable Warp credit fallback when a BYOK request fails.](../../../../assets/support-and-community/fallback.png) -### Zero Data Retention (ZDR) and BYOK +### Zero data retention (ZDR) and BYOK Warp is **SOC 2 compliant** and has **Zero Data Retention (ZDR)** policies with all of its contracted LLM providers. No customer AI data is retained, stored, or used for training by the model providers. @@ -111,7 +111,7 @@ However, when you use your own API key: Warp itself never stores your LLM API keys. -### BYOK on Enterprise and Business plans +### BYOK on enterprise and business plans Currently, BYOK is configured at the **user level**, not the team or admin level: diff --git a/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx b/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx index b3580d15..75fbf7d3 100644 --- a/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx +++ b/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx @@ -86,7 +86,7 @@ Team members have access to your shared [Warp Drive](/knowledge-and-collaboratio * Create unlimited [Notebooks](/knowledge-and-collaboration/warp-drive/notebooks/) and [Workflows](/knowledge-and-collaboration/warp-drive/workflows/) in Warp Drive to organize and share knowledge across your team. * Use Unlimited [Session Sharing](/knowledge-and-collaboration/session-sharing/) to collaborate in real time through live, shared terminal sessions. -### My co-workers are using Warp but we’re not on a Team together yet. How does billing work? +### My co-workers are using warp but we’re not on a team together yet. how does billing work? Individual users with either personal or work email domains may continue to use Warp independently without incurring billing. The benefit of joining together on a Warp Team is that you get access to a shared Team Drive and collaboration features. @@ -237,13 +237,13 @@ The team at Warp is standing by and ready to help. For subscribers technical iss For more details, see this blog post on [Warp's plan changes](https://www.warp.dev/blog/warp-new-pricing-flexibility-byok). -#### How do I change from my current plan to the new Build or Business plan? +#### How do I change from my current plan to the new build or business plan? You can switch to the new Warp Build or Business plan anytime from **Settings** > **Billing and usage** > **Manage billing** > **Update subscription** in the Warp app or at [app.warp.dev/upgrade](https://app.warp.dev/upgrade). Select Change plan, then choose the plan that fits your needs. If you take no action, your Pro, Turbo, Lightspeed, or legacy Business plan will automatically move to the new structure on your first renewal after **December 1, 2025**. You’ll receive an email before your renewal with details to make the transition easier. -#### What happens when I change from my legacy plan to the new Build or Business plans? +#### What happens when I change from my legacy plan to the new build or business plans? If you move from Warp’s legacy Pro, Turbo, Lightspeed, or old Business plans to the new Build or Business plans: @@ -280,7 +280,7 @@ For **existing monthly subscribers**, changes will apply on your first renewal a If you have any questions, please reach out to us at **billing@warp.dev**. -#### **What happens to my current plan (Pro, Turbo, Lightspeed, Business)?** +#### **What happens to my current plan (pro, turbo, lightspeed, business)?** You will retain your current plan and credits until the first renewal after December 1, 2025. At renewal, all current Pro, Turbo, Lightspeed, and Business plans will transition to the new Warp Build and Business plans. @@ -311,11 +311,11 @@ For existing users on legacy plans, plan credits on Pro, Turbo, and Lightspeed d For the Build plan, credits will not rollover but Add-on credits will rollover and be valid for 12 months from the date of purchase. -#### Can I purchase Add-on Credits on legacy plans (Pro, Turbo, Lightspeed)? +#### Can I purchase add-on credits on legacy plans (pro, turbo, lightspeed)? No. Add-on Credits (including auto-reload) are only available on the Build, Business, and Enterprise plans. If you attempt to purchase Add-on Credits on a legacy plan, the purchase will not go through. To access Add-on Credits, switch to the Build plan at any time from **Settings** > **Billing and usage** or at [app.warp.dev/upgrade](https://app.warp.dev/upgrade). If you need additional usage while on a legacy plan, you can use [Overages (Legacy)](/support-and-community/plans-and-billing/overages-legacy/) instead. -#### Can I bring my own key on legacy plans (Pro, Turbo, Lightspeed)? +#### Can I bring my own key on legacy plans (pro, turbo, lightspeed)? No, Bring-your-own API key for OpenAI, Anthropic, and Gemini is only available to users on the Warp Build plan. You can choose to switch your existing plan to Warp Build at any time before your applicable renewal date to access BYOK. @@ -338,7 +338,7 @@ Add-on Credits roll over month to month, remain valid for 12 months, and offer u If you’re part of a team that needs shared credit management, SSO, or enforced Zero Data Retention (ZDR), the Business plan provides all the same AI capabilities plus advanced security and administrative features. -#### Should I subscribe to the Build plan or the Business plan? +#### Should I subscribe to the build plan or the business plan? If you’re an individual developer or part of a small team, the Build plan is the best fit. It includes 1,500 monthly credits, discounted Add-on Credits for additional usage, and the ability to bring your own API key (BYOK) for OpenAI, Anthropic, or Google models. You’ll also get unlimited Warp Drive objects, collaboration tools, and the highest codebase indexing limits. diff --git a/src/content/docs/support-and-community/privacy-and-security/network-log.mdx b/src/content/docs/support-and-community/privacy-and-security/network-log.mdx index 969221e3..2325b3a6 100644 --- a/src/content/docs/support-and-community/privacy-and-security/network-log.mdx +++ b/src/content/docs/support-and-community/privacy-and-security/network-log.mdx @@ -24,6 +24,6 @@ Each log item is a timestamped Debug format string for either a request or respo -## Known issues with Network Log +## Known issues with network log At the moment, network traffic originating from crash reports and error messages is not captured in the network log. This is due to our use of the Sentry SDK, which encapsulates all network logic and doesn’t currently expose a hook for handling requests and responses directly. The team is actively investigating a solution to include such traffic in the log in a future release. You may also disable Crash Reporting entirely in Warp’s **Settings** > **Privacy** tab. diff --git a/src/content/docs/support-and-community/privacy-and-security/privacy.mdx b/src/content/docs/support-and-community/privacy-and-security/privacy.mdx index 096d6639..9ab86b74 100644 --- a/src/content/docs/support-and-community/privacy-and-security/privacy.mdx +++ b/src/content/docs/support-and-community/privacy-and-security/privacy.mdx @@ -66,7 +66,7 @@ Deletion jobs run every 24 hours, so if you deleted your account and want to sig If you're a [Team](/knowledge-and-collaboration/teams/) admin, the deletion flow will require that you assign a team member as the new admin. ::: -### Exhaustive Telemetry Table +### Exhaustive telemetry table | Event Name | Description | |---|---| @@ -81,9 +81,9 @@ If you're a [Team](/knowledge-and-collaboration/teams/) admin, the deletion flow | `AI Execution Profile: Removed From Denylist` | An item was removed from an AI execution profile denylist | | `AI Execution Profile: Setting Updated` | An AI execution profile setting was updated | | `AI Input Not Sent` | The AI input was not sent | -| `AI Suggested Rule Added` | Clicked the Add Suggested Rule button in the AI blocklist | +| `AI Suggested Rule Added` | Clicked the Add Suggested Rule button in the AI block list | | `AI Suggested Rule Content Changed` | Content changed by the user in the suggested rule dialog | -| `AI Suggested Rule Edited` | Clicked the Edit Suggested Rule button in the AI blocklist | +| `AI Suggested Rule Edited` | Clicked the Edit Suggested Rule button in the AI block list | | `AIAutonomy.AutoexecutedRequestedCommand` | Autoexecuted an Agent Mode requested command | | `AIAutonomy.ChangedAgentModeCodingPermissions` | Changed Agent Mode permissions for coding tasks | | `AIAutonomy.ToggledAutoexecuteReadonlyCommandsSetting` | Toggled setting to autoexecute readonly Agent Mode requested commands | @@ -100,7 +100,7 @@ If you're a [Team](/knowledge-and-collaboration/teams/) admin, the deletion flow | `Agent Mode Setup Banner Accepted` | Agent Mode setup banner accepted | | `Agent Mode Setup Banner Dismissed` | Agent Mode setup banner dismissed | | `Agent Mode Setup Project Scoped Rules Action` | User clicked a button in the Agent Mode setup project scoped rules step | -| `Agent Mode.Setup Codebase Context Action` | User clicked a button in the Agent Mode setup codebase context step | +| `Agent Mode.Setup Codebase Context Action` | User clicked a button in the Agent Mode setup Codebase Context step | | `Agent Predict` | Completed an Agent Predict prediction | | `Agent Toolbar Dismissed` | User dismissed the use-agent toolbar | | `AgentManagement.AgentTypeSelectorOpened` | User opened the agent type selector from agent management | @@ -296,8 +296,8 @@ If you're a [Team](/knowledge-and-collaboration/teams/) admin, the deletion flow | `CodexModal.UseCodexClicked` | User clicked 'Use Codex' in the Codex modal | | `Command Correction Event` | Accepted command correction | | `Command File Run` | Opened a .cmd or unix executable file and ran it directly in Warp | -| `Command Palette Search Accepted` | Accepted a command palette search result | -| `Command Palette Search Exited` | Exited command palette search without accepting a result | +| `Command Palette Search Accepted` | Accepted a Command Palette search result | +| `Command Palette Search Exited` | Exited Command Palette search without accepting a result | | `Command Search Async Query Completed` | Finished searching for a command in the background | | `Command Search Exited` | Exited command search (universal search panel to search) without accepting a result | | `Command Search Filter Changed` | Changed command search filter | @@ -500,7 +500,7 @@ If you're a [Team](/knowledge-and-collaboration/teams/) admin, the deletion flow | `SSH Tmux Warpify Block Dismissed` | User dismissed an ssh tmux warpify block | | `Save Launch Config` | Saved current launch configuration of windows, tabs, and panes | | `Select App Icon` | Selected app icon | -| `Select Command Palette Option` | Selected option from command palette (i.e. CMD-P) | +| `Select Command Palette Option` | Selected option from Command Palette (i.e. CMD-P) | | `Select Cursor Type` | Selected cursor type | | `Select Navigation Palette Item` | Selected session from the Session Navigation Palette (search across panes, tabs, and windows) | | `Select Theme` | Selected theme | @@ -551,7 +551,7 @@ If you're a [Team](/knowledge-and-collaboration/teams/) admin, the deletion flow | `Thin Strokes Setting Changed` | Changed thin strokes setting in settings -> Appearance | | `Tier Limit Hit` | User hit the tier limit for a feature | | `Toggle Active AI Enablement` | Toggled active AI enablement. | -| `Toggle Agent Mode Codebase Context` | Toggled on/off the enablement of codebase context usage for Agent Mode. | +| `Toggle Agent Mode Codebase Context` | Toggled on/off the enablement of Codebase Context usage for Agent Mode. | | `Toggle Agent Mode Query Suggestions Setting` | Toggled on/off the prompt suggestions setting | | `Toggle Approvals Modal` | Opened or closed teams modal | | `Toggle Block Filter Case Sensitivity` | Toggled on/off case sensitivity within the block filter editor | @@ -559,7 +559,7 @@ If you're a [Team](/knowledge-and-collaboration/teams/) admin, the deletion flow | `Toggle Block Filter Query` | Toggled on/off a block filter query | | `Toggle Block Filter Regex` | Toggled on/off regex within the block filter editor | | `Toggle Code Suggestions Setting` | Toggled on/off the code suggestions setting | -| `Toggle Codebase Context Autoindexing` | Toggled on/off the enablement of autoindexing for codebase context. | +| `Toggle Codebase Context Autoindexing` | Toggled on/off the enablement of autoindexing for Codebase Context. | | `Toggle Dim Inactive Panes` | Whether the dim inactive panes feature has been toggled | | `Toggle Focus Pane On Hover` | Toggled on/off focus pane on hover feature, which causes panes to automatically focus when hovering over them | | `Toggle Git Operations Autogen Setting` | Toggled on/off the git operations autogen setting | @@ -643,4 +643,3 @@ If you're a [Team](/knowledge-and-collaboration/teams/) admin, the deletion flow | `revenue.AutoReloadModalClosed` | User closed the auto-reload modal (either dismissed or enabled auto-reload) | | `revenue.AutoReloadToggledFromBillingSettings` | User toggled auto-reload in Billing & Usage settings | | `revenue.OutOfCreditsBannerClosed` | User closed the 'Out of credits' banner (dismissed or purchased credits) | - diff --git a/src/content/docs/support-and-community/privacy-and-security/secret-redaction.mdx b/src/content/docs/support-and-community/privacy-and-security/secret-redaction.mdx index 3e59d785..adf2822c 100644 --- a/src/content/docs/support-and-community/privacy-and-security/secret-redaction.mdx +++ b/src/content/docs/support-and-community/privacy-and-security/secret-redaction.mdx @@ -19,7 +19,7 @@ Warp ships with a [list of recommended regex](/support-and-community/privacy-and By default, identified secrets will be displayed with a strikethrough visual treatment, i.e. ` echo`` `` `~~`password`~~. -If instead you'd prefer to visually hide the secrets as well, i.e. `echo ********`, the setting to obfuscate secrets with asterisks can be found in **Settings** > **Privacy** > **Secret redaction** > **Hide secrets in blocklist**. +If instead you'd prefer to visually hide the secrets as well, i.e. `echo ********`, the setting to obfuscate secrets with asterisks can be found in **Settings** > **Privacy** > **Secret redaction** > **Hide secrets in block list**. Clicking on a secret will display a tooltip that lets you reveal the secret or copy the secret's contents. When trying to copy terminal output containing secrets, it will be copied as asterisks (e.g. `echo password` becomes `echo ********`) unless revealed or copied from the tooltip. Secret redaction is not applied in [Session Sharing](/knowledge-and-collaboration/session-sharing/). diff --git a/src/content/docs/support-and-community/troubleshooting-and-support/sending-us-feedback.mdx b/src/content/docs/support-and-community/troubleshooting-and-support/sending-us-feedback.mdx index e354a545..31f789f9 100644 --- a/src/content/docs/support-and-community/troubleshooting-and-support/sending-us-feedback.mdx +++ b/src/content/docs/support-and-community/troubleshooting-and-support/sending-us-feedback.mdx @@ -106,10 +106,10 @@ Warp's logs and crash reports _**do not**_ contain any console input or output. ```bash # Run if Warp on macOS is installed - RUST_LOG=wgpu_core=info,wgpu_hal=info /Applications/Warp.app/Contents/MacOS/stable + RUST_LOG=wgpu_core=info,wgpu_hal=info /Applications/Warp.app/Contents/macOS/stable # Run if Warp Preview on macOS is installed - RUST_LOG=wgpu_core=info,wgpu_hal=info /Applications/WarpPreview.app/Contents/MacOS/preview + RUST_LOG=wgpu_core=info,wgpu_hal=info /Applications/WarpPreview.app/Contents/macOS/preview ``` ::: diff --git a/src/content/docs/terminal/appearance/themes.mdx b/src/content/docs/terminal/appearance/themes.mdx index d4ae608e..e5f86978 100644 --- a/src/content/docs/terminal/appearance/themes.mdx +++ b/src/content/docs/terminal/appearance/themes.mdx @@ -53,7 +53,7 @@ Automatically create new themes based on a background image. 3. Upload the image and select the background color. 4. Click "Create Theme" to save and accept the new theme. -### OS Theme Sync +### OS theme sync Warp supports synchronizing your theme with the OS’s light and dark themes. To enable this: diff --git a/src/content/docs/terminal/blocks/sticky-command-header.mdx b/src/content/docs/terminal/blocks/sticky-command-header.mdx index 001bbbe9..0f3d5173 100644 --- a/src/content/docs/terminal/blocks/sticky-command-header.mdx +++ b/src/content/docs/terminal/blocks/sticky-command-header.mdx @@ -11,7 +11,7 @@ import VideoEmbed from '@components/VideoEmbed.astro'; For long-running commands that take up the full screen, the sticky header only shows after you start scrolling up. This is to prevent the header from blocking the top part of the output for commands like `git log` that simulate full-screen apps. ::: -## How to access Sticky Command Header +## How to access sticky command header @@ -34,13 +34,13 @@ For long-running commands that take up the full screen, the sticky header only s -## How to use Sticky Command Header +## How to use sticky command header * If a Block has a large output ( e.g. `seq 1 1000`), the header of the Block will show on the top of the active Window, Tab, or Pane. * Click on the Sticky Command Header to quickly jump to the top of the Block. * While active you can also minimize the Sticky Command Header on the active pane by clicking the UP/DOWN arrow in the middle of the header. -## How Sticky Command Header works +## How sticky command header works diff --git a/src/content/docs/terminal/input/universal-input.mdx b/src/content/docs/terminal/input/universal-input.mdx index 8619acb4..c60bf8e3 100644 --- a/src/content/docs/terminal/input/universal-input.mdx +++ b/src/content/docs/terminal/input/universal-input.mdx @@ -80,7 +80,7 @@ When Warp detects an input type, the input switcher softly highlights the corres The model Warp uses to detect natural language automatically is completely local. ::: -#### Disabling Natural Language Auto-detection +#### Disabling natural language auto-detection By default, auto-detection is enabled. This means Warp decides whether to treat your input as a command or an Agent prompt. @@ -91,7 +91,7 @@ By default, auto-detection is enabled. This means Warp decides whether to treat | Agent (natural language) mode enabled | Terminal (shell) mode enabled | | -------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- | -| | | +| Terminal mode enabled with auto-detection off | Agent Mode enabled with auto-detection off | ### Entering Agent Mode @@ -177,7 +177,7 @@ You can leave Agent or Terminal Modes in several ways: -### Natural Language Auto-detection Settings +### Natural language auto-detection settings Warp can automatically detect when you’re writing in plain English and switch you into Agent Mode. If needed, you can customize or disable this behavior. diff --git a/src/content/docs/terminal/more-features/accessibility.mdx b/src/content/docs/terminal/more-features/accessibility.mdx index 546dc004..4c48fe9d 100644 --- a/src/content/docs/terminal/more-features/accessibility.mdx +++ b/src/content/docs/terminal/more-features/accessibility.mdx @@ -13,7 +13,7 @@ We recognize the need to improve the experience for those visually impaired, as **Keep in mind that this is a work-in-progress and the current state is not a final state of accessibility in Warp**. -## How to use Warp with Voice Over? +## How to use warp with voice over? The best way to start working with Warp & VoiceOver is to install it using Homebrew: diff --git a/src/content/docs/terminal/more-features/files-and-links.mdx b/src/content/docs/terminal/more-features/files-and-links.mdx index 7315b95a..3c979e9b 100644 --- a/src/content/docs/terminal/more-features/files-and-links.mdx +++ b/src/content/docs/terminal/more-features/files-and-links.mdx @@ -73,7 +73,7 @@ Non exhaustive list of editors, please submit new ones on our GitHub, see [Sendi ## Scripts -Warp can open `.command` and Unix Executable files from the finder directly. +Warp can open **.command** and Unix Executable files from the finder directly. 1. Find a `.command` or Shell script you'd like to open in Finder. 2. Right-click and open the script with Warp. diff --git a/src/content/docs/terminal/more-features/full-screen-apps.mdx b/src/content/docs/terminal/more-features/full-screen-apps.mdx index 2aa78d41..eb3afeb7 100644 --- a/src/content/docs/terminal/more-features/full-screen-apps.mdx +++ b/src/content/docs/terminal/more-features/full-screen-apps.mdx @@ -33,7 +33,7 @@ If you want a mouse event to go to Warp instead (for example, for text selection ## Padding -Warp supports configuring how much padding surrounds full-screen apps. The default is 0 pixel padding, but this can be changed to a custom padding amount or to match the padding in the Blocklist. +Warp supports configuring how much padding surrounds full-screen apps. The default is 0 pixel padding, but this can be changed to a custom padding amount or to match the padding in the block list. :::note Warp allows you to scale your terminal by fractions of a cell width | height. When your terminal size is not perfectly aligned to a cell width | height, the extra space appears as padding on the right | bottom. @@ -42,7 +42,7 @@ Warp allows you to scale your terminal by fractions of a cell width | height. Wh ### How to access it * Go to **Settings** > **Appearance** > **Full-screen Apps** or from the [Command Palette](/terminal/command-palette/) search for "Appearance" - * `Use custom padding in alt-screen` is enabled by default, you can disable it to match the Blocklist padding + * `Use custom padding in alt-screen` is enabled by default, you can disable it to match the block list padding * Set the desired uniform padding (px) pixels, which is set to 0px by default :::caution diff --git a/src/content/docs/terminal/more-features/markdown-viewer.mdx b/src/content/docs/terminal/more-features/markdown-viewer.mdx index 58be5329..2f34b842 100644 --- a/src/content/docs/terminal/more-features/markdown-viewer.mdx +++ b/src/content/docs/terminal/more-features/markdown-viewer.mdx @@ -39,7 +39,7 @@ The following commands are considered Markdown viewers: * `glow` * `less` -### Opening a Markdown file from Finder +### Opening a markdown file from finder From Finder, you can open a Markdown file in Warp from the “Open With” menu that appears when right-clicking on the file. diff --git a/src/content/docs/terminal/more-features/text-selection.mdx b/src/content/docs/terminal/more-features/text-selection.mdx index 003a0d1c..5eba3c01 100644 --- a/src/content/docs/terminal/more-features/text-selection.mdx +++ b/src/content/docs/terminal/more-features/text-selection.mdx @@ -14,7 +14,7 @@ description: >-
Using smart selection to select a file path by double clicking.
-Double-click on text in the input or blocklist. The following patterns are recognized: +Double-click on text in the input or block list. The following patterns are recognized: 1. URLs 2. File paths diff --git a/src/content/docs/terminal/sessions/launch-configurations.mdx b/src/content/docs/terminal/sessions/launch-configurations.mdx index 53135bfa..11b60101 100644 --- a/src/content/docs/terminal/sessions/launch-configurations.mdx +++ b/src/content/docs/terminal/sessions/launch-configurations.mdx @@ -15,7 +15,7 @@ Launch Configurations have been replaced by [Tab Configs](/terminal/windows/tab- With Launch configurations you can save in the app or by adding a yaml file. -## Creating a Launch Configuration +## Creating a launch configuration ### From the UI @@ -29,7 +29,7 @@ With Launch configurations you can save in the app or by adding a yaml file. * Launch Configurations files are generated when you create them with the UI and can also be created or modified manually. * Please see the below for [Launch Configuration YAML file locations, format, and examples](/terminal/sessions/launch-configurations/#launch-configuration-yaml-format). -## Using a Launch Configuration +## Using a launch configuration @@ -66,7 +66,7 @@ You can open saved Launch Configurations via Alfred Workflow or [Raycast](/termi -## Launch Configuration YAML Format +## Launch configuration YAML format All Launch Configuration yaml files are stored in the following location: diff --git a/src/content/docs/terminal/sessions/session-restoration.mdx b/src/content/docs/terminal/sessions/session-restoration.mdx index b5a131c4..fdcd2726 100644 --- a/src/content/docs/terminal/sessions/session-restoration.mdx +++ b/src/content/docs/terminal/sessions/session-restoration.mdx @@ -13,7 +13,7 @@ import { Tabs, TabItem } from '@astrojs/starlight/components'; Session restoration allows you to quickly pick up where you left off in your previous terminal session. -## How to access Session Restoration +## How to access session restoration * Session Restoration comes enabled by default in Warp. diff --git a/src/content/docs/terminal/settings/index.mdx b/src/content/docs/terminal/settings/index.mdx index d01ee9b9..c0b7da5c 100644 --- a/src/content/docs/terminal/settings/index.mdx +++ b/src/content/docs/terminal/settings/index.mdx @@ -5,7 +5,7 @@ description: >- how it works with the Settings panel, and see common configuration examples. --- -Warp stores your preferences in a plain-text file called `settings.toml`. You can edit it directly in any text editor, check it into version control, or generate it with a script. Changes take effect immediately — no restart required. +Warp stores your preferences in a plain-text file called **settings.toml**. You can edit it directly in any text editor, check it into version control, or generate it with a script. Changes take effect immediately — no restart required. The settings file works alongside the graphical Settings panel. Changes you make in either place are reflected in the other. @@ -19,7 +19,7 @@ The settings file works alongside the graphical Settings panel. Changes you make ## Opening your settings file -There are several ways to open `settings.toml`: +The `settings.toml` file is available through these options: * In the Warp app, go to **Settings** and click **Open settings file** at the bottom of the panel. * Open the file directly in any editor at the path listed below for your platform and Warp release channel. diff --git a/src/content/docs/terminal/warpify/subshells.mdx b/src/content/docs/terminal/warpify/subshells.mdx index 3260eded..5d89878d 100644 --- a/src/content/docs/terminal/warpify/subshells.mdx +++ b/src/content/docs/terminal/warpify/subshells.mdx @@ -41,9 +41,9 @@ You can add any command that spawns a bash, fish, or zsh subshell to ‘Added co Furthermore, you can add regular expressions to the Added commands list. Any commands that match an added regex will be eligible for "Warpification." -#### Blocklisting commands +#### Denying commands -Some types of subshells are not compatible, and you may also want to control Warp so it never invites you to "Warpify" the subshells for specific commands. When you add commands to the Blocklist, Warp will never invite you to "Warpify" subshells spawned by those commands. +Some types of subshells are not compatible, and you may also want to control Warp so it never invites you to "Warpify" the subshells for specific commands. When you add commands to the denylist, Warp will never invite you to "Warpify" subshells spawned by those commands. ### Automatically "Warpify" subshells diff --git a/src/content/docs/terminal/windows/tab-configs.mdx b/src/content/docs/terminal/windows/tab-configs.mdx index 35fc1a37..3601da0f 100644 --- a/src/content/docs/terminal/windows/tab-configs.mdx +++ b/src/content/docs/terminal/windows/tab-configs.mdx @@ -7,11 +7,11 @@ description: >- Tab Configs let you define reusable tab setups — including directory, startup commands, pane layout, shell, and theme — in a simple TOML file. Select a Tab Config from the `+` menu to open a fully configured tab with a single click. -## How Tab Configs work +## How tab configs work Each Tab Config is a `.toml` file stored in `~/.warp/tab_configs/`. Every file defines a single tab layout with optional pane splits, startup commands, and parameterized inputs. Tab Configs appear in the `+` menu alongside your existing tabs, so you can launch a preconfigured workspace instantly. -## Creating a Tab Config +## Creating a tab config ### From the UI @@ -23,7 +23,7 @@ Each Tab Config is a `.toml` file stored in `~/.warp/tab_configs/`. Every file d 1. Create a new `.toml` file in `~/.warp/tab_configs/`. Use snake_case for the file name (e.g., `dev_server.toml`). 2. Define the tab layout using the schema below, then save the file. The new config appears in the `+` menu automatically. -### Save an existing tab as a Tab Config +### Save an existing tab as a tab config You can also capture a tab's current state as a reusable Tab Config without writing TOML. Right-click any tab in the [vertical tabs](/terminal/windows/vertical-tabs/) panel or horizontal tab bar to open the context menu, then click **Save as new config**. Warp generates a `.toml` file from the tab's layout, commands, and directory and adds it to the `+` menu. @@ -32,7 +32,7 @@ You can also capture a tab's current state as a reusable Tab Config without writ
Saving a tab config.
-## Managing Tab Configs +## Managing tab configs Saved Tab Configs appear in the `+` menu for quick access. When you hover a Tab Config in the menu, a **sidecar panel** appears alongside it with options to: @@ -45,7 +45,7 @@ Saved Tab Configs appear in the `+` menu for quick access. When you hover a Tab
Tab config menu with sidecar options.
-## Using skills to manage Tab Configs +## Using skills to manage tab configs Warp includes built-in skills for creating and modifying Tab Configs through natural language: